• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1959
  • Last Modified:

Problems installing SQL Server Desktop Engine (MSDE)

I have just tried to install MSDE but I am not sure if it worked correctly.  I ran the following run cmd:

Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD="PASSWORD"

and it ran and came up installed correctly.  I then rebooted the machine expecting  an icon representing the database service manager.

This does not appear so I am not sure if this has worked correctly or not!!!

Anybody have a similar problem or have any ideas on this??

Thanks
0
WNottsC
Asked:
WNottsC
  • 8
  • 6
1 Solution
 
graf0Commented:
Check if the MSSQLSERVER$NetSDK service exists and is running - that would mean that the instalation was sucessful. If it does not exist, check sqlstp.log in windows directory - it should have information about what has happened.
0
 
WNottsCAuthor Commented:
I have found the following services:-

MSSQL$NetSDK  which starts automatically
SQLAgent$NetSDK which does not start

I set the SQLAgent$NetSDK to start automatically and it starts now but I still do not get an icon representing the database service manager.

I have found a log called SQLAGENT.1  which had this in it!!!

2005-04-20 09:01:33 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86 unicode retail build) : Process ID
2005-04-20 09:01:33 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86 unicode retail build) : Process ID 3560
2005-04-20 09:01:33 - ? [101] SQL Server ????????\NetSDK version 8.00.760 (0 connection limit)
2005-04-20 09:01:33 - ? [102] SQL Server ODBC driver version 3.85.1117
2005-04-20 09:01:33 - ? [103] NetLib being used by driver is DBMSLPCN.DLL; Local host server is ????????\NetSDK
2005-04-20 09:01:33 - ? [310] 1 processor(s) and 504 MB RAM detected
2005-04-20 09:01:33 - ? [339] Local computer is DR03R116-LP014 running Windows NT 5.1 (2600) Service Pack 2
2005-04-20 09:01:34 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent
2005-04-20 09:01:34 - ? [129] SQLAgent$NetSDK starting under Windows NT service control
2005-04-20 09:01:34 - + [260] Unable to start mail session (reason: No mail profile defined)
2005-04-20 09:01:34 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2005-04-20 09:36:51 - ? [130] SQLAgent$NetSDK stopping because of Windows shutdown...
2005-04-20 09:37:21 - ! [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
2005-04-20 09:37:21 - ! [311] Thread 'JobInvocationEngine' (ID 3592) is still running
2005-04-20 09:37:22 - + [098] SQLServerAgent terminated (forcefully)

Is this the problem???
0
 
graf0Commented:
If the services are there, the installation must have been sucessful (at least to some degree).
The Service Manager is in no way important for the database to work properly. Anyway, you can start it manualy from Programs>Microsoft SQL Server>Service Manager.
Try to run osql -E or just Enterprise Manager to see if you can connect to your server.
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
graf0Commented:
oops, there is no EM in MSDE - so you can not use it to verify conectivity. Just run this:
osql -E
and if you get a prompt like this:
1>
you are connected to your MSDE instance.
0
 
WNottsCAuthor Commented:
this is not the full version of SQL Server.  This is the free download from microsofts website of  SQL Server Desktop Engine (MSDE).  It does not have the enterprise manager!!

When installed it comes up with the following error log

2005-04-20 10:05:06.71 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 2)

2005-04-20 10:05:06.71 server    Copyright (C) 1988-2002 Microsoft Corporation.
2005-04-20 10:05:06.71 server    All rights reserved.
2005-04-20 10:05:06.71 server    Server Process ID is 524.
2005-04-20 10:05:06.71 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2005-04-20 10:05:06.72 server    SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-04-20 10:05:06.76 server    SQL Server configured for thread mode processing.
2005-04-20 10:05:06.76 server    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2005-04-20 10:05:06.79 spid3     Warning ******************
2005-04-20 10:05:06.79 spid3     SQL Server started in single user mode. Updates allowed to system catalogs.
2005-04-20 10:05:06.80 spid3     Starting up database 'master'.
2005-04-20 10:05:07.02 server    Using 'SSNETLIB.DLL' version '8.0.766'.
2005-04-20 10:05:07.02 spid5     Starting up database 'model'.
2005-04-20 10:05:07.04 spid3     Server name is '????????\NETSDK'.
2005-04-20 10:05:07.04 spid3     Skipping startup of clean database id 5
2005-04-20 10:05:07.04 spid3     Skipping startup of clean database id 6
2005-04-20 10:05:07.04 spid3     Starting up database 'msdb'.
2005-04-20 10:05:07.44 spid5     Clearing tempdb database.
2005-04-20 10:05:08.05 server    SQL server listening on Shared Memory.
2005-04-20 10:05:08.05 server    SQL Server is ready for client connections
2005-04-20 10:05:08.55 spid5     Starting up database 'tempdb'.
2005-04-20 10:05:08.60 spid3     Warning ******************
2005-04-20 10:05:08.60 spid3     Attempting to change default collation to Latin1_General_CI_AS.
2005-04-20 10:05:11.36 spid3     Clustered index restored for master.sysdatabases.
2005-04-20 10:05:11.41 spid3     Non-clustered index restored for master.sysobjects.
2005-04-20 10:05:11.44 spid3     Non-clustered index restored for master.sysobjects.
2005-04-20 10:05:11.47 spid3      index restored for master.syscolumns.
2005-04-20 10:05:11.47 spid3      index restored for master.systypes.
2005-04-20 10:05:11.50 spid3      index restored for master.sysusers.
2005-04-20 10:05:11.79 spid3      index restored for master.sysproperties.
2005-04-20 10:05:11.80 spid3      index restored for master.sysfulltextcatalogs.
2005-04-20 10:05:11.91 spid3      index restored for master.sysxlogins.
2005-04-20 10:05:11.93 spid3      index restored for master.sysdevices.
2005-04-20 10:05:11.97 spid3      index restored for master.sysservers.
2005-04-20 10:05:13.43 spid3      index restored for master.syslanguages.
2005-04-20 10:05:13.49 spid3      index restored for master.syscharsets.
2005-04-20 10:05:13.54 spid3      index restored for master.sysfilegroups.
2005-04-20 10:05:13.65 spid3      index restored for master.spt_values.
2005-04-20 10:05:13.66 spid3      index restored for master.MSreplication_options.
2005-04-20 10:05:13.68 spid3      index restored for master.spt_datatype_info_ext.
2005-04-20 10:05:13.69 spid3      index restored for master.spt_datatype_info.
2005-04-20 10:05:13.93 spid3     Non-clustered index restored for tempdb.sysobjects.
2005-04-20 10:05:13.93 spid3     Non-clustered index restored for tempdb.sysobjects.
2005-04-20 10:05:13.93 spid3      index restored for tempdb.syscolumns.
2005-04-20 10:05:13.94 spid3      index restored for tempdb.systypes.
2005-04-20 10:05:13.94 spid3      index restored for tempdb.sysusers.
2005-04-20 10:05:13.94 spid3      index restored for tempdb.sysproperties.
2005-04-20 10:05:13.94 spid3      index restored for tempdb.sysfulltextcatalogs.
2005-04-20 10:05:13.94 spid3      index restored for tempdb.sysfilegroups.
2005-04-20 10:05:14.13 spid3     Non-clustered index restored for model.sysobjects.
2005-04-20 10:05:14.15 spid3     Non-clustered index restored for model.sysobjects.
2005-04-20 10:05:14.29 spid3      index restored for model.syscolumns.
2005-04-20 10:05:14.30 spid3      index restored for model.systypes.
2005-04-20 10:05:14.50 spid3      index restored for model.sysusers.
2005-04-20 10:05:14.50 spid3      index restored for model.sysproperties.
2005-04-20 10:05:14.50 spid3      index restored for model.sysfulltextcatalogs.
2005-04-20 10:05:14.50 spid3      index restored for model.sysfilegroups.
2005-04-20 10:05:14.80 spid3     Non-clustered index restored for msdb.sysobjects.
2005-04-20 10:05:14.80 spid3     Non-clustered index restored for msdb.sysobjects.
2005-04-20 10:05:14.82 spid3      index restored for msdb.syscolumns.
2005-04-20 10:05:14.82 spid3      index restored for msdb.systypes.
2005-04-20 10:05:14.83 spid3      index restored for msdb.sysusers.
2005-04-20 10:05:14.85 spid3      index restored for msdb.sysproperties.
2005-04-20 10:05:14.85 spid3      index restored for msdb.sysfulltextcatalogs.
2005-04-20 10:05:14.85 spid3      index restored for msdb.sysfilegroups.
2005-04-20 10:05:14.85 spid3      index restored for msdb.sysjobschedules.
2005-04-20 10:05:14.86 spid3      index restored for msdb.syscategories.
2005-04-20 10:05:14.86 spid3      index restored for msdb.systargetservers.
2005-04-20 10:05:14.86 spid3      index restored for msdb.systargetservergroups.
2005-04-20 10:05:16.11 spid3      index restored for msdb.sysalerts.
2005-04-20 10:05:16.11 spid3      index restored for msdb.sysoperators.
2005-04-20 10:05:16.11 spid3      index restored for msdb.syscachedcredentials.
2005-04-20 10:05:16.11 spid3      index restored for msdb.logmarkhistory.
2005-04-20 10:05:16.13 spid3      index restored for msdb.sysdtscategories.
2005-04-20 10:05:16.13 spid3      index restored for msdb.sysdbmaintplan_databases.
2005-04-20 10:05:16.15 spid3      index restored for msdb.mswebtasks.
2005-04-20 10:05:16.15 spid3      index restored for msdb.sysdownloadlist.
2005-04-20 10:05:16.15 spid3      index restored for msdb.sysjobs.
2005-04-20 10:05:16.15 spid3      index restored for msdb.sysjobsteps.
2005-04-20 10:05:16.74 spid3     Default collation successfully changed.
2005-04-20 10:05:16.91 spid3     Recovery complete.
2005-04-20 10:05:16.91 spid3     SQL global counter collection task is created.
2005-04-20 10:05:16.94 spid3     Warning: override, autoexec procedures skipped.
2005-04-20 10:05:27.50 spid51    Error: 15457, Severity: 0, State: 1
2005-04-20 10:05:27.50 spid51    Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2005-04-20 10:05:27.57 spid51    Error: 15457, Severity: 0, State: 1
2005-04-20 10:05:27.57 spid51    Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2005-04-20 10:05:27.90 spid3     SQL Server is terminating due to 'stop' request from Service Control Manager.

