SSMS.EXE shuts down upon start.

Question

 

SQL Server management studio shows the splash screen, then stops.  Curious as to what was happening I hooked cdb and ran it.

Here is the debugger output:

 

C:\Program Files\Microsoft SQL Server>cdb ssms.exe

Microsoft (R) Windows Debugger Version 6.8.0004.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: ssms.exe
Symbol search path is: SRV*C:\Utils\Debuggers\Symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is:
ModLoad: 00000000`00860000 00000000`0099e000   Ssms.exe
ModLoad: 00000000`77950000 00000000`77ad0000   ntdll.dll
ModLoad: 00000000`77af0000 00000000`77c50000   ntdll32.dll
ModLoad: 00000000`75c40000 00000000`75c85000   C:\Windows\system32\wow64.dll
ModLoad: 00000000`75bf0000 00000000`75c3e000   C:\Windows\system32\wow64win.dll
ModLoad: 00000000`75b40000 00000000`75b49000   C:\Windows\system32\wow64cpu.dll
(1ba8.1b78): Break instruction exception - code 80000003 (first chance)
ntdll!DbgBreakPoint:
00000000`77994ea0 cc              int     3
0:000>

 

0:000> g
ModLoad: 00000000`77750000 00000000`7787b000   WOW64_IMAGE_SECTION
ModLoad: 00000000`765c0000 00000000`766d0000   WOW64_IMAGE_SECTION
ModLoad: 00000000`77750000 00000000`7787b000   NOT_AN_IMAGE
ModLoad: 00000000`77880000 00000000`7794d000   NOT_AN_IMAGE
ModLoad: 00000000`765c0000 00000000`766d0000   C:\Windows\syswow64\kernel32.dll
ModLoad: 00000000`74050000 00000000`740eb000   C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1801_none_d08
8a2ec442ef17b\MSVCR80.dll
ModLoad: 00000000`762c0000 00000000`7636a000   C:\Windows\syswow64\msvcrt.dll
ModLoad: 00000000`74130000 00000000`7414b000   C:\Windows\WinSxS\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.1801_none_d1c
25e38435be7bf\ATL80.DLL
ModLoad: 00000000`75df0000 00000000`75eb6000   C:\Windows\syswow64\ADVAPI32.dll
ModLoad: 00000000`75d00000 00000000`75df0000   C:\Windows\syswow64\RPCRT4.dll
ModLoad: 00000000`75ca0000 00000000`75d00000   C:\Windows\syswow64\Secur32.dll
ModLoad: 00000000`768b0000 00000000`76980000   C:\Windows\syswow64\USER32.dll
ModLoad: 00000000`76010000 00000000`760a0000   C:\Windows\syswow64\GDI32.dll
ModLoad: 00000000`76170000 00000000`762b4000   C:\Windows\syswow64\ole32.dll
ModLoad: 00000000`776c0000 00000000`7774d000   C:\Windows\syswow64\OLEAUT32.dll
ModLoad: 00000000`76b10000 00000000`7761f000   C:\Windows\syswow64\SHELL32.dll
ModLoad: 00000000`76850000 00000000`768a8000   C:\Windows\syswow64\SHLWAPI.dll
(1ba8.1b78): WOW64 breakpoint - code 4000001f (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ntdll32!DbgBreakPoint:
00000000`77b00004 cc              int     3
0:000:x86>

 

