I am running SQL Server 2012 Express 64-bit (SP2 CU9) on Windows 8.1 Pro. Application of SP3 failed. The GUI shows:
The process appeared to run to completion and then fail at the very end, apparently because it could not start the instance. From the Windows Application Event Log:
Faulting application name: sqlservr.exe, version: 2011.110.6020.0, time stamp: 0x5626ed31
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18007, time stamp: 0x55c4c341
Exception code: 0xe06d7363
Fault offset: 0x000000000000871c
Faulting process id: 0xeb4
Faulting application start time: 0x01d14003da18532c
Faulting application path: c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 181d161a-abf7-11e5-821d-00a0d1ad0b0b
Faulting package full name:
Faulting package-relative application ID:
From the SP3 setup summary log:
Overall summary:
Final result: The patch installer has failed to update the following instance: SQLEXPRESS. To determine the reason for failure, review the log files.
Exit code (Decimal): -2061893607
Instance SQLEXPRESS overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): -2061893607
When I tried to start SQL Server manually like this:
C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn>sqlservr -c -s SQLEXPRESS
I got this:
2015-12-26 13:06:59.79 Server Error: 17311, Severity: 16, State: 1.
2015-12-26 13:06:59.79 Server SQL Server is terminating because of fatal ex
ception c06d007e. This error may be caused by an unhandled Win32 or C++ exceptio
n, or by an access violation encountered during exception handling. Check the SQ
L error log for any related stack dumps or messages. This exception forces SQL S
erver to shutdown. To recover from this error, restart the server (unless SQLAge
nt is configured to auto restart).
2015-12-26 13:06:59.89 Server Using 'dbghelp.dll' version '4.0.5'
2015-12-26 13:06:59.96 Server **Dump thread - spid = 0, EC = 0x000000000000
0000
2015-12-26 13:06:59.96 Server ***Stack Dump being sent to c:\Program Files\
Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\LOG\SQLDump0072.txt
By the way, uninstalling SP3 does return the system to the previous (SP2 CU9) working state. I have done it at least twice but I will leave my broken SP3 in place while I (hopefully) resolve this issue with your help.
What do I do next? In particular, what should I do with the stack dump?