October 10, 2002 at 11:19 am
HELP!!!
I have scoured the Internet looking for answers. I've followed ALL suggestions from ALL sources and have not found the answer to my problem.
I have repeatedly attempted to install SQL Server 7 MSDE version onto my Win 2000 Prof. system, and have continually gotten errors.
I have:
1. Logged on as Administrator
2. Cleared out previous installation "dead wood" from my Registry
3. Disconnected from my IIS whose tasks were all Stopped.
4. Deleted my entire previous C:\MSSQL7 directory
5. If found, attempted to Un-Install previous erroneously listed SQL Server 7 from my Installed Programs. Most often the UnInstall met with failure.
I'm totally at a loss as to how to proceed. I need to get the MSDE installed so that I can begin to work with my MS Visual Studio 6.0
HELP!!!!!
Thanks,
jrb
October 11, 2002 at 6:10 pm
I've heard (but in a quick look didn't see it documented) you cannot install MSDE on any server that had SQL on it. I have no idea what settings it checks, but given the number of places that a SQL install affects it would be pretty darn hard to remove all traces.
On a probably unrelated note, we have not been able to ever successfully install MSDE on a domain server. If we demote it, install, and promot it then everything works, but otherwise we get things so screwed up that they generally wipe it and reinstall windows (I do not think that was necessary but the two times I am familiar with they were under the gun and they knew they could make that work).
October 11, 2002 at 7:32 pm
I am not certain I understand what you mean by "install MSDE on a Domain Server". Are you referring to the Default installation setting which I have continued to use in hopes that it would create less problems?
=====================================
Once again I tried all suggestions and, once again, it did not work!!!
I did EVERYTHING suggested for pre-Installation "housecleaning" to remove info from previous failed installation attempts.
* Erase C:\MSSQL7 directory
* Purge related Registry Entries
* etc. (see list in initial posting)
I then logged in as Administrator and re-tried the MSDE Installation with all Default installation settings -- Failed to Connect.
HELP!!!!!
The following does not help me in the least to actually understand and/or debug the problem, but below are the debug/log file results:
===================================================
FROM ERRORLOG
2002-10-11 18:50:23.77 kernel Copyright (C) 1988-1997 Microsoft Corporation.
2002-10-11 18:50:23.77 kernel All rights reserved.
2002-10-11 18:50:23.77 kernel Logging SQL Server messages in file 'C:\MSSQL7\log\ERRORLOG'.
2002-10-11 18:50:23.87 kernel initconfig: Number of user connections limited to 32767.
2002-10-11 18:50:23.87 kernel SQL Server is starting at priority class 'normal'(1 CPU detected).
2002-10-11 18:50:23.95 kernel User Mode Scheduler configured for thread processing
2002-10-11 18:50:25.19 server Directory Size: 16217
2002-10-11 18:50:25.23 spid1 Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks
2002-10-11 18:50:25.24 spid1 Warning ******************
2002-10-11 18:50:25.24 spid1 SQL Server started in single user mode. Updates allowed to system catalogs.
2002-10-11 18:50:25.24 spid1 Warning ******************
2002-10-11 18:50:25.24 spid1 Recovering only master database
2002-10-11 18:50:25.24 spid1 Starting up database 'master'.
2002-10-11 18:50:25.24 spid1 Opening file C:\MSSQL7\data\master.mdf.
2002-10-11 18:50:25.27 spid1 Opening file C:\MSSQL7\data\mastlog.ldf.
2002-10-11 18:50:25.33 spid1 Loading SQL Server's Unicode collation.
2002-10-11 18:50:25.37 spid1 Loading SQL Server's non-Unicode sort order and character set.
2002-10-11 18:50:25.50 spid1 4 transactions rolled forward in database 'master' (1).
2002-10-11 18:50:25.51 spid1 0 transactions rolled back in database 'master' (1).
2002-10-11 18:50:25.70 spid1 Server is unnamed.
2002-10-11 18:50:25.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2002-10-11 18:50:25.70 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2002-10-11 18:50:25.76 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen on '\\.\pipe\sql\query'.
2002-10-11 18:50:25.76 ods Using 'SSMSSO70.DLL' version '7.0.623' to listen on '1433'.
2002-10-11 18:50:35.71 spid1 ODS does not start in 10 seconds
2002-10-11 18:50:35.71 spid1 SQL Server's Unicode collation is:
2002-10-11 18:50:35.71 spid1 'English' (ID = 1033).
2002-10-11 18:50:35.71 spid1 comparison style = 196609.
2002-10-11 18:50:35.71 spid1 SQL Server's non-Unicode sort order is:
2002-10-11 18:50:35.71 spid1 'nocase_iso' (ID = 52).
2002-10-11 18:50:35.71 spid1 SQL Server's non-Unicode character set is:
2002-10-11 18:50:35.71 spid1 'iso_1' (ID = 1).
2002-10-11 18:50:35.74 kernel Warning: override, autoexec procedures skipped.
2002-10-11 18:52:19.62 kernel SQL Server is terminating due to 'stop' request from Service Control Manager.
===================================================
From CNFGSVR.OUT
Starting Service ...
Connecting to Server ...
driver={sql server};server=VISIONQUEST;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver]Timeout expired
SQL Server configuration failed.
===================================================
Thanks,
jrbbldr
October 12, 2002 at 12:59 pm
quote:
I am not certain I understand what you mean by "install MSDE on a Domain Server". Are you referring to the Default installation setting which I have continued to use in hopes that it would create less problems?
I suspect it does not apply in your situation as you said "Win 2000 Prof". We have put MSDE on numerous W2K servers, and all the member servers work fine, but we have never gotten a domain server to work at all without demoting it first.
I should be more specific, I think it's been about 6 member servers and 2 domain servers, and both times we were under the gun in a production environment and did not do a lot of research. But it was really consistent.
But I don't think it applies in your situation.
I'm sorry, I don't have a suggestion based on your log.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply