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.After this are you not able to start MSSql services on the computer? What is the version of ssnetlib.dll, sqlservr.exe?
-Kashif|||No.
The only usefull files i can find under the "Microsoft SQL Server" directory that the setup creates, are the log files.
When the setup program fails, it goes backward, in a sort of rollback and it deletes any other files it had installed during the installation process.
That's why, I think, I can't find any of those files you are talking about (ssnetlib.dll and sqlservr.exe) on my computer.|||Do you have some dbs in the DATA dir under the sql server install folder - if yes please move that some place else before starting setup.
Hope that helps
Kashif|||The only files I have in the DATA dir are tempdb.mdf and templog.ldf|||Can you move these dbs to a different directory on your machien and then try the MSDE installation.
-Kashif|||ok..
I moved them all in a different location so that the DATA directory was empty... didn't work.
The log file still report the same error.
I looked on the net and i found out i'm not the only one with that problem, but i couldn't find anyone who could provide a solution.
What can I do?|||Any ideas?|||Ok..
I found by myself what was wrong..
I'm running Windows XP home edition, while the professional edition is needed.
Hope this will help people with the same problem.
No comments:
Post a Comment