I have a maintenance job that is failing with the
following error message:
The job failed. Unable to determine if the owner %OWNER%
of job %JOB% has server access (reason: The log for
database 'tempdb' is not available. [SQLSTATE HY000]
(Error 9001)).
Any ideas how to resolve this one? I've looked in the KB
and BOL, and I see entries for the error and the reason
in parentheses, but not with the two together. Was
thinking just cycling the instance might resolve the
issue, but was hoping to avoid doing this. Never seen
this one before, so any help would be appreciated.
Cheers.
All I can think is no DC available for authentication? I suspect the =
reason in brackets to be misleading, if tempdb had lost it's log you =
would be getting many other problems!)
Mike John
"knives" <anonymous@.discussions.microsoft.com> wrote in message =
news:1e30b01c454a9$cf5029c0$a001280a@.phx.gbl...
> I have a maintenance job that is failing with the=20
> following error message:
>=20
> The job failed. Unable to determine if the owner %OWNER%=20
> of job %JOB% has server access (reason: The log for=20
> database 'tempdb' is not available. [SQLSTATE HY000]=20
> (Error 9001)).
>=20
> Any ideas how to resolve this one? I've looked in the KB=20
> and BOL, and I see entries for the error and the reason=20
> in parentheses, but not with the two together. Was=20
> thinking just cycling the instance might resolve the=20
> issue, but was hoping to avoid doing this. Never seen=20
> this one before, so any help would be appreciated.
>=20
> Cheers.
|||I'd start by setting the job owner to sa.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"knives" <anonymous@.discussions.microsoft.com> wrote in message
news:1e30b01c454a9$cf5029c0$a001280a@.phx.gbl...
> I have a maintenance job that is failing with the
> following error message:
> The job failed. Unable to determine if the owner %OWNER%
> of job %JOB% has server access (reason: The log for
> database 'tempdb' is not available. [SQLSTATE HY000]
> (Error 9001)).
> Any ideas how to resolve this one? I've looked in the KB
> and BOL, and I see entries for the error and the reason
> in parentheses, but not with the two together. Was
> thinking just cycling the instance might resolve the
> issue, but was hoping to avoid doing this. Never seen
> this one before, so any help would be appreciated.
> Cheers.
Showing posts with label msg. Show all posts
Showing posts with label msg. Show all posts
Monday, March 19, 2012
Job failure - error msg attached
I have a maintenance job that is failing with the
following error message:
The job failed. Unable to determine if the owner %OWNER%
of job %JOB% has server access (reason: The log for
database 'tempdb' is not available. [SQLSTATE HY000]
(Error 9001)).
Any ideas how to resolve this one? I've looked in the KB
and BOL, and I see entries for the error and the reason
in parentheses, but not with the two together. Was
thinking just cycling the instance might resolve the
issue, but was hoping to avoid doing this. Never seen
this one before, so any help would be appreciated.
Cheers.All I can think is no DC available for authentication? I suspect the =reason in brackets to be misleading, if tempdb had lost it's log you =would be getting many other problems!)
Mike John
"knives" <anonymous@.discussions.microsoft.com> wrote in message =news:1e30b01c454a9$cf5029c0$a001280a@.phx.gbl...
> I have a maintenance job that is failing with the > following error message:
> > The job failed. Unable to determine if the owner %OWNER% > of job %JOB% has server access (reason: The log for > database 'tempdb' is not available. [SQLSTATE HY000] > (Error 9001)).
> > Any ideas how to resolve this one? I've looked in the KB > and BOL, and I see entries for the error and the reason > in parentheses, but not with the two together. Was > thinking just cycling the instance might resolve the > issue, but was hoping to avoid doing this. Never seen > this one before, so any help would be appreciated.
> > Cheers.|||I'd start by setting the job owner to sa.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"knives" <anonymous@.discussions.microsoft.com> wrote in message
news:1e30b01c454a9$cf5029c0$a001280a@.phx.gbl...
> I have a maintenance job that is failing with the
> following error message:
> The job failed. Unable to determine if the owner %OWNER%
> of job %JOB% has server access (reason: The log for
> database 'tempdb' is not available. [SQLSTATE HY000]
> (Error 9001)).
> Any ideas how to resolve this one? I've looked in the KB
> and BOL, and I see entries for the error and the reason
> in parentheses, but not with the two together. Was
> thinking just cycling the instance might resolve the
> issue, but was hoping to avoid doing this. Never seen
> this one before, so any help would be appreciated.
> Cheers.
following error message:
The job failed. Unable to determine if the owner %OWNER%
of job %JOB% has server access (reason: The log for
database 'tempdb' is not available. [SQLSTATE HY000]
(Error 9001)).
Any ideas how to resolve this one? I've looked in the KB
and BOL, and I see entries for the error and the reason
in parentheses, but not with the two together. Was
thinking just cycling the instance might resolve the
issue, but was hoping to avoid doing this. Never seen
this one before, so any help would be appreciated.
Cheers.All I can think is no DC available for authentication? I suspect the =reason in brackets to be misleading, if tempdb had lost it's log you =would be getting many other problems!)
Mike John
"knives" <anonymous@.discussions.microsoft.com> wrote in message =news:1e30b01c454a9$cf5029c0$a001280a@.phx.gbl...
> I have a maintenance job that is failing with the > following error message:
> > The job failed. Unable to determine if the owner %OWNER% > of job %JOB% has server access (reason: The log for > database 'tempdb' is not available. [SQLSTATE HY000] > (Error 9001)).
> > Any ideas how to resolve this one? I've looked in the KB > and BOL, and I see entries for the error and the reason > in parentheses, but not with the two together. Was > thinking just cycling the instance might resolve the > issue, but was hoping to avoid doing this. Never seen > this one before, so any help would be appreciated.
> > Cheers.|||I'd start by setting the job owner to sa.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"knives" <anonymous@.discussions.microsoft.com> wrote in message
news:1e30b01c454a9$cf5029c0$a001280a@.phx.gbl...
> I have a maintenance job that is failing with the
> following error message:
> The job failed. Unable to determine if the owner %OWNER%
> of job %JOB% has server access (reason: The log for
> database 'tempdb' is not available. [SQLSTATE HY000]
> (Error 9001)).
> Any ideas how to resolve this one? I've looked in the KB
> and BOL, and I see entries for the error and the reason
> in parentheses, but not with the two together. Was
> thinking just cycling the instance might resolve the
> issue, but was hoping to avoid doing this. Never seen
> this one before, so any help would be appreciated.
> Cheers.
Friday, March 9, 2012
job failed om the sql server
Hi,
i have a problem when i schedule an agent on the sql server and i log off the sql server ,
the agent failed with this msg' in the event viewr :
Login failed for user 'sa'. [CLIENT: <local machine>].
the account that run the SQL AGENT is NT AUTHORITY\NETWORKSERVICE.
i guess the problem is there but i can't find how to resolve it?
i'll be happy for any help.
10X.
anyone plz...?|||Hi everyone,
If more info is need i'll be happy to give...
Thanks.
|||I think NT AUTHORITY\NetworkService account is appropriate for MSDTC service but for SQL AGENT you need a domain account if you schedule activities on a network , so change SQL Agent logon account.|||Which service account is the service account running with ?
Jens K. Suessmeyer
http://www.sqlserver2005.de
|||These resources may help you sort out the service account requirements for SQL Agent.
Configuration -Service Accounts, SQL Server 2005 - Setting Up Windows Service Accounts
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
http://msdn2.microsoft.com/en-us/library/ms143504.aspx
Configuration -Service Accounts, SQL Server or SQL Server Agent service account
http://support.microsoft.com/kb/283811/en-us
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
Configuration -Service Accounts,Selecting an Account for the SQL Server Agent Service
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
http://support.microsoft.com/kb/907557
the service account running with NT AUTHORITY\NetworkService.
(sql server agent service).
|||As previously indicated, that is NOT a good account for the SQL Agent service.
Refer to the sources I posted for guidelines in setting up a domain account for your SQL Agent Service.
job failed om the sql server
Hi,
i have a problem when i schedule an agent on the sql server and i log off the sql server ,
the agent failed with this msg' in the event viewr :
Login failed for user 'sa'. [CLIENT: <local machine>].
the account that run the SQL AGENT is NT AUTHORITY\NETWORKSERVICE.
i guess the problem is there but i can't find how to resolve it?
i'll be happy for any help.
10X.
anyone plz...?|||Hi everyone,
If more info is need i'll be happy to give...
Thanks.
|||I think NT AUTHORITY\NetworkService account is appropriate for MSDTC service but for SQL AGENT you need a domain account if you schedule activities on a network , so change SQL Agent logon account.|||Which service account is the service account running with ?
Jens K. Suessmeyer
http://www.sqlserver2005.de
|||These resources may help you sort out the service account requirements for SQL Agent.
Configuration -Service Accounts, SQL Server 2005 - Setting Up Windows Service Accounts
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
http://msdn2.microsoft.com/en-us/library/ms143504.aspx
Configuration -Service Accounts, SQL Server or SQL Server Agent service account
http://support.microsoft.com/kb/283811/en-us
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
Configuration -Service Accounts,Selecting an Account for the SQL Server Agent Service
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
http://support.microsoft.com/kb/907557
the service account running with NT AUTHORITY\NetworkService.
(sql server agent service).
|||As previously indicated, that is NOT a good account for the SQL Agent service.
Refer to the sources I posted for guidelines in setting up a domain account for your SQL Agent Service.
Subscribe to:
Posts (Atom)