|
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. |
|
Will the version 9 odbc crash the asa12 database? 1
I do not know that this issue was the direct cause. I was listing all the things I was able to find as a result of the logging, which prompted me to update our app, the ODBC driver, and the server with the latest EBFs. The real lesson was not to trust a client saying everything was up to date, but instead log the connections and check for yourself.
(26 Aug '11, 10:54)
Siger Matt
In general, you can connect with older clients to newer servers. For all current SA versions, clients from v6 and above should be able to connect (though they might not be able to use all newer client facilities like Unicode, Kerberos, connection pooling and the like). So a v9 client should not crash the database... Have a look at the comments on this DCX page.
(26 Aug '11, 12:01)
Volker Barth
|
Did the server create a dump file when it crashed?
If you are asking about SA generating a dump file, I do not know how to check that. If you are asking about the server itself (like a blue-screen dump file), it did not crash. The application reports a communication error, I log in to the server and the service is stopped, and the event log has an entry "XYZ service has terminated unexpectedly." But the rest of the server seems fine and no other problems are reported.