RE: SQL 2005 processe stuck in 'Starting' state after reboot

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

This is pretty broad so you may be spending quite some time in the message
boards tblshooting this.

Because of the network problems I would do the first two following things:

Make sure only the TCP/IP Protocal is enabled and that the port is set to
the default 1344.

Next I would look at the sql server service and see what account is starting
the service. I would try and make sure it is an account on your active
directory and that their are no profiles associated with it (a labled service
account).

If this fixes the problem then it is indeed a network related issue. If not
unfortunatly we have not done enough to rule the network out as of yet.



"twd" wrote:

I should preface this with the disclaimer: I don't know anything about SQL
server, so please use small words :)

This is on a Windows Server 2003 R2 box. The SQL server in question was
installed as part of the CommVault Simpana 8.0 backup software. I have
opened a ticket with CommVault, but they say this is an SQL problem, and not
theirs.

I upgraded from Simpana 7.0 to 8.0 following CommVault's instructions. Prior
to the upgrade SQL worked fine. Now the service SQL Server (COMMVAULT) will
not start after the machine is rebooted. It attempts to start, but hangs
with a status of 'Starting'. While it is in this state, networking does not
work. Also, while SQL Server is stuck, the Performance Logs and Alerts
service is in the 'Stopping' state.

To get around this, I can set SQL Server to 'Disabled' (which freezes the
mmc console, requiring a reboot to unfreeze) I can then manually start SQL
Server and it works fine.

There are no entries in the Event Log, nor in the ERRORLOG files. But as I
said above, I don't know anything about SQL, so it's very possible I missed a
log file somewhere.

CommVault's first suggestion was to uninstall their software and the SQL
server and reinstall. That didn't change anything. The next thing they
suggest is to completely rebuild the server from the OS up. I am reluctant
to do this. There are no other applications on this server. I did apply SP3
yesterday, but it didn't help.

Any help is appreciated, and I am happy to provide any further information
that might be needed.
.

Relevant Pages

  • Re: SharePoint Services
    ... IT does not support our Access app explicitly as the app is considered ... The app is a 'split' mde with only the BE sitting on the network ... server will work to speed up the app. ... As I stated moving the backend data to SQL server will usually slow it ...
    (comp.databases.ms-access)
  • Re: how big can disconnected dataset be?
    ... I forgot to mention, yes, reducing network ... > traffice, or rather, get all the data to the local server ... > Server from the datasets. ... huge performance increase on your SQL server, but I'm sure you will see some ...
    (microsoft.public.dotnet.languages.vb)
  • Re: DTS and the Internet
    ... It's good to know it is not a login problem, so I can concentrate on the ... network part of the problem. ... >>Server Administrator and has all the permissions. ... > password) for a SQL Server login, ...
    (microsoft.public.sqlserver.dts)
  • Re: Cannot connect to SQL 2000 remotely
    ... Microsoft SQL Server, and then click Server Network Utility. ... similar program, the Client Network Utility. ...
    (microsoft.public.sqlserver.connect)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)