date and installing, among others SP4 for win2k.
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Michaels B
ackup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) - Status: Failed - Invoked
on: 2004-01-19 02:00:00 - Message: The job failed. Unable to determine if
the owner (MYSERVER\mylogin) of job DB Backup Job for DB Maintenance Plan 'M
ichaels Backup Plan' has server access (reason: Could not obtain information
about Windows NT group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 819
8))."
the only thing that changed was the updates, which can be significant but I
certainly didn't change anything related to my account. I have recreated th
e plan with the same result.
I can open the LOGON section of SQLadmin and see my name there, I can open i
t and close it but if I try to make any changes it says messages similar to
the above on.
KB articles suggested ading the everyone group to the pre2000 users group bu
t that sounds dangerous.
Help? what else can I look at. I am the sysop and should have all the necess
ary rightsIn message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
writes
quote:
>I am getting the following message in my event logs since hitting windows
>update_and installing, among others _SP4 for win2k.
>"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
>'Michaels Backup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) -
>Status: Failed - Invoked on: 2004-01-19 02:00:00 - Message: The job
>failed._ Unable to determine if the owner (MYSERVER\mylogin) of job DB
>Backup Job for DB Maintenance Plan 'Michaels Backup Plan' has server
>access (reason: Could not obtain information about Windows NT
>group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 8198))."
>the only thing that changed was the updates, which can be significant but
>_I certainly didn't change anything related to my account. I have recreated
>the plan with the same result.
>I can open the LOGON section of SQLadmin and see my name there, I
>can open it and close it but if I try to make any changes it says messages
>similar to the above on.
>KB articles suggested ading the everyone group to the pre2000 users
>group but that sounds dangerous.
>Help? what else can I look at. I am the sysop and should have all the
>necessary rights
I assume you have seen KB 241643, but have you tried the first
workaround "Change the job owner to a standard SQL Server user or system
administrator (sa)."? I have read this many times, and the second option
has never worked for me, so I go straight for option 1. I suspect there
may be other causes, perhaps network issues between SQL and the DC.
PRB: 8198 Error Message Returned from Job Owned by Windows NT
Authenticated User
http://support.microsoft.com?kbid=241643
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org|||"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...
quote:|||Lets try that again.
> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>
I saw the KB article and I couldn't make option 2 work either so that is
encouraging :-?
The DC and the SQL server are the same machine so comms shouldn't be an
issue.
I'll try creating a new backup plan under sa but could you tell me what a
"Standard Sql Server User " is?
"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...
quote:|||In message <u1fxN$d4DHA.2612@.tk2msftngp13.phx.gbl>, mmac <no@.thanks.com>
> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>
writes
quote:
>Lets try that again.
>I saw the KB article and I couldn't make option 2 work either so that is
>encouraging :-?
>The DC and the SQL server are the same machine so comms shouldn't be an
>issue.
>I'll try creating a new backup plan under sa but could you tell me what a
>"Standard Sql Server User " is?
>
A standard SQL Server user, or SQL (Server) login, is what you use as
opposed to and integrated or NT authentication login. This option is
only available if the server is set to Mixed Mode security.
sa is a SQL login, but BUILTIN\Administrators is a integrated login.
Make sense?
Darren
quote:
>"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in messag
e
>news:7r2qD3R8WFEAFwOw@.sqldts.com...
>recreated
>messages
>
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org
