SQL Server 7.0 stopped loading as service issues...

Ok, Windows 2000 server w/sp4 and all patches. Runs SQLServer 7.0 with legac
y
app. About 2 months ago the SQLServer stopped running as a service. To
invoke, we double click on SQLSRVER.EXE. I've checked to logs, nothing
concrete.

IF someone changed the SA password, could that effect loading as service and
how could I get what it is set for. This is an issue because it appears that
the SQL Server Agent for Arcserve isn't backing up the databases... I imagin
e
that the reason is because SQLServer isn't a service anymore...

Enterprise manager runs, but can't open the current SQLServer becaue it
isn't started. Thank God that it can be 'brute forced' and the application
runs.

Getting it started as a service would be nice, but there needs to be backups
of the data. Are there any ways to get backups through a script on SQLServer
,
or would shutting down SQLServer allow a good backup...

Thanks for any assistance...

Hi

You may want to change the service accounts and try running it from the
services applet to see if it produces an error message. Also check the event
log to see if there is any messages in that.

The sa login is a SQL Server account and if SQL Server is starting this from
the command prompt it should not be the cause of your problem.

John

"drkc" wrote:

> Ok, Windows 2000 server w/sp4 and all patches. Runs SQLServer 7.0 with leg
acy
> app. About 2 months ago the SQLServer stopped running as a service. To
> invoke, we double click on SQLSRVER.EXE. I've checked to logs, nothing
> concrete.
>
> IF someone changed the SA password, could that effect loading as service a
nd
> how could I get what it is set for. This is an issue because it appears th
at
> the SQL Server Agent for Arcserve isn't backing up the databases... I imag
ine
> that the reason is because SQLServer isn't a service anymore...
>
> Enterprise manager runs, but can't open the current SQLServer becaue it
> isn't started. Thank God that it can be 'brute forced' and the application
> runs.
>
> Getting it started as a service would be nice, but there needs to be backu
ps
> of the data. Are there any ways to get backups through a script on SQLServ
er,
> or would shutting down SQLServer allow a good backup...
>
> Thanks for any assistance...

Here is what comes up in the event viewer:

Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7000
Description:
The MSSQLServer service failed to start due to the following error:
Access is denied.

Then I tried to start the SQLAgent and get this:

Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7001
Description:
The SQLServerAgent service depends on the MSSQLServer service which failed
to start because of the following error:
Access is denied.

And I get thousands of these messages in the Application log:

Event Type:	Information
Event Source:	MSSQLServer
Event Category:	(4)
Event ID:	17055
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLServer ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: 18454, Login succeeded for user 'Master'.
Connection: Non-Trusted.

Which fills up the Application log fast. Does that help?

This is all from trying to run it from the services applet. The messages are
the same...

Thanks. Does this help???

"John Bell" wrote:

> Hi
>
> You may want to change the service accounts and try running it from the
> services applet to see if it produces an error message. Also check the eve
nt
> log to see if there is any messages in that.
>
> The sa login is a SQL Server account and if SQL Server is starting this fr
om
> the command prompt it should not be the cause of your problem.
>
> John
>
> "drkc" wrote:
> 

Hi

At a guess you are currently using a domain account to start the service?
Does the service start if you change it to local system?

Also check the SQL Server log before you try to start the service and
immediately  after this fails to see if there is anything.

If the log has not changed check the directory/file permissions.

John

"drkc" wrote:

> Here is what comes up in the event viewer:
>
> Event Type:	Error
> Event Source:	Service Control Manager
> Event Category:	None
> Event ID:	7000
> Description:
> The MSSQLServer service failed to start due to the following error:
> Access is denied.
>
> Then I tried to start the SQLAgent and get this:
>
> Event Type:	Error
> Event Source:	Service Control Manager
> Event Category:	None
> Event ID:	7001
> Description:
> The SQLServerAgent service depends on the MSSQLServer service which failed
> to start because of the following error:
> Access is denied.
>
> And I get thousands of these messages in the Application log:
>
> Event Type:	Information
> Event Source:	MSSQLServer
> Event Category:	(4)
> Event ID:	17055
> Description:
> The description for Event ID ( 17055 ) in Source ( MSSQLServer ) cannot be
> found. The local computer may not have the necessary registry information 
or
> message DLL files to display messages from a remote computer. The followin
g
> information is part of the event: 18454, Login succeeded for user 'Master'
.
> Connection: Non-Trusted.
>
> Which fills up the Application log fast. Does that help?
>
> This is all from trying to run it from the services applet. The messages a
re
> the same...
>
> Thanks. Does this help???
>
> "John Bell" wrote:
> 

No, it was using 'local system' and still won't start. It is a directory/fil
e
permissions thing, what should the security be? Finding out who did it is
another thing and probably won't ever be determined...

Thank you for your help so far. Extremely helpful!

"John Bell" wrote:

> Hi
>
> At a guess you are currently using a domain account to start the service?
> Does the service start if you change it to local system?
>
> Also check the SQL Server log before you try to start the service and
> immediately  after this fails to see if there is anything.
>
> If the log has not changed check the directory/file permissions.
>
> John
>
> "drkc" wrote:
> 

Hi

I am not sure how you would restrict it for only local system, you may want
to try giving everything to everyone to make sure it works and then closing
it down.

John

"drkc" wrote:

> No, it was using 'local system' and still won't start. It is a directory/f
ile
> permissions thing, what should the security be? Finding out who did it is
> another thing and probably won't ever be determined...
>
> Thank you for your help so far. Extremely helpful!
>
> "John Bell" wrote:
>