after system restore the agent does not start

Hi group,
we have a server that had a server restore (near mirror, the system admin had to work out a few kinks). After the restore, the sql server agent does not start. When trying start it in service, it appears to be trying to start, but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service did not return an error. This could be an internal error or an internal service error.
Window event log shows the following error:
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: 17050, initerrlog: Could not open error log file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin
The log mentioned, is the normal name for the SQL Server error log... It looks like SQL is trying to open it a second time, (as if you have 2 instances of SQL Server trying to write to the same log file)... THis can be changed in SEM startup properties...
However it might be possible that your SQL Agent is trying to open the log ( in SEM right click SQL Agent and go to properties to discover the log name it is using..)
All in all it looks to me that the error you are showing is not related to the SQL Agent not starting...Ensure the agent is using an NT login that is a SQL Server administrator.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's community of SQL Server professionals.
www.sqlpass.org
"Quentin Ran" <ab@.who.com> wrote in message news:OwDGnstQEHA.1960@.TK2MSFTNGP10.phx.gbl...
Hi group,
we have a server that had a server restore (near mirror, the system admin had to work out a few kinks). After the restore, the sql server agent does not start. When trying start it in service, it appears to be trying to start, but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service did not return an error. This could be an internal error or an internal service error.
Window event log shows the following error:
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: 17050, initerrlog: Could not open error log file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin
|||>>The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer.
sounds like the sqlagent thinks it's running on a different computer.
does this restored server have a different name than the original
server?
[vbcol=seagreen]
system error = 32(The process cannot access the file because it is being
used by another process.).
this, as the other poster pointed out, sounds like something is using
that log file. that log file is for sqlserver. you should specify a
different log file for the agent, generally should be something like
e:\mssql\log\sqlagent.out
Quentin Ran wrote:

> Hi group, we have a server that had a server restore (near mirror, the
> system admin had to work out a few kinks). After the restore, the sql
> server agent does not start. When trying start it in service, it
> appears to be trying to start, but at the end the MMC gives a
> message Could not start the SQLSERVERAGENT service on local computer.
> The service did not return an error. This could be an internal error
> or an internal service error. Window event log shows the following
> error: 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:
> 17050, initerrlog: Could not open error log file
> 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process
> cannot access the file because it is being used by another
> process.). Can someone offer the fix? Thanks. The following is the
> configuration: Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> May 31 2003 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack
> 3) Quentin
|||Thanks for both responses.
The restored server has exactly the same name as before. SQL Server Agent
is running off a server admin account.
SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
server service log seems to work at least half way -- when the server
service starts, it records what it was doing like opening the databases. In
fact it even recorded a restore of a database. The fact that it did not
record any failure of launching the server agent may be due to it never was
asked to do so -- Windows may not know to direct such event there. The
agent log actually also contains some entries after the starting of the
server service, but not those ones that agent service start failed.
Any additional comments?
Quentin
"ch" <ch@.dontemailme.com> wrote in message
news:40B4980C.B82ABDFE@.dontemailme.com...
> message DLL files to display messages from a remote computer.
> sounds like the sqlagent thinks it's running on a different computer.
> does this restored server have a different name than the original
> server?
>
> system error = 32(The process cannot access the file because it is being
> used by another process.).
> this, as the other poster pointed out, sounds like something is using
> that log file. that log file is for sqlserver. you should specify a
> different log file for the agent, generally should be something like
> e:\mssql\log\sqlagent.out
>
>
> Quentin Ran wrote:
>
|||maybe there are some registry settings incorrect due to the restore of the
server.
try this.
create an nt account that is local admin on the server.
using enterprise manager, change the sqlserver and sqlagent services to use that
account.
restart server. see if agent starts properly.
now go back using enterprise manager and reset your sqlserver and sqlagent
accounts to whatever account(s) they were using before.
restart server. see if agent starts properly.
if that doesn't work, see if you can get them to run properly using the system
account for the two services.
be sure to use enterprise manager to make changes to the accounts the services
use.
Quentin Ran wrote:
[vbcol=seagreen]
> Thanks for both responses.
> The restored server has exactly the same name as before. SQL Server Agent
> is running off a server admin account.
> SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
> Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
> server service log seems to work at least half way -- when the server
> service starts, it records what it was doing like opening the databases. In
> fact it even recorded a restore of a database. The fact that it did not
> record any failure of launching the server agent may be due to it never was
> asked to do so -- Windows may not know to direct such event there. The
> agent log actually also contains some entries after the starting of the
> server service, but not those ones that agent service start failed.
> Any additional comments?
> Quentin
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4980C.B82ABDFE@.dontemailme.com...
|||Neither a local admin account nor the system account would start them.
There must be wrong registry settings, and we don't know which ones and the
correct values.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4BCFB.1AF8E97B@.dontemailme.com...
> maybe there are some registry settings incorrect due to the restore of the
> server.
> try this.
> create an nt account that is local admin on the server.
> using enterprise manager, change the sqlserver and sqlagent services to
use that
> account.
> restart server. see if agent starts properly.
> now go back using enterprise manager and reset your sqlserver and sqlagent
> accounts to whatever account(s) they were using before.
> restart server. see if agent starts properly.
> if that doesn't work, see if you can get them to run properly using the
system
> account for the two services.
> be sure to use enterprise manager to make changes to the accounts the
services[vbcol=seagreen]
> use.
>
> Quentin Ran wrote:
Agent[vbcol=seagreen]
SQL[vbcol=seagreen]
The[vbcol=seagreen]
In[vbcol=seagreen]
was[vbcol=seagreen]
or[vbcol=seagreen]
being[vbcol=seagreen]
the[vbcol=seagreen]
sql[vbcol=seagreen]
computer.[vbcol=seagreen]
error[vbcol=seagreen]
MSSQLSERVER
>
|||check this article
http://support.microsoft.com/default...b;en-us;283811
Quentin Ran wrote:
[vbcol=seagreen]
> Neither a local admin account nor the system account would start them.
> There must be wrong registry settings, and we don't know which ones and the
> correct values.
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4BCFB.1AF8E97B@.dontemailme.com...
> use that
> system
> services
> Agent
> SQL
> The
> In
> was
> or
> being
> the
> sql
> computer.
> error
> MSSQLSERVER
|||Thanks.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4D8F9.5C7C10D7@.dontemailme.com...[vbcol=seagreen]
> check this article
> http://support.microsoft.com/default...b;en-us;283811
>
> Quentin Ran wrote:
the[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
sqlagent[vbcol=seagreen]
the[vbcol=seagreen]
and[vbcol=seagreen]
E:\MSSQL\LOG\SQLAGENT.OUT.[vbcol=seagreen]
server[vbcol=seagreen]
databases.[vbcol=seagreen]
not[vbcol=seagreen]
never[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
information[vbcol=seagreen]
computer.[vbcol=seagreen]
using[vbcol=seagreen]
specify a[vbcol=seagreen]
like[vbcol=seagreen]
mirror,[vbcol=seagreen]
the[vbcol=seagreen]
it[vbcol=seagreen]
following[vbcol=seagreen]
from a[vbcol=seagreen]
the
>