Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Server now stops after applying Windows 98 updates

Status
Not open for further replies.

Hap007

MIS
Mar 21, 2003
1,018
US
Help,

I have SQL Server 2000 running on Win 98 PC that I use for some development.

Ok so far. It has worked great for 2 years.

Then, I decided to download, from Microsoft site, all the updates for windows 98. (What a mistake that was)

Now, SQL Server stops every hour or 2. I can not figure out how to examine or change settings short of reinstalling SQL. I would prefer not to do that. WHo nows what might happen to my test environment.

Anybody know why?

FYI:
1) No problem on my Win 2000 box or my Win XP Box. (even after Windows does the update process)
2) Each System runs own Desktop Version of SQL (All development PCs)

Thanks,
Hap Access Add-on developer [pc] - [americanflag]
 
Have you tried looking in the sql event log files?

they are plain textfiles that should be found in the log subdirectory that by default is in the same place as your sql data directory.

 
flutepir,

Thanks, I examined the latest logs, per your recommendation.

It appears that something is failing, a dmp occurs and that fails.
I have inclued a small portion of the log.

Note:
1) This did not happen before updating my window 98 software.
2) This occurs even if I am not using SQL. Just starting SQL and letting it sit idle for over an hour causes this. On the other hand, if I stop and restart each hour, well all is fine.

Thanks,
Hap

Partial Log:
2003-04-01 13:02:40.90 server SQL Server is ready for client connections
2003-04-01 13:02:40.91 spid3 Skipping startup of clean database id 4
2003-04-01 13:02:40.91 spid3 Skipping startup of clean database id 5
2003-04-01 13:02:40.92 spid3 Skipping startup of clean database id 6
2003-04-01 13:02:40.92 spid3 Skipping startup of clean database id 7
2003-04-01 13:02:40.92 spid3 Skipping startup of clean database id 8
2003-04-01 13:02:40.92 spid3 Skipping startup of clean database id 9
2003-04-01 13:02:40.93 spid3 Skipping startup of clean database id 10
2003-04-01 13:02:40.95 spid3 Skipping startup of clean database id 11
2003-04-01 13:02:40.95 spid3 Skipping startup of clean database id 12
2003-04-01 13:02:40.95 spid3 Skipping startup of clean database id 13
2003-04-01 13:02:40.95 spid3 Skipping startup of clean database id 14
2003-04-01 13:02:40.95 spid3 Starting up database 'ABS_db'.
2003-04-01 13:02:41.26 spid5 Clearing tempdb database.
2003-04-01 13:02:41.61 spid3 13 transactions rolled forward in database 'ABS_db' (15).
2003-04-01 13:02:41.83 spid3 0 transactions rolled back in database 'ABS_db' (15).
2003-04-01 13:02:41.91 spid3 Recovery is checkpointing database 'ABS_db' (15)
2003-04-01 13:02:42.18 spid5 Starting up database 'tempdb'.
2003-04-01 13:02:42.39 spid3 Recovery complete.
2003-04-01 14:20:43.20 server Using 'sqlimage.dll' version '4.0.5'
Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL\log\SQL00016.dmp
2003-04-01 14:20:43.22 server SqlDumpExceptionHandler: Process -543225 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
*******************************************************************************
*
* BEGIN STACK DUMP:
* 04/01/03 14:20:43 spid 0

Now a large dump........................ Access Add-on developer [pc] - [americanflag]
 
Do you have any scheduled jobs in sql agent or task scheduler?

C0000005 is usually a memory access violation a program (not neccesarily sql server) tried to access a memory address that did not belong to it.

These are extremly hard to diagnose.

I would try going to msdn.microsoft.com/sqlserver and searching the knowledge base for the error and error number.
 
Is the latest service pack for SQL Server installed. Known access violations are usually corrected in service packs.

The MDAC components may have been updated with the WIN98 update. See the following article.


See Neil Pike's SQL FAQ for more information about debugging access violation errors in SQL Server.

If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
 
Thanks,

No, I have not tried the latest patches to SQL yet.

Heck, everything was working perfect, my 4 year old original Windows 98 and my 3 year old SQL Server.

Then, for what ever reason (I got a wild bug), I decided to download and install all the latest patches to Windows 98.

Internet Explorer then failed to show graphics.
My associations to gif and jpeg got messed up.

Then, SQL Server started failing. Nothing running, just start SQL and after the PC sits for 20 or 30 minutes, it fails.

So I am very cautious about other patches.

Now, on my Win2000 PC and My Win XP system, I install updates every week, but I wish I had left my Win 98 PC alone.

Oh well, I guess you can detect frustration. Heck, I have lost almost a day's time (8 hours) trying to fix things after doing the Win 98 patch. I just wish I left it alone.

Thanks For the Reply,
Hap
Access Add-on developer [pc] - [americanflag]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top