The problem is that when I run the setup program from console using SAPWD="(Some password)" SecurityMode=SQL, it fails with that error log:
--- LOG START
2003-08-15 17:56:13.12 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)
2003-08-15 17:56:13.12 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-08-15 17:56:13.12 server All rights reserved.
2003-08-15 17:56:13.12 server Server Process ID is 3076.
2003-08-15 17:56:13.12 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2003-08-15 17:56:13.14 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2003-08-15 17:56:13.18 server SQL Server configured for thread mode processing.
2003-08-15 17:56:13.21 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2003-08-15 17:56:13.29 spid3 Warning ******************
2003-08-15 17:56:13.29 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2003-08-15 17:56:13.87 spid3 Starting up database 'master'.
2003-08-15 17:56:15.76 server Using 'SSNETLIB.DLL' version '8.0.766'.
2003-08-15 17:56:15.76 spid5 Starting up database 'model'.
2003-08-15 17:56:15.87 spid3 Server name is 'ALEX'.
2003-08-15 17:56:15.87 spid3 Skipping startup of clean database id 5
2003-08-15 17:56:15.87 spid3 Skipping startup of clean database id 6
2003-08-15 17:56:15.87 spid3 Starting up database 'msdb'.
2003-08-15 17:56:17.18 spid5 Clearing tempdb database.
2003-08-15 17:56:18.70 server SQL server listening on Shared Memory.
2003-08-15 17:56:18.70 server SQL Server is ready for client connections
2003-08-15 17:56:21.43 spid5 Starting up database 'tempdb'.
2003-08-15 17:56:22.56 spid3 Recovery complete.
2003-08-15 17:56:22.56 spid3 SQL global counter collection task is created.
2003-08-15 17:56:22.93 spid3 Warning: override, autoexec procedures skipped.
2003-08-15 17:56:36.48 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
--- LOG END
if anybody can help, I would really appreciate!
Alex.http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q185/8/06.asp&NoWebContent=1
you should have googled that last line.
This article was previously published under Q185806
BUG #: Windows NT: 17812 (6.50)
SYMPTOMS
A SQL Server computer that is enabled for clustering with Microsoft Cluster Server (MSCS), may experience sudden stops of the SQL Server service and subsequent restarts of the service. The last error log terminates with the following message:
SQL Server terminating due to 'stop' request from Service Control Manager
CAUSE
The Resource DLL for the SQL Server service exports two functions used by the MSCS Cluster Manager to check for availability of the SQL Server resource at predefined intervals. There is a simple check, LooksAlive, that queries the service status through the Windows NT Service Control Manager, and a more stringent check, IsAlive, that connects to SQL Server as user "probe" and performs a simple query to the system catalog. By default, LooksAlive is fired every 5 seconds and IsAlive is fired every 60 seconds.
IsAlive uses a fixed login time-out of 15 seconds to connect to SQL Server. In situations where the server is very busy, SQL Server may fail to respond to the IsAlive login request within this interval. Thus IsAlive returns FALSE to the Cluster Manager, which issues a Terminate request and a subsequent Online request to SQL Server and the SQL Executive Resource DLL which causes both services to be stopped and restarted.
WORKAROUND
Increase the polling interval for SQL Server's IsAlive test in MSCS Cluster Administrator to decrease the chance for this to happen.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server 6.5. For information about how to download and install the latest SQL Server Service Pack, see the following Microsoft Web site:
http://support.microsoft.com/highlights/sql.asp
For more information, contact your primary support provider.
MORE INFORMATION
If you experience sudden SQL Server restarts in a cluster environment and are unsure of the cause, enable MSCS logging by restarting the MSCS service with the system environment variable "Clusterlog=<path>". MSCS will now log all activity in the specified log file. There you will find, among others, all calls to LooksAlive and IsAlive and their outcome. In a situation where the login fails you'll find the following message in the log:
[sql65res] CheckQueryProcessorAlive: dbopen failed|||I just upgraded to XP pro, was able to get IIS running and figured out how to browse to the server on my home network from another computer.
The goal is simply to follow the instructions when setting up the ASP CSK.
I downloaded and installed MSDE receiving the same error log as shown above.
How do I...
Increase the polling interval for SQL Server's IsAlive test in MSCS Cluster Administrator to decrease the chance for this to happen.
if the only thing I have is MSDE through the ASP.net link? And according to the error log, it isn't installed, because it was 'stop'ped.
Thanks,
Chris
No comments:
Post a Comment