error 1067

I'm using MSDE2000sp3 and I can't get the service to start. The error that I
get is, 'error 1067 The process terminated unexpectedly'. Can anyone tell me
why I get this error. Please help.
hi,
vz wrote:
> I'm using MSDE2000sp3 and I can't get the service to start. The error
> that I get is, 'error 1067 The process terminated unexpectedly'. Can
> anyone tell me why I get this error. Please help.
please verify your errorlog file for the cause of the problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Error : Timeout expired. The timeout period elapsed...

Hi,

Iget this error from our web application every once in a while. " Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding". I emailmyself when an error occurs, and once every 2-3 days I get this timeouterror emails, like 5-10 emails in a span of few minutes. Then it goesaway. I have set the command timeout for 60 secs.

Itdoesn't happen from the same stored procedure, actually I have seen ittimeout from really simple 1 or 2 line stored procedures, which shouldn't normally take 1 sec. Its likesql server just shuts down for few minutes. We have somebackups and maintenance jobs scheduled, but they run only aftermidnight. I have checked theapplication event viewer, there are no warnings orerror messages forMSSQLSERVER.

Canany one tell me how to check whats going on during that short timespanwhen timeout error occurs, and what causes it? I don't want to run sqlprofiler continuously for 2-3 days, I am afraid it will slow down theserver more.

Thanks.

It could be locking|||Sorry, that was a bit laconic. I meant it could be table (or page) locking. I don't think you can do much without running the profiler or at least a good error logging so that you would isolate the scenario. In the mean time you could be looking for concurent access to those records|||

websolutions:

Sorry, that was a bit laconic. I meant it could be table (or page) locking. I don't think you can do much without running the profiler or at least a good error logging so that you would isolate the scenario. In the mean time you could be looking for concurent access to those records

I agree read the performance tuning tips in the link below and run SQL Server profiler to find out what is causing your error. Hope this helps.

http://msdn.microsoft.com/msdnmag/issues/06/07/WebAppFollies/default.aspx