Could not obtain information

Hi All,
We've just recently changed/upgraded server boxes and went from Windows 2000
Server to Windows 2003 Server with
SQLServer 2000 sp4 installed on both. The Startup Service Account settings f
or both SQLServer and SQLServer
Agent is 'System Account'. On the original machine backups worked without a
flaw, but with the new machine I
receive the following error:
<<error from SQL Agent Error log>>
[298] SQLServer Error: 8198, Could not obtain information about Windows
NT group/user 'DOMAINNAME\username'.
[SQLSTATE 42000] (ConnIsLoginSysAdmin)
When remoted into the new machine with 'DOMAINNAME\username' and doing an "e
xec xp_logininfo
'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
<<error from Query Analyzer>>
Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
Could not obtain information about Windows NT group/user 'DOMAINNAME\usernam
e'.
I've looked at kb241643 and kb834124 and realize there is a workaround, but
this same account gets locked by AD
at least a couple of times a day when I try and use it to login to this and/
or other machines I administer (this
account is an admin account used strictly for administration purposes, I hav
e an individual account that I use
for my desktop and laptop). It seems to have began shortly after I had to ch
ange the password for this account.
I believe, the error and the lockout are related (my inexperience shows as I
do not have anything concrete to
make that assumption) so I would really like to know why this is happening a
nd how to correct it.
Thank you.
gdr
--
Gary D. Rezek
University Nerworking Systems and Services
South Dakota State UniversityHi,
Is both SQL box on same Domain ? are they have the same User Account in it ?
Have you set Password Policy for Account Lockout ?if so ,after how many
attempts it locks account ? i suspect that theirs is no such user ..
Regards
--
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"Gary D. Rezek" wrote:

> Hi All,
> We've just recently changed/upgraded server boxes and went from Windows 20
00 Server to Windows 2003 Server with
> SQLServer 2000 sp4 installed on both. The Startup Service Account settings
for both SQLServer and SQLServer
> Agent is 'System Account'. On the original machine backups worked without
a flaw, but with the new machine I
> receive the following error:
> <<error from SQL Agent Error log>>
> [298] SQLServer Error: 8198, Could not obtain information about Window
s NT group/user 'DOMAINNAME\username'.
> [SQLSTATE 42000] (ConnIsLoginSysAdmin)
> When remoted into the new machine with 'DOMAINNAME\username' and doing an
"exec xp_logininfo
> 'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
> <<error from Query Analyzer>>
> Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
> Could not obtain information about Windows NT group/user 'DOMAINNAME\usern
ame'.
> I've looked at kb241643 and kb834124 and realize there is a workaround, bu
t this same account gets locked by AD
> at least a couple of times a day when I try and use it to login to this an
d/or other machines I administer (this
> account is an admin account used strictly for administration purposes, I h
ave an individual account that I use
> for my desktop and laptop). It seems to have began shortly after I had to
change the password for this account.
> I believe, the error and the lockout are related (my inexperience shows as
I do not have anything concrete to
> make that assumption) so I would really like to know why this is happening
and how to correct it.
> Thank you.
> gdr
> --
> Gary D. Rezek
> university Nerworking Systems and Services
> South Dakota State University
>
>|||Hi Andy,
Yes both boxes are on the same domain and have the same user accounts in the
m. As far as I can tell the 2 boxes
are near identical with their setups. The AD guys have set a lockout policy
of 5 bad logins within 15 minutes
locks the account out for 15 minutes.
Thanks.
gdr
"Andy Davis" <activecrypt@.gmail.com> wrote in message news:873FAFB3-F604-45F4-913F-EAF6D2C0A
CA0@.microsoft.com...[vbcol=seagreen]
> Hi,
> Is both SQL box on same Domain ? are they have the same User Account in it
?
> Have you set Password Policy for Account Lockout ?if so ,after how many
> attempts it locks account ? i suspect that theirs is no such user ..
> Regards
> --
> Andy Davis
> Active Crypt Team
> ---SQL Server Encryption
> Decryption Software
> http://www.activecrypt.com
>
> "Gary D. Rezek" wrote:
>