My Windows 2008 R2x64 server is running a SA184.108.40.20627 database server.
For no reason, the server crashed with no log information about the crash.
There is nothing at console log file and no mini dump file was generated.
The only log available is the Windows Event Viewer Application Log, copied as follows:
Faulting application name: dbsrv11.exe, version: 220.127.116.1127, time stamp: 0x4e0536dd Faulting module name: dbserv11.dll, version: 18.104.22.16827, time stamp: 0x4e0536c2 Exception code: 0xc0000417 Fault offset: 0x00000000005a6c38 Faulting process id: 0xaf0 Faulting application start time: 0x01cc39b5b67152d6 Faulting application path: C:\Program Files\SQL Anywhere 11\Bin64\dbsrv11.exe Faulting module path: C:\Program Files\SQL Anywhere 11\Bin64\dbserv11.dll Report Id: 56adb6c4-bc59-11e0-ae97-00155d830172
The problem was solved by Sybase Engineering as folows:
QTS #681398 - Server could crash while using UNLOAD statement to unload data to a file.
The correction was addressed at build #2661.
EDIT: Full description (with interesting details, methinks):
This may sound a bit old-school, but hardware failures can cause otherwise-unexplainable application and system crashes. Unhandled memory errors are the most common hardware source, but blown-out capacitors on the system board have also caused problems.
If you can afford some system down-time, try testing the memory and visually inspecting for failed capacitors (look for bulged ends or any sign of fluid leakage).
answered 17 Sep '11, 21:00
This is a STATUS_INVALID_CRUNTIME_PARAMETER exception. You say, that no dump is created, so it might be, that the exception is thrown as a result of trying to call _invoke_watson to dump the real exception. Which would mean, that the information necessary for Sybase to identify any flaw is obscurred by this subsequent error.
answered 20 Sep '11, 03:00