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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

installing msde- can't get started !!!

Status
Not open for further replies.

KJS2002

Programmer
Jul 15, 2002
11
GB
insulting the expertise of many of you I know but ...
I've installed MSDE from win200 disk but am not getting any icons in the task bar and can't work out how to open the Service manager. I don't think it has installed correctly.
Any advice?
Thanks.
 
nothing in the start menu.
Running sqlservr.exe gives:
lots of text then...
"Error: 17826, Severity: 18, State: 1"

Is it a conflict with port 1433?
I can't uninstall or reinstall - so am feeling a bit stuck!!
 
delighted to!...

2002-11-21 23:52:35.82 kernel initconfig: Number of user connections limited to 32767.
2002-11-21 23:52:35.82 kernel SQL Server is starting at priority class 'normal'(1 CPU detected).
2002-11-21 23:52:35.82 kernel User Mode Scheduler configured for thread processing
2002-11-21 23:52:36.82 server Directory Size: 10803
2002-11-21 23:52:36.82 spid1 Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks
2002-11-21 23:52:36.82 spid1 Starting up database 'master'.
2002-11-21 23:52:36.82 spid1 Opening file C:\MSSQL7\data\master.mdf.
2002-11-21 23:52:36.85 spid1 Opening file C:\MSSQL7\data\mastlog.ldf.
2002-11-21 23:52:36.94 spid1 Loading SQL Server's Unicode collation.
2002-11-21 23:52:36.96 spid1 Loading SQL Server's non-Unicode sort order and
character set.
2002-11-21 23:52:37.11 spid1 2 transactions rolled forward in database 'maste
r' (1).
2002-11-21 23:52:37.11 spid1 0 transactions rolled back in database 'master'
(1).
2002-11-21 23:52:37.20 spid1 Starting up database 'model'.
2002-11-21 23:52:37.20 spid1 Opening file C:\MSSQL7\DATA\model.mdf.
2002-11-21 23:52:37.28 spid1 Opening file c:\mssql7\data\modellog.ldf.
2002-11-21 23:52:37.41 spid1 Clearing tempdb database.
2002-11-21 23:52:37.45 spid1 Creating file C:\MSSQL7\DATA\TEMPDB.MDF.
2002-11-21 23:52:37.57 spid1 Closing file C:\MSSQL7\DATA\TEMPDB.MDF.
2002-11-21 23:52:37.61 spid1 Creating file C:\MSSQL7\DATA\TEMPLOG.LDF.
2002-11-21 23:52:37.62 spid1 Closing file C:\MSSQL7\DATA\TEMPLOG.LDF.
2002-11-21 23:52:37.66 spid1 Opening file C:\MSSQL7\DATA\TEMPDB.MDF.
2002-11-21 23:52:37.67 spid1 Opening file C:\MSSQL7\DATA\TEMPLOG.LDF.
2002-11-21 23:52:38.34 spid1 Closing file C:\MSSQL7\DATA\TEMPDB.MDF.
2002-11-21 23:52:38.37 spid1 Closing file C:\MSSQL7\DATA\TEMPLOG.LDF.
2002-11-21 23:52:38.38 spid1 Starting up database 'tempdb'.
2002-11-21 23:52:38.38 spid1 Opening file C:\MSSQL7\DATA\TEMPDB.MDF.
2002-11-21 23:52:38.43 spid1 Opening file C:\MSSQL7\DATA\TEMPLOG.LDF.
2002-11-21 23:52:38.66 spid1 Server name is 'M6Q0M6'.
2002-11-21 23:52:38.66 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2002-11-21 23:52:38.66 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2002-11-21 23:52:38.66 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen
on '\\.\pipe\sql\query'.
2002-11-21 23:52:38.66 ods Using 'SSMSRP70.DLL' version '7.0.623' to listen
on 'M6Q0M6'.
2002-11-21 23:52:38.68 ods Error: 17826, Severity: 18, State: 1

thanks again!
Keith
 
Is M6Q0M6 the name of the server? If it isn't, then the error may be caused by having an incorrect name in MSDE. If this is the case, you'll have to find a a way to uninstall MSDE and the reinstall.

If the server name is correct, then you may be correct in asking about port 1433 because the next line should probably read "Using 'SSMSSO70.DLL' version '7.0.623' to listen on '1433'." You should check for conflicts. Terry L. Broadbent - DBA
Computing Links:
faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions.
 
M6Q0M6 is the name of the server. If I run "Netstat -an" from the DOS prompt nothing appears to be listening at 1344. I then run sqlservr.exe and get the same old error messages. Running "Netstat -an" again now shows something listening on port 1344 but I guess that's because SQL Server hasn't started properly. I've tried changing the TCP/IP to 0 in the 'SQL Server Network Utility' but that doesn't seem to help.
This "Netstat -an" is new to me - I found the idea on the web.
Thanks for your help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top