October 3, 2008 at 8:00 am
When launching SSMS, it dispayed, then quickly disappeared. In the event log I saw
Faulting application sqlwb.exe, version 2005.90.3042.0, stamp 45cd69e0, faulting module msvcr80.dll, version 8.0.50727.1433, stamp 471eb5ae, debug? 0, fault address 0x0001500a.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
in the event log.
Anyone can help me?
October 15, 2008 at 6:05 am
I am getting the same error when running SSMS. I did a repair on .NET 2.0 in Add/Remove programs and in the past this fixed the problem but this time it did not fix it.
Has you been able to fix this problem yet?
October 15, 2008 at 7:06 am
Thank you for your reply.
Some articles mentioned to re-install .net 2.0 framework, but I did not try it yet since if so I can live without SSMS on it.
October 16, 2008 at 3:08 am
The version you mention is quite old. I'd say its a fair bet that upgrading .Net Framework 2.0 to SP1 and your SQL tools to SP2 will probably help.
October 16, 2008 at 6:53 am
we had .net 2.0 sp1 and sql sql sp2 installed.
October 16, 2008 at 7:07 am
You're quite right. that is the SP1 version.
I find repairing rarely helps. I guess I'd try an uninstall / reinstall of .Net framework next.
I have a fair number of servers with both applications installed and have never seen this error.
Sorry, don't have anything else to suggest...
October 16, 2008 at 8:36 am
Have a look at this:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3457121&SiteID=1
And by the way msvcr80.dll is the MS C runtime library, nothing to do with .NET
October 16, 2008 at 8:56 am
Thanks it solved the issue.
January 16, 2009 at 9:20 am
Pei Zhu,
How did you solve the issue?
January 16, 2009 at 4:46 pm
The link above provided solution.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply