>First, check both the NT event log and the SQL Server error logs for anything obvious.
>
>If you don't see anything strange there, use SQL Profiler to capture everything submitted to the server. Run your app. Check the trace results for anything. Specifically, look to see if anyone has submitted the SHUTDOWN statement to the server.
>
>Good luck.
>
>-Mike

I'd like to add to this that it would be easier to catch the moment when the SHUTDOWN statement is issued if you ensure that the user who logs in to the SQL server does not have system administrator privileges.

Best wishes, Michael