MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack yet) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to make the MSDE server listen on TCP/IP port 1433. But it will not listen on that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack ye
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

MSDE or MS SQL Server 2000 Developer Edition ?

I have been using MSDE and I recently got Microsoft SQL ServerTM 2000 Developer Edition as part of my MAPS pack. Can and should I replace MSDE with Microsoft SQL Server 2000 Developer Edition on my development pc? Thanks in advance for any advice on pros and cons or known issues?Please excuse my ignorance -- what a MAPS pack?

I think the benefit of installing the Developer Edition would be that you'd be able to use the Client Tools -- such as Enterprise Manager and Query Analyzer. I know people that have bought just the Developer Edition for legal use of those tools.

The Developer Edition includes all of the functionality of the Enterprise Edition, but you cannot use it for production. If you are going to be developing mobile applications needing SQL Server CE, owning the Developer Edition gives you the rgiht to redistribute SQL Server CE.

This white paper explains the differences between the editions and should help you to make an informed choice:Choosing an Edition of SQL Server 2000.

Terri|||Thanks for the info. There is some (M)icrosoft (A)ction (P)ack info:

The Action Pack Update kits are sent quarterly. To see a complete listing of the
contents of the Update kit (in the US and Canada), please visit:

http://members.microsoft.com/partner/salesmarketing/partnermarket/actionpack/updatekits.aspx

Thank you for continuing your subscription to the Microsoft Action Pack!

-The Worldwide Partner Programs Team|||Everywhere it says NT and 2000. Does it run on XP. Thanks.|||Well, I can tell you that I have XP Pro an I am running SQL Server 2000 Personal Edition successfully, and my colleague is also running XP Pro but with the SQL Server 2000 Developer Edition and he has been able to use it successfully.

YMMV

Terri

MSDE installation error

Hi, are days that i'm trying to install MSDE on my computer (windows XP service pack 1).
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.