April 12, 2005 at 1:21 pm
Hi,
I'm having trouble with MSDE. After I run the setup, it doesn't ask me if I want to reboot (I'm using Windows XP sp2). So, I run 'net start mssqlserver' and it is running. But for some reason, I can't connect to it using a DSN setup program.
The issue I'm having is, if I reboot the computer and let MSSQL start, I have no problem connecting to the server using the DSN setup program.
Why doesn't the MSSQL setup program ask me if I want to reboot or not?
This is important to me, since I am trying to deploy the setup program with a software product I am making.
I have posted some information (In-memory DLL snapshots before and after rebooting, with MSSQL running). I ran a recursive MD5 sum comparison of the entire file system before and after, but there was no significant difference, just some log files and temp file entries.
Please see my output files at http://thorie.com/sqldiff/paste.html
I don't know what is wrong, and why rebooting solves the installation issue -- and how to fix this so that either A) i don't need to reboot, or B) have the MSDE setup ask to reboot.
Thanks for your help!
Tak.
April 13, 2005 at 8:31 am
Hi, Tak. When you said that the DSN setup program could not connect, what error message did you get? Did you run the svrnetcn.exe utility to make sure the network protocols were enabled before the reboot? I, too, have seen the MSSQL setup not ask for a reboot and I'm not sure why. The failure to connect must have something to do with port 1433 not being opened or the service not really listening on that port. Check the Errorlog from just after the installation, any clues there?
HTH
Don
April 13, 2005 at 10:18 am
By default, MSDE SP3 will not install any network protocols (TCP, named pipes, etc). You will always be able to connect on the same machine using Shared memory protocol. If no network protocols are installed and/or running, then "DSN setup" (actually called DataLinks properties) or any other application will not be able to browse for the instance, since 1433 is not enabled or available for SQL server browser. The service will not listen on that port if there are no active network protocols.
You can still connect even if the server/instance does not show up on the drop down list of SQL Servers. Just type in the server/instance name, and the login information, and it will connect (to list databases, for example).
I have rarely seen that MSDE will need a reboot on WinXP. The only time I have seen it has been on a absolutely clean machine with no service packs or patches. Even if SP1 is installed it should not require a reboot. So you're experience not asking for a reboot should be normal.
Mark
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply