Sql Server Stops Unexpectedly

[iansr]

For some reason my SQL Server stops randomly. I enabled both 'Autostart SQL Server if it stops unexpectedly' & 'Autostart Sql Server Agent if it stops unexpectedly' and 'Autostrart Sql Server agent when OS starts'.
However, the problem persists, sometimes after I leave the computer/test server idle, sometimes even when I am coding.

I am using Win2K advanced server with all the latest patches from windows update.

Please help me, I want to keep Sql Server running at all times.

 

[Inwoner]

First, go and look at Windows Application and System log, and also at SQL Server's log.

Their might be a tip on why it shuts down automatic.

Let me know if you have found anything

 

[iansr]

The only thing negative is can decipher is this:
It occurs on the last entry of all 6 Archives in the SQL Server logs.

process_commands: Process 1728 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.


the Process number changes across all six Archives. the only applications i have running are Dreamweaver MX & IE. No system-bar application of any sort.

 

[Inwoner]

I assume the Process is the Windows PID as seen in the task manager.

I am almost certain that your process will be SQL server. I recommend that you uninstall and reinstall your SQL Server installation - but their might be other ways to resolve this.

Question - can you give me a little background on your SQL server, the number of connection, etc.

 

[iansr]

I was thinking about that. (reinstall) But id like to resolve this in another way so that in the event that it happens again, i will have a solution.


Funny cuz this hasn't happened to me before, in my previous SQL Databases.

On the development server (where I am having problems) I am running SQL Server 7.0. I didnt change anything from the default installation settings except the password for sa. All other settings are the same as the defaults. As of the moment, there are around 5 other users aside from myself accessing this server. All access to the db are through stored procs. No jobs/Alerts have been created.

And if it helps, I am using ASP.NET C# to call those stored procs from within assemblies.

 

[Inwoner]

I am sorry,
One other solution (just) might be to rebuild your master database. I do not know how it will contribute to fixing your problem, but it might work, you'll never know.