August 3, 2010 at 11:28 pm
when i open my management studio and click on connect ... The mgmt studio is getting closed immediately can you help me on this?????
August 4, 2010 at 12:35 am
August 4, 2010 at 12:54 am
virus update is happening daily so i think there should be some other issue.....even in error log file there is no entry for this
August 4, 2010 at 2:45 am
Do you see any error messages in the Application\System Event logs?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
August 4, 2010 at 5:33 am
premkuttan.lakshmanan (8/4/2010)
virus update is happening daily so i think there should be some other issue.....even in error log file there is no entry for this
It can be something corrupted at the SQL system files! Reinstall can be a solution! This SSMS issue is in your local machine or in production server!? If you have that problem in your local machine, just try to reinstall the SQL Server again, of course you should pay attention to backup something that you need after reinstall, (DBs, users etc etc).
August 4, 2010 at 5:41 am
I don't think you would need to reinstall everything just the Client Tools!
August 4, 2010 at 7:14 am
Can you open up remote desktop, hit your dev server, and open up SSMS that way?
If so, I tend to agree that there might be something going on with the client tools on your machine. But also try these tricks first before you reinstall.
If you used the shortcut on your desktop, try opening it up through the start menu.
If you opened up with the start menu, try the shortcut on your desktop.
Find the .exe file for SSMS in Windows explorer and open it up that way.
Still getting the same problem? Try rebooting your machine. It could be a problem with your Windows profile instead of with SSMS.
Check your Event Viewer for System and Application errors/warnings related to SSMS. Look for the date and time in which you opened up SSMS.
If all this doesn't help you, then try reinstalling the client tools.
August 5, 2010 at 1:28 am
When i try to open the ssms
In application log it shows 2 line items
1) .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)
2)Faulting application sqlwb.exe, version 2005.90.3042.0, stamp 45cd69e0, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? 0, fault address 0x000055fc.
but as a work around i am opening SSMS in another server and connecting this instance but only on this server i am not able to connect
August 5, 2010 at 7:31 am
Apparently, other people have had problems with that .DLL and sometimes it's related to the .Net Framework.
Check this link for more details.
Also, google "Faulting application sqlwb.exe". There are a ton of links for this problem.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply