database service MSSQL$Sharepoint fails to start during config

I'm installing WSS 3.0 (12.0.4518.1016) under Server 2003.  The initial
install seems to take an awfully long time (like, overnight...), and then
when I run the Configuration tool I get the following:

Configuration failed

One or more configuration settings failed.  Completed configuration settings
cannot be rolled back.  Resolve the problem and run this configuration wizard
again.  The following contains detailed information about the failure:

Failed to start the database service MSSQL$Sharepoint.  Repair this product
by selecting it from the Add/Remove programs menu.

To diagnose the problem, review the event log and configuration file located
at:

Extensions\12\LOGS\PSCDiagnostics_1_2_2007_11_7_53_901_4585

I have, of course, tried the repair (twice) but still get the same error.
This machine is in our data center and the local system account does not have
internet access, so I'm wondering if there is a problem during install
related to the installer using BITS or some other service that needs to hit
something on the net but can't...

Thanks in advance...

Chad

I can post the full log but it doesn't seem very helpful.  The last few
lines are:

01/02/2007 11:44:23  1  INF                  Not running in high contrast,
so we will paint the background with our trademarked image
01/02/2007 11:44:23  1  INF                  Not running in high contrast,
so we will paint the background with our trademarked image
01/02/2007 11:44:29  1  INF                  Not running in high contrast,
so we will paint the background with our trademarked image
01/02/2007 11:44:29  1  INF                  Entering function
PsconfigLinkLabel.LinkLabelClickedEventHandler
01/02/2007 11:44:29  1  INF                    Clicking the link data
C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\12\LOGS\PSCDiagnostics_1_2_2007_11_7_53_901_458569546.log
01/02/2007 11:44:29  1  INF                  Leaving function
PsconfigLinkLabel.LinkLabelClickedEventHandler
01/02/2007 11:44:29  1  INF                  Not running in high contrast,
so we will paint the background with our trademarked image

Hi Chad,Sorry to hear about your problems.

Hi Chad,

Sorry to hear about your problems.

Installing WSS should not take awful long (definitely less than an hour). Is
the machine up to the task and not running something else in the background?
Especially, is there less than 1GB of RAM? That would explain a lot (and
with <1GB of RAM I wouldn't bother, although you might get the system up).

Is this an upgrade scenario? I am assuming this is standalone. I think we
usually use a different db name in clean installs, that db name rings a bell
if you tried upgrading from WSS v2.

Regardless, sometimes especially with limited resources, the db instance
that we install just does not have enough time to start before we try to use
it. To double check if that was the case, ensure that the db is running
(Services from under the Control Panel, Administrative tools) and try
rerunning the Sharepoint... configuration wizard.

If these do not help, go back in to the PSC log and look for lines around
the first line that has "ERR " (include the space in the search). The lines
copied in this post just tell how the last screen was rendered, they are
irrelevant to the original problem (as you probably already figured).

JP

Jukka,Thanks for the fast response. Here is some followup info.1.

Jukka,

Thanks for the fast response.  Here is some followup info.

1. The machine is a dual core Xeon 3.2 GHz with 1G RAM.  I'm doing a
standalone install and the machine is not performing any other tasks in the
background -- it's a dedicated box for evaluating SP 2007.  We would
eventually deploy to something much more robust, but it sounds like this
should be enough to get WSS up and running.  WWS 2 was never installed on
this machine.  However, I did try a previous install of WWS 3 -- it was
taking hours to install so I rebooted the machine and started from scratch
(uninstalling and re-installing .NET framework 3 etc.).  I imagine that hard
aborting the install could have negative consequences in terms of leaving
stuff hanging around in the registry, etc.  Any thoughts on how to get back
to a clean slate at this point?  Should removing WSS 3 via add/remove
programs do the trick?

When you say "ensure that the db is running" in the services control panel,
to which service are you referring?

Finally, below is the relevant section of the log file, where you can see
the error messages thrown during install because of the MSSQL$Sharepoint
failure (should I be seeing a service called MSSQL$Sharepoint in the services
control panel?)

Thanks again.
Chad


01/02/2007 11:30:01  1  INF                        The parameter dbservice
is chosen, so returning the value as MSSQL$Sharepoint
01/02/2007 11:30:01  1  INF                        Entering function
ServiceHelper.Start
01/02/2007 11:30:01  1  INF                          Trying to start service
MSSQL$Sharepoint and waiting 120 sec to do so
01/02/2007 11:30:01  1  ERR                          An exception was
encountered when trying to start service MSSQL$Sharepoint
01/02/2007 11:30:01  1  INF                          Entering function
Common.BuildExceptionInformation
01/02/2007 11:30:01  1  INF                            Entering function
Common.BuildExceptionMessage
01/02/2007 11:30:01  1  INF                              Entering function
StringResourceManager.GetResourceString
01/02/2007 11:30:01  1  INF                                Resource id to be
retrieved is ExceptionInfo for language English (United States)
01/02/2007 11:30:01  1  INF                                Resource
retrieved id ExceptionInfo is An exception of type {0} was thrown.
Additional exception information: {1}
01/02/2007 11:30:01  1  INF                              Leaving function
StringResourceManager.GetResourceString
01/02/2007 11:30:01  1  INF                            Leaving function
Common.BuildExceptionMessage
01/02/2007 11:30:01  1  INF                          Leaving function
Common.BuildExceptionInformation
01/02/2007 11:30:01  1  ERR                          An exception of type
System.InvalidOperationException was thrown.  Additional exception
information: Service MSSQL$Sharepoint was not found on computer '.'.
System.InvalidOperationException: Service MSSQL$Sharepoint was not found on
computer '.'. ---> System.ComponentModel.Win32Exception: The specified
service does not exist as an installed service
--- End of inner exception stack trace ---
at System.ServiceProcess.ServiceController.GenerateNames()
at System.ServiceProcess.ServiceController.get_ServiceName()
at System.ServiceProcess.ServiceController.GenerateStatus()
at System.ServiceProcess.ServiceController.get_Status()
at Microsoft.SharePoint.PostSetupConfiguration.ServiceHelper.Start(String
serviceName)
01/02/2007 11:30:01  1  INF                        Leaving function
ServiceHelper.Start
01/02/2007 11:30:01  1  INF                        Entering function
Common.BuildExceptionInformation
01/02/2007 11:30:01  1  INF                          Entering function
Common.BuildExceptionMessage
01/02/2007 11:30:01  1  INF                            Entering function
StringResourceManager.GetResourceString
01/02/2007 11:30:01  1  INF                              Resource id to be
retrieved is ExceptionInfo for language English (United States)
01/02/2007 11:30:01  1  INF                              Resource retrieved
id ExceptionInfo is An exception of type {0} was thrown.  Additional
exception information: {1}
01/02/2007 11:30:01  1  INF                            Leaving function
StringResourceManager.GetResourceString
01/02/2007 11:30:01  1  INF                          Leaving function
Common.BuildExceptionMessage
01/02/2007 11:30:01  1  INF                        Leaving function
Common.BuildExceptionInformation
01/02/2007 11:30:01  1  ERR                        An exception of type
System.InvalidOperationException was thrown.  Additional exception
information: Service MSSQL$Sharepoint was not found on computer '.'.
System.InvalidOperationException: Service MSSQL$Sharepoint was not found on
computer '.'. ---> System.ComponentModel.Win32Exception: The specified
service does not exist as an installed service
--- End of inner exception stack trace ---
at System.ServiceProcess.ServiceController.GenerateNames()
at System.ServiceProcess.ServiceController.get_ServiceName()
at System.ServiceProcess.ServiceController.GenerateStatus()
at System.ServiceProcess.ServiceController.get_Status()
at Microsoft.SharePoint.PostSetupConfiguration.ServiceHelper.Start(String
serviceName)
at
Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.DefaultDatbaseServer()
01/02/2007 11:30:01  1  INF                        The parameter dbservice
is chosen, so returning the value as MSSQL$Sharepoint
01/02/2007 11:30:01  1  ERR                        Failed to start the
database service MSSQL$Sharepoint
01/02/2007 11:30:01  1  INF                        The parameter dbservice
is chosen, so returning the value as MSSQL$Sharepoint
01/02/2007 11:30:01  1  INF                        Entering function
StringResourceManager.GetResourceString
01/02/2007 11:30:01  1  INF                          Resource id to be
retrieved is SqlServerInstanceFailedToStart for language English (United
States)
01/02/2007 11:30:01  1  INF                          Resource retrieved id
SqlServerInstanceFailedToStart is Failed to start the database service {0}.
Repair this product by selecting it from the Add/Remove Programs menu.

Hi,Yes, the machine sounds definitely robust enough for testing.

Hi,

Yes, the machine sounds definitely robust enough for testing.

The odd thing here is that as far as I can tell, the db name is not what I'd
expect in clean install and that's why I asked about the earlier versions.
WSS should install what is called SQL 2005 Server Embedded Edition (referred
to as SSEE). However, your connecting string seems to refer to MSDE/WMSDE,
which was used as part of the WSS v2 system. It is possible, that this is
correct under some set of circumstances, but as boilerplate, it should be
the SSEE.

Yes, in both cases the Service Control Manager (SCM, Control panel, admin
tools, services) should show the database engine and it should be in the
started / running state. The display name for SSEE is SQL Server 2005
Embedded Edition (MICROSOFT##SSEE). I think the WMSDE name should be
something like MSSQL$Sharepoint.

Given the stage you are in, I would definitely try to uninstall WSS from the
Add/Remove Programs (ARP). After uninstalling it, refresh the ARP, and
double check that there are no SQL components of any sort left behind
(unless something else on the box requires them). Reboot -- older beta
versions of WSS / MOSS didn't always prompt this, but may still require
before reinstalling is succesful. After reboot, you may consider cleaning up
any db files left behind by the SQL uninstalls (search for .mdb / .ldb
files, understand what you are deleting and delete them as appropriate.
These can be under program files or windows or maybe other directories
depending on what and how was installed). You may also want to double check
the SCM for not having any SQL-related entries at this stage.

If you want to be really thorough, you can clean the registry hive of
HKLM\software\microsoft\shared tools\web server extensions\12. NOTE! All the
normal disclaimers about editing registry directly apply. Understand what
you are doing in the registry. However, the hive I mentioned is used by WSS
only and since you have just uninstalled, it should not be a big risk.
Similarly you may want to delete any remaining files in \program
files\common files\microsoft shared\web server extensions\12 (same
disclaimer).

After this, try reinstalling the WSS RTM and configuring it.

The logs just show that the config wizard tried starting the db, but could
not.

For anyone else having similar issues with MOSS, the expected db name is
slightly different, it is the SQL Server (OFFICESERVERS). If you have done
first WSS install and then upgraded to MOSS in standalone config, you should
have both.

JP

Well... I'm not sure if things are getting better or worse.

Well... I'm not sure if things are getting better or worse.  I uninstalled
WSS3, removed registry keys and uninstalled SQL Server 2000 (just to have a
really clean slate).  After rebooting I ran the WSS3 install again.  This
time I did not get any errors in the PSCDiagnostics log: it's last few lines
are:

01/04/2007 14:30:48  1  INF    Leaving function TaskDriver.Run
01/04/2007 14:30:48  1  INF    Successfully ran the task driver using the
command line task driver module.
01/04/2007 14:30:48  1  INF  Leaving function PsconfigCommandLineMain.Main

However, the install failed and I did get a general error log from the
installer.  What seem to be the important lines are quoted below.  I'm
starting to get the sense that this is a really tough problem.  What can you
suggest in terms of escalating this to a genuine support incident?

MSI(INFO): 'Property(S): INSTALLLEVEL = 1'
MSI(INFO): 'Property(S): SOURCEDIR = C:\Program Files\MSECache\wssv3\Global\'
MSI(INFO): 'Property(S): SourcedirProduct =
{90120000-1110-0000-0000-0000000FF1CE}'
MSI(INFO): 'Property(S): ProductToBeRegistered = 1'
MSI(INFO): '=== Logging stopped: 1/6/2007  17:23:19 ==='
MSI(TERMINATE): '(null)'
PERF: TickCount=169562203 Name=MsiPackage::Install Description=Returned from
OMsiInstaller::InstallProduct
Successfully installed package: wss path:C:\Program
Files\MSECache\wssv3\Global\wss.MSI
Executing command path: 'C:\Program Files\Common Files\Microsoft
Shared\SERVER12\Server Setup Controller\wrapinst.exe', args: 'timeout=2950
MsiPath=msxml\msxml6.msi'
Error: Command: 'C:\Program Files\Common Files\Microsoft
Shared\SERVER12\Server Setup Controller\wrapinst.exe' failed to return after
600000 milliseconds Type: CommandFailed.
Error: Command: 'C:\Program Files\Common Files\Microsoft
Shared\SERVER12\Server Setup Controller\wrapinst.exe' failed to return after
600000 milliseconds Type: CommandFailed.
Error: Command: 'C:\Program Files\Common Files\Microsoft
Shared\SERVER12\Server Setup Controller\wrapinst.exe' failed to return after
600000 milliseconds Type: CommandFailed.
Catalyst execution finished: 01/06/2007 17:34:23.  Return code: 30008.
Exception caught: CommandFailed.
PERF: TickCount=170226203 Name=RunSetup Description=End function
=========================================================================
Setup temp foler set to [C:\DOCUME~1\dh00cxa\LOCALS~1\Temp\1\Setup00000420].

The PSC logs were the old logs?

The PSC logs were the old logs? At least the time stamps indicate so. If
not, I am not following your procedure, because the PSC logs are created
only after the setup.

The failure in setup: it seems that it might be a timeout. In the same dir
that has the setup logs, there should be a wrapinst-log, which may have
additional details. However, it would seem that installing MSXML took too
long? To recover, you need to uninstall and reinstall (should not require
reboots since nothing was configured).

JP

Jukka,I really appreciate your time on this -- turns out the whole thing was

Jukka,

I really appreciate your time on this -- turns out the whole thing was kind
of a red herring.  In the end it was the eTrust Antivirus software running on
the machine that was preventing a clean install.  Obviously turning off
anti-virus apps is a good idea when installing anything, but I just
overlooked it in this case.  I assume the eTrust was blocking the creation of
the MSSQL service or somesuch...

Chad

Glad to hear it is solved.

Glad to hear it is solved. One more option for list of things that might go
wrong.

JP