PowerDNN Website Was Down For 2 Hours?

Looks like they were upgrading their website and that’s why it was down and not due to technical difficulties with their servers. I really liked the features and reviews over internet and I would continue recommending PowerDNN & 3Essentials to my client and will leave up to them to chose one.
UPDATE: 12:00 PM: Response from Tony V., who is Chief Technology Officer (PowerDNN)
We actually knew about that issue with our website. The reason it was down was we were pushing a new version of our website live. Normally we do this late at night, but because of the long weekend, we figured that nobody else would notice. Obviously we were wrong. :D
UPDATE: As of 9:00AM the PowerDNN website is running fine. Overview page now look like below screen shot.

I am greatly shocked to see the PowerDNN website who is specialize in hosting DotNetNuke based websites is facing technical difficulties. As of September 5, 2009 (between 7:00 AM and 8:30 AM) most of the pages on their website are not working and throwing error.
I am wondering what kind of service PowerDNN will able to provide to their customer if their own website were down for more then 2 hours. Following are screen shot of few pages that are throwing error.
Shared Hosting overview page is empty.
URL: http://www.powerdnn.com/SharedHosting/Overview/tabid/292/Default.aspx

PowerDNN advantage page throw error too. URL: http://www.powerdnn.com/SharedHosting/PowerDNNAdvantage/tabid/282/Default.aspx

PowerDNN Dedicated Servers page throw following error. URL: http://www.powerdnn.com/DedicatedServers/Overview/tabid/291/Default.aspx

Comments

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart. Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel. I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances. RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then ...

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs. 25 Best Blogs of 2009 25 Best Blogs 2008 25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog ...

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck ...

Laksha

Search This Blog