February 2, 2006 at 2:18 pm
Hi all,
Everything is fine until today.
I have two instances(both msde databases, but I have enterprise manager and analyser installed) on my computer one instance is mssql and the other is mssql$netsdk (asp.net starter kit database)
somehow the connection to mssql$netsdk is failed which display in enterprise manager.
So I removed the origianl server registration and start a new one, I type "BETTYPC\NETSDK" as server and using windows authentication when doing the registration, but the message display at the last step:
sql server registration failed because of connection failure displayed below:sqldumpexceptionhandler :process 53 generated a fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION, sql server is terminating this process.
what's the problem?
Can you help and I am desperated
February 3, 2006 at 4:50 am
i tried recreating your problem but did not get the error.[maybe if your post the exact steps you are taking and especially the variables you are inputing i can see if the situation can be helped]
maybe first apply the latest service pack for sql on your machine and try again.this is an ms product after all
February 3, 2006 at 11:01 am
Bledu,
I think you are right. My problem is I usually don't check what's the service pack I need to apply at the right time. Sometime I am afraid of doing apply patch. I sometimes got trouble by applying patch. what's the best strategy to decide you should apply patch or you can wait.
I only apply patch when something went wrong and I have to apply.
here is one of the errorlog, I don't know if this has to do with netlibs patch
I later fixed the problem by stop mssql$netsdk and restarted(it somehow stopped automatically) and then I have to restart the computer and then register the server. The connection is fine.
2006-02-02 13:13:09.36 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2006-02-02 13:13:09.36 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-02-02 13:13:09.36 server All rights reserved.
2006-02-02 13:13:09.36 server Server Process ID is 2664.
2006-02-02 13:13:09.36 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2006-02-02 13:13:09.38 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2006-02-02 13:13:09.56 server SQL Server configured for thread mode processing.
2006-02-02 13:13:09.56 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2006-02-02 13:13:09.58 spid2 Starting up database 'master'.
2006-02-02 13:13:09.63 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-02-02 13:13:09.63 spid5 Starting up database 'model'.
2006-02-02 13:13:09.64 spid2 Server name is 'BETTYPC\NETSDK'.
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 4
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 5
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 6
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 7
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 8
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 9
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 10
2006-02-02 13:13:09.64 spid2 Skipping startup of clean database id 11
2006-02-02 13:13:09.64 spid2 Starting up database 'subway'.
2006-02-02 13:13:09.75 spid5 Clearing tempdb database.
2006-02-02 13:13:10.77 server SQL server listening on .
2006-02-02 13:13:10.77 server Error: 17826, Severity: 18, State: 1
2006-02-02 13:13:10.77 server Could not set up Net-Library 'SSNETLIB'..
2006-02-02 13:13:10.77 server Unable to load any netlibs.
2006-02-02 13:13:10.77 server SQL Server could not spawn FRunCM thread.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply