VS 2005 Crashes Abound
-
Hey all: We recently moved from Visual Studio 2003 to 2005, and about the same time, I got a new workstation - moved from a Sony Vaio laptop running XP Professional to an HP xw4400 with Vista Business. Apart from a few expected hiccups, things were going great, and I wasn't having any major problems. Then things took a nose-dive for the worse. While working on our WinForms project, VS will hang for several seconds for no apparent reason while in code view. It also seems to want to re-draw the entire form whenever I switch to design view, causing another hang. Granted, some of our forms have too much on them for their own good, but when all I have is a few textboxes and a button or two, having to wait 3-5 seconds for the designer to reappear gets annoying. This seems to happen more and more frequently as the day progresses, until one of two things happens: 1) The designer view starts to throw OutOfMemory exceptions. Upon loading task manager, I see that VS is using anywhere between 500 and 700 megs of memory. When this occurs, however, I only have two or three documents open. 2) The compiler stops working completely. I get greeted with a message informing me that "The Visual Basic Compiler has stopped working. Visual Studio must close." After restarting and reloading the solution, I can go anywhere from ten seconds to a few hours before this happens again. I never seemed to get these problems when I was working on XP Pro. The other people on our team who are all running XP Pro rarely get the out of memory error, and I've only heard of the Compiler crash occurring once elsewhere. Is this something related to VS 2005 and Vista exclusively? Has anyone else run into this? :confused:
-
Hey all: We recently moved from Visual Studio 2003 to 2005, and about the same time, I got a new workstation - moved from a Sony Vaio laptop running XP Professional to an HP xw4400 with Vista Business. Apart from a few expected hiccups, things were going great, and I wasn't having any major problems. Then things took a nose-dive for the worse. While working on our WinForms project, VS will hang for several seconds for no apparent reason while in code view. It also seems to want to re-draw the entire form whenever I switch to design view, causing another hang. Granted, some of our forms have too much on them for their own good, but when all I have is a few textboxes and a button or two, having to wait 3-5 seconds for the designer to reappear gets annoying. This seems to happen more and more frequently as the day progresses, until one of two things happens: 1) The designer view starts to throw OutOfMemory exceptions. Upon loading task manager, I see that VS is using anywhere between 500 and 700 megs of memory. When this occurs, however, I only have two or three documents open. 2) The compiler stops working completely. I get greeted with a message informing me that "The Visual Basic Compiler has stopped working. Visual Studio must close." After restarting and reloading the solution, I can go anywhere from ten seconds to a few hours before this happens again. I never seemed to get these problems when I was working on XP Pro. The other people on our team who are all running XP Pro rarely get the out of memory error, and I've only heard of the Compiler crash occurring once elsewhere. Is this something related to VS 2005 and Vista exclusively? Has anyone else run into this? :confused:
-
Yeah, I've had Automatic Updates running ever since getting this machine. Of particular interest is the last security update (KB937061)[^] - looking at my update history, it has tried to install 17 times, and failed each time. Every time it fails, it gives me error code 64C, on which a search leads to absolutely nowhere other than a generic installation failure information screen.
-
Yeah, I've had Automatic Updates running ever since getting this machine. Of particular interest is the last security update (KB937061)[^] - looking at my update history, it has tried to install 17 times, and failed each time. Every time it fails, it gives me error code 64C, on which a search leads to absolutely nowhere other than a generic installation failure information screen.
-
Lieutenant Frost wrote:
Yeah, I've had Automatic Updates running ever since getting this machine.
Automatic Updates does not cover VS2005. Make sure you've got all the updates mentioned in the earlier post.
I must have misspoken...I have been checking for updates for everything installed on a regular basis, and every time there has been an update for VS2005, I've been installing them. Hence why I'm confused why the last security update failed. All the updates that were mentioned are installed.
-
I must have misspoken...I have been checking for updates for everything installed on a regular basis, and every time there has been an update for VS2005, I've been installing them. Hence why I'm confused why the last security update failed. All the updates that were mentioned are installed.
If you run Bit Defender Anti-Virus then try disabling it before running the windows update as I have had problems with it blocking the updates before.
Jonathan Wilkes Darka[Xanya.net]
-
Yeah, I've had Automatic Updates running ever since getting this machine. Of particular interest is the last security update (KB937061)[^] - looking at my update history, it has tried to install 17 times, and failed each time. Every time it fails, it gives me error code 64C, on which a search leads to absolutely nowhere other than a generic installation failure information screen.
0x64C is 1612 in decimal which if it's intended to be the Windows error code, means ERROR_INSTALL_SOURCE_ABSENT. That means Windows Installer couldn't find the original source for the product, which it needs to perform the repair (Windows Installer installs patches by applying transforms to the installer database then repairing the product using the information from the modified database). Did you install Visual Studio from a network share? If so, it'll need that share to be present when it repairs the product. Support for security patches is free. Look for the number to call at support.microsoft.com[^].
DoEvents: Generating unexpected recursion since 1991 -
0x64C is 1612 in decimal which if it's intended to be the Windows error code, means ERROR_INSTALL_SOURCE_ABSENT. That means Windows Installer couldn't find the original source for the product, which it needs to perform the repair (Windows Installer installs patches by applying transforms to the installer database then repairing the product using the information from the modified database). Did you install Visual Studio from a network share? If so, it'll need that share to be present when it repairs the product. Support for security patches is free. Look for the number to call at support.microsoft.com[^].
DoEvents: Generating unexpected recursion since 1991Okay...that explains a lot. My only question at this point would be if I need the 2005 upgrade disk or the original 2003 install disk (we install 2003, then run the 2005 upgrade).
-
Hey all: We recently moved from Visual Studio 2003 to 2005, and about the same time, I got a new workstation - moved from a Sony Vaio laptop running XP Professional to an HP xw4400 with Vista Business. Apart from a few expected hiccups, things were going great, and I wasn't having any major problems. Then things took a nose-dive for the worse. While working on our WinForms project, VS will hang for several seconds for no apparent reason while in code view. It also seems to want to re-draw the entire form whenever I switch to design view, causing another hang. Granted, some of our forms have too much on them for their own good, but when all I have is a few textboxes and a button or two, having to wait 3-5 seconds for the designer to reappear gets annoying. This seems to happen more and more frequently as the day progresses, until one of two things happens: 1) The designer view starts to throw OutOfMemory exceptions. Upon loading task manager, I see that VS is using anywhere between 500 and 700 megs of memory. When this occurs, however, I only have two or three documents open. 2) The compiler stops working completely. I get greeted with a message informing me that "The Visual Basic Compiler has stopped working. Visual Studio must close." After restarting and reloading the solution, I can go anywhere from ten seconds to a few hours before this happens again. I never seemed to get these problems when I was working on XP Pro. The other people on our team who are all running XP Pro rarely get the out of memory error, and I've only heard of the Compiler crash occurring once elsewhere. Is this something related to VS 2005 and Vista exclusively? Has anyone else run into this? :confused:
Upon doing some digging after the latest crash (tried opening up a form in design mode -> X|), I found a rather disturbing anomaly in my system - the event viewer service has completely ceased to function. Trying to start it up lands me a sweet new error message:
"Windows could not start the Windows Event Log service on Local Computer. Error 4201: The instance name passed was not recognized as valid by a WMI data provider."Searching the Microsoft forums landed this result, which tempting as it might be, will take a considerable amount of time to complete, not to mention it smells suspiciously like a hack rather than a solution. So...armed with this new knowledge, I kicked over a few more rocks, and I'm starting to suspect that there might be a common thread between this and a few other problems that I've been having as of late: 1) My right monitor will occasionally go completely black for a few seconds (Running an ATI FireMV 2250 card with dual-DVI monitors); 2) Our Proxy server has inexplicably cast me down to what I call "Uzar Akksess" level (i.e. restricted from accessing pretty much EVERYTHING), even though I have verified that my machine has been added to the exemption group, and last but most certainly not least; 3) There are two instances of Visual Studio 2005 installed on my machine, both Professional 2005 and some sort of "Premiere Partner Edition," even though I had performed an upgrade from a 2003 installation with a 2005 upgrade disk. In short, I'm not entirely sure if this is something that is wrong with my machine or just me. Again, these problems didn't crop up on my old XP machine. Odd, ne? -
Okay...that explains a lot. My only question at this point would be if I need the 2005 upgrade disk or the original 2003 install disk (we install 2003, then run the 2005 upgrade).
The 2005 disc. The products are independent - the installer for the upgrade edition of 2005 only does a compliance check when it is initially launched. (If 2003 is not already installed it will ask for disk 1 of the 2003 CD set, so it is possible to install 2005 without also installing 2003.)
DoEvents: Generating unexpected recursion since 1991