Could you see if you can help with the bottom 6 or 7 lines
0
 
graf0Commented:
This log is just normal. Nothing out of ordinary here.
0
 
graf0Commented:
The command to connect to your MSDE should be:
osql -S????????\NETSDK -E
Where ???????? is your server name.
0
 
WNottsCAuthor Commented:
I have just run this in the run cmd:  osql -E

I do not get this prompt:   1>

it goes to the dos prompt and then goes off after a minute or two.
0
 
WNottsCAuthor Commented:
it comes up with the following error message:

[DBMSLPCN] SQL Server does not exist or access denied
[DBMSLPCN] ConnectionOpen (connect())

I have then started the service and it now came up with
1>

I could stil do with the service manager coming up.

Does this not mean anything in the error log then:

2005-04-20 10:05:16.94 spid3     Warning: override, autoexec procedures skipped.
2005-04-20 10:05:27.50 spid51    Error: 15457, Severity: 0, State: 1
2005-04-20 10:05:27.50 spid51    Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2005-04-20 10:05:27.57 spid51    Error: 15457, Severity: 0, State: 1
2005-04-20 10:05:27.57 spid51    Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2005-04-20 10:05:27.90 spid3     SQL Server is terminating due to 'stop' request from Service Control Manager.
0
 
graf0Commented:
Well, you have to have the database service running in order to connect... :-)

The service manager does not matter for the well being of your database. You can start it from C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe manualy or place it in Autostart group in Menu Start.

The errorlog is just normal - the messages are not really errors, just warning messages issued as setup reconfigures the server at the end of installation.
0
 
WNottsCAuthor Commented:
I am getting confused now.  If I log off from the network so this is a stand alone machine and reboot the machine the SQLAgent$NetSDK does not start automatically I restart this and then this works:  osql -S????????\NETSDK -E

However if I then run this:C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe  it does not come up with anything in the drop down box for servers.

2 questions.  

How do I get this to start the SQLAGENT$NETSDK service automoatically??
And Why is it not appearing in the sqlmanager.exe??
0
 
graf0Commented:
1. Just set SQLAGENT$NETSDK to start automaticaly from the Services applet in Control Panel.
2. I believe you need to type the name of your server (ie. ????????\NETSDK) in the server box of the Service Manager and then click "Refresh Services...".
0
 
WNottsCAuthor Commented:
question 1 seems to work fine!!
question 2 This works whe I first do this but when I reboot the computer this does not keep the sql server I am looking at, any ideas??
0
 
graf0Commented:
If the Service Manager is not persisting the name of the server, you can try to modify the values in registry.
It stores its configuration per-user in:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\Service Manager\

However, this doesn't work for me - I always get the local server in SM, even if I modify the name in registry. But you can still give it a try. If you find what needs to modified, let me know.
0

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now