I have job running under a domian\userraccont.. It use to work fine..
suddenly it stoppped working..below is the error message
"""""The job failed. Unable to determine if the owner
(HO_PDOMAIN\cyresextractprod) of job Cypress Reserves Extract Processing has
server access (reason: Could not obtain information about Windows NT
group/user 'HO_PDOMAIN\cyresextractprod'. [SQLSTATE 42000] (Error 819"""
I could not even get the user login info by isuing xp_logininfo command..
I will be gald if any 1 responseCould be
PRB: 8198 Error Message Returned from Job Owned by Windows NT Authenticated
User
http://support.microsoft.com/defaul...b;en-us;q241643
Since we don't allow users to create/own jobs we set all our jobs to be
owned by sa to avoid this issue. This may not be applicable in your
situation but it does mean we never run into this issue :-)
Also have a look at the KB articles returned by this search (watch for URL
wrapping)
%26CDID%3DEN-US-KB%26PRODLISTSRC%3DON&withinResults=&QuerySource=gASr_Query&Produc
t=sql2k&Queryc=8198&Query=8198&KeywordType=ALL&maxResults=25&Titles=false&numDays=
&InCC=on" target="_blank">http://support.microsoft.com/search...br />
&InCC=on
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Babu" <Babu@.discussions.microsoft.com> wrote in message
news:47299136-8FE8-4573-8C70-561EE1C27C04@.microsoft.com...
>
> I have job running under a domian\userraccont.. It use to work fine..
> suddenly it stoppped working..below is the error message
> """""The job failed. Unable to determine if the owner
> (HO_PDOMAIN\cyresextractprod) of job Cypress Reserves Extract Processing
> has
> server access (reason: Could not obtain information about Windows NT
> group/user 'HO_PDOMAIN\cyresextractprod'. [SQLSTATE 42000] (Error 819"
""
> I could not even get the user login info by isuing xp_logininfo command..
> I will be gald if any 1 response
Monday, March 12, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment