One of our clients is using version 12, build 2601.
We run the database as a Windows service on their 2008 Server.
Starting Jan 03 the service crashes with an event in the Windows event log "Service has terminated unexpectedly. The first time I restarted it, it stayed up for 2 weeks. After the next crash about 5 days, and now it has happened twice this week.
Beyond the Windows event log, which does not show any correlated events, what is the best way to diagnose what is happening just before the crash?
We have multiple clients with this setup and only one is having this problem, so I strongly suspect the environment, but I have to prove it. Any thoughts on what in the environment would cause this would also be helpful.
asked 20 Jan '11, 20:16
If the server did catch the crash and generate a dump file, you should be able to see these by executing
If the -lc option has anything listed, you can try to submit these using
The dumps themselves need to be analyzed by an engineer and the easiest way to get this to happen is to open a support case, and provide your case contact with the submission IDs from running dbsupport -ls.
That being said, the server dumps are often minimal and won't always give us the picture we need to determine what the problem is. We may ask for more info.
What you may want to check for yourself is server output messages before the crash occurs; these are output to a file using "-o server_log.txt" in the command line arguments if you are not already doing so.
If you find an assertion in the output log, you will likely want to try rebuilding a copy of the database, and seeing if the crash no longer occurs.
It could be that there are also other errors that occur in the output log, these will usually be prefixed with a E. on the line.
If you do have any trouble finding the cause of the crash, I would recommended opening a support case for investigation.
Will the version 9 odbc crash the asa12 database?
answered 26 Aug '11, 00:45