I started getting this error out of the blue trying to startup VS 2010 tonight.  A quick bingle search lead me to the Microsoft Connect site where somebody has already filed it as a bug, and a quick workaround to get VS to start again was to run “devenv /resetuserdata” in the C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE directory.  The problem seems to stem from having a corrupted profile (at least it did for me), and running that command fixed the problem. 

If you are having this issue, give this a try, and head over to the Connect site and vote up the bug to get fixed.

Here is the demos that I will be using for my Talk tonight on jQuery.

Download

So Visual Studio 2008 RTM was released last week.  I'm a bit behind the game and just downloaded it from MSDN.  After the long download, I burnt the ISO to disk and began the install, and what happened?  Installation failure.  I went and did some googling and it seems there are a lot of people having installation problems with RTM.  I followed some of the suggestions I found and nothing seemed to work for me.  So, I had to go and do the research myself in order to get this thing installed.

My installation was failing on the Microsoft Visual Studio Web Authoring Component, which is the third item installed if you do the standard installation (after the .Net framework 3.5 and Microsoft Document Explorer 2008).  I went into the D:\WCU\WebDesignerCore folder and used winzip to extract WebDesignerCore.EXE into another folder, then I attempted to do the installation of the Web Authoring Components manually to see what happened.  I received the following error:

"Setup is unable to proceed due to the following error(s): The 2007 Microsoft Office system does not support upgrading from a prerelease version of the 2007 Microsoft Office system. You must first uninstall any prerelease versions of the 2007 Microsoft Office system products and associates technologies."

Which was a bit strange to me since I am still on Office 2003 and haven't installed any Office 2007 betas to my knowledge.  I dove back into my Add Remove Programs to make sure I didn't have any betas hanging around.  What I did find was that I had the Compatablity Pack for the 2007 Office System (Beta) installed.  I got this a few months back so that I could open up the new Word docx file format using Word 2003.  Seems that when Microsoft first released this patch, it was using Office 2007 beta software.  I uninstalled this package and tried the Web Component install again.  Worked like a charm this time.

I cancelled the installation and began fresh installing VS2008 once again.  This time it successfully went through the Web Components and continued with the rest of the installation with no issues.

Uninstalling the Compatability Pack worked for my issue.  Microsoft has since released a new version of the Compatablity Pack that does not use Office 2007 beta software.  You can find that here.

I'm sure this isn't new to any blogs anywhere, but I wanted a quick place to find it in case I need it again in the future.  We had a problem this morning with an asp page giving the following error:

 Response object error 'ASP 0251 : 80004005'

Response Buffer Limit Exceeded

/page.asp, line 0

Execution of the ASP page caused the Response Buffer to exceed its configured limit.

Turns out that IIS6 sets a limit on how much data can be stored in the response buffer when you are creating a page.  On the particular page that was giving us problems this morning, the total output was over 12MB, and the default for the ASPBufferLimit is only 4MB.  Sure, the 12MB of html being sent back to the client is a problem that will have to be fixed through redesigning the page, but I needed to get the size of the buffer increased so this page would work now.  So, to do so we increase the ASPBufferLimit through the adsutil utility:

adsutil set w3svc/aspbufferinglimit "4194304"

This will set the ASPBufferingLimit on the global web service that all the virtual directories inherit from, meaning that all the sites configured on this box now have this limit.  The number is the amount of bytes for the buffer limit, 4194304 (4MB) being the default.