Answered by:
Having persistent message "WWT encountered a problem and needs to close"

Question
-
I have cleaned my registry, but it didn't solve the problem. I run Windows XP SP 3 @ dual core 3.40 GHz. The error description contains the following info: Event Type clr20r3 P2: 3.0.76.1 P3: 4f099ec
Exception info: Code: 0xe0434f4d Address: 0x000000007c812afb
Can I fix it?
Sunday, May 6, 2012 9:27 PM
Answers
-
There have been reports of the .NET settings file getting corrupted when WWT is running during a forced Windows Shutdown.
The problem is that while WWT is shutting down .NET save the confiruration settings that changed, if during the save WWT is forcibly quit during the shutdown, the file may be only partially written and can become corrupt. When WWT launches next, .NET tries to load the settings and crashes before any of WWT's code can actually run, so we can't work around the error or change what error message is given.
If this is the issue it can be addressed by deleting the settings directory or WWT.
Find the directories that start with wwtexplorer.exe in the settings folder and delete them.
On Vista and Windows 7
c:\users\{your user name}\AppData\local\Microsoft_Research
On Windows XP
C:\Documents and Settings\{your user name}\Local Settings\Application Data\Microsoft_Research
Your settings folders might not be in c:\ so you might need to change the drive letter but 99% of the time they are.
Jonathan
- Marked as answer by Jonathan Fay - WorldWide Telescope ArchitectMicrosoft employee, Moderator Wednesday, May 23, 2012 4:39 PM
Monday, May 14, 2012 7:47 PMModerator
All replies
-
Can you please be more specific about when this happens. At launch time? During running?
Did this just start?
The most common problem that causes this is when the user ignores and cancels the Directx 9.0c setup that is part of the overall WWT setup, thinking they alreayd have another DX version installed. If this is the case, re-run setup and make sure Direct X installs.
If not please give me more details.
thanks
Joanthan
Sunday, May 6, 2012 11:22 PMModerator -
Hello, Jonathan.
I have reinstalled the DirtectX 9.0C, but it didn't solve the problem. This messge appears at the start of the program, and I 've just sent this error report to your investigation center again. In fact, I used to have an older version of WWTelescope, but I couldn't find uninstaller, so I decided to remove it by using Windows "Add/remove programs" in the Control Panel. Maybe that was the case? What should I do? I indended to use this program for ASCOM control of my telescope.
Wednesday, May 9, 2012 8:34 AM -
I am sorry, but this is still actualThursday, May 10, 2012 10:09 AM
-
There have been reports of the .NET settings file getting corrupted when WWT is running during a forced Windows Shutdown.
The problem is that while WWT is shutting down .NET save the confiruration settings that changed, if during the save WWT is forcibly quit during the shutdown, the file may be only partially written and can become corrupt. When WWT launches next, .NET tries to load the settings and crashes before any of WWT's code can actually run, so we can't work around the error or change what error message is given.
If this is the issue it can be addressed by deleting the settings directory or WWT.
Find the directories that start with wwtexplorer.exe in the settings folder and delete them.
On Vista and Windows 7
c:\users\{your user name}\AppData\local\Microsoft_Research
On Windows XP
C:\Documents and Settings\{your user name}\Local Settings\Application Data\Microsoft_Research
Your settings folders might not be in c:\ so you might need to change the drive letter but 99% of the time they are.
Jonathan
- Marked as answer by Jonathan Fay - WorldWide Telescope ArchitectMicrosoft employee, Moderator Wednesday, May 23, 2012 4:39 PM
Monday, May 14, 2012 7:47 PMModerator -
Thank you very much, Jonathan. I've just erased the contents of that folder. And I'm going to reinstall WWTelescope soon - will tell about the outcome. Actually, that Microsoft Research settings folder contained only one 2 KB file...Wednesday, May 16, 2012 4:29 AM