0:000:x86> g
ModLoad: 00000000`77620000 00000000`77680000   C:\Windows\SysWOW64\IMM32.DLL
ModLoad: 00000000`75f40000 00000000`76008000   C:\Windows\syswow64\MSCTF.dll
ModLoad: 00000000`76370000 00000000`76379000   C:\Windows\syswow64\LPK.DLL
ModLoad: 00000000`75ec0000 00000000`75f3d000   C:\Windows\syswow64\USP10.dll
ModLoad: 00000000`75640000 00000000`757de000   C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001
.18000_none_5cdbaa5a083979cc\comctl32.dll
ModLoad: 00000000`727f0000 00000000`72870000   C:\Windows\SysWOW64\uxtheme.dll
ModLoad: 00000000`10000000 00000000`10006000   C:\Program Files (x86)\BPK\bpkhk.dll
ModLoad: 00000000`760e0000 00000000`76164000   C:\Windows\syswow64\CLBCatQ.DLL
ModLoad: 00000000`76980000 00000000`76b0a000   C:\Windows\syswow64\SETUPAPI.dll
ModLoad: 00000000`74570000 00000000`7457a000   C:\Program Files (x86)\Microsoft SQL Server\100\Shared\instapi10.dll
ModLoad: 00000000`745d0000 00000000`745e5000   C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlboot.dll
ModLoad: 00000000`75ae0000 00000000`75afe000   C:\Windows\SysWOW64\USERENV.dll
ModLoad: 00000000`71f10000 00000000`71fca000   C:\Windows\SysWOW64\PROPSYS.dll
ModLoad: 00000000`50000000 00000000`508d0000   C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ms
env.dll
ModLoad: 00000000`75b30000 00000000`75b38000   C:\Windows\SysWOW64\VERSION.dll
ModLoad: 00000000`72500000 00000000`7255f000   C:\Windows\SysWOW64\SXS.DLL
ModLoad: 00000000`75940000 00000000`7597b000   C:\Windows\SysWOW64\rsaenh.dll
ntdll!ZwTerminateProcess+0xa:
00000000`77995d3a c3              ret
0:000>

 

0:000> lmvmssms
start             end                 module name
00000000`00860000 00000000`0099e000   Ssms       (deferred)
    Image path: Ssms.exe
    Image name: Ssms.exe
    Timestamp:        Fri May 30 00:31:29 2008 (483FAD51)
    CheckSum:         00144634
    ImageSize:        0013E000
    File version:     2007.100.1442.32
    Product version:  10.0.1442.32
    File flags:       8 (Mask 3F) Private
    File OS:          40000 NT Base
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft SQL Server
    InternalName:     SSMS
    OriginalFilename: SSMS.EXE
    ProductVersion:   10.0.1442.32
    FileVersion:      2007.0100.1442.032 ((SQL_PreRelease).080529-2343 )
    FileDescription:  SSMS - SQL Server Management Studio
    LegalCopyright:   Microsoft Corp. All rights reserved.
    LegalTrademarks:  Microsoft SQL Server is a registered trademark of Microsoft Corporation.
    Comments:         SQL
0:000>

 

 

Any suggestions?

 

 

 

Answer 1

Oops!  I forgot to post the stack at the WOW64 breakpoint:

 

 

0:000:x86> ~*kv

.  0  Id: 198c.111c Suspend: 1 Teb: 00000000`7efdb000 Unfrozen
ChildEBP          RetAddr           Args to Child
002af948 77b5e78e 768b4a29 77b14c52 77b14040 ntdll32!DbgBreakPoint (FPO: [Non-Fpo])
002af97c 77b46beb 7efdd000 7efde000 77bda118 ntdll32!LdrpDoDebuggerBreak+0x31 (FPO: [Non-Fpo])
002afae0 77b5ed65 002afb70 77af0000 768b4819 ntdll32!LdrpInitializeProcess+0x1229 (FPO: [Non-Fpo])
002afb4c 77b26639 002afb70 77af0000 00000000 ntdll32!_LdrpInitialize+0xf2 (FPO: [Non-Fpo])
002afb5c 00000000 002afb70 77af0000 00000000 ntdll32!LdrInitializeThunk+0x10 (FPO: [Non-Fpo])
0:000:x86>

 

 

Answer 2

Have you tried repairing through setup yet?

 

Answer 3

In addition to Richard's question - Is this an upgrade of a CTP installation?

 

Thanks!

 

Buck Woody, SQL Server Program Manager

 

Answer 4

Also, you can try this:

 

1)    From the command line:  “ssms.exe /setup /selfreg”

2)    Start ssms normally

Answer 5

Hi,

I have tried a CTP of SQL Server 2008 in parallel with SQL Server 2005 Enterprise. There was no problem until I uninstalled the CTP. SSMS 2005 is no longer able to create a project (ssmssqlproj).

 

I get a simple error in the status bar of SSMS: "Project Creation Failure". I also noticed the MIME type was messed up in Vista Explorer - the extension (ssmssqlproj) was no longer registered in Vista, and I was prompted to select the MIME type on open. Any thoughts?

 

Answer 6

Hi,

 

That post about the SSMS.EXE /SETUP /SELFREG fixed my problem too, but I had to use:

 

C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\sqlwb.exe /setup /selfreg