Linked Server Problems with all providers

Im having problems with linked servers on one particular computer and am out
of ideas. The box is an XP SP2, SQL server 2000 SP3. When i create a linke
d
server of any type, clicking on "tables" or "views" in the enterprise manage
r
list, gives the following error:
Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBinitialize::Initialize
returned 0x80004005: ].
This particular LSN is pointing to another SQL server machine. Regardless
of what provider i choose, i get the same error (the error message changes
the provider based on the provider of the LSN).
I am an administrator on both boxes, have disabled virus protection, the
windows firewall on the XP box is disabled (by a group policy on the domain)
,
and i have enabled inbound and outbound traffic in the dcomcnfg.exe.
LSN's created on other computers work fine. Any ideas?You can get this error with timeout issues. Refer to the
following:
Error message when you execute a linked server query in SQL
Server: "Timeout Expired"
http://support.microsoft.com/?id=314530
You can also double check the security mappings for the
linked servers.
You will also want to check the connectivity - try pinging
the other servers from the box you are having problems with.
Ping by server name and IP.
-Sue
On Wed, 15 Mar 2006 06:56:28 -0800, John Kurtis <John
Kurtis@.discussions.microsoft.com> wrote:

>Im having problems with linked servers on one particular computer and am ou
t
>of ideas. The box is an XP SP2, SQL server 2000 SP3. When i create a link
ed
>server of any type, clicking on "tables" or "views" in the enterprise manag
er
>list, gives the following error:
>Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
>OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBinitialize::Initializ
e
>returned 0x80004005: ].
>This particular LSN is pointing to another SQL server machine. Regardless
>of what provider i choose, i get the same error (the error message changes
>the provider based on the provider of the LSN).
>I am an administrator on both boxes, have disabled virus protection, the
>windows firewall on the XP box is disabled (by a group policy on the domain
),
>and i have enabled inbound and outbound traffic in the dcomcnfg.exe.
>LSN's created on other computers work fine. Any ideas?|||Thanks for the reply. However im 99% sure that its not a timeout issue. I
get the error immediately after i click on "tables" or "views" in enterprise
manager.
Pings from the box that is having problems come back fine, both with IP as
well as name.

linked server login problem... with a particular login... on a particular box

Im having a problem with one particular Linked Server Login. I've created
two of them. Neither of which has an existing Login on the Linked Server and
both of which are mapped to a member of SA. In the below examply, Login1
will work, but Login2 will fail with:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login1'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login2'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
Again, please keep in mind that the Login on the Linked Server is in the SA
role, and that the top Login works. Another important tip, both of these
work successfully on another box, just not the one that counts.
All ideas are greatly appreciated as Im quite desperate.
--
SQL2K SP3
TIA, ChrisRI think its related to this issue but Im not sure.
http://support.microsoft.com/default.aspx?scid=kb;en-us;238477
I don't really need a fix for this anyomore as I've found a workaround and
only needed this temporarily. More info: I had opened Query Analyzer under
the failing account on my local box... RClick/ Run as. But if I log directly
onto the box I was trying to run the query from it works fine. Which is why
Im thinking its related to the above article.
"ChrisR" <bla@.noemail.com> wrote in message
news:#uUSqB4EFHA.2608@.TK2MSFTNGP10.phx.gbl...
> Im having a problem with one particular Linked Server Login. I've created
> two of them. Neither of which has an existing Login on the Linked Server
and
> both of which are mapped to a member of SA. In the below examply, Login1
> will work, but Login2 will fail with:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login1'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login2'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> Again, please keep in mind that the Login on the Linked Server is in the
SA
> role, and that the top Login works. Another important tip, both of these
> work successfully on another box, just not the one that counts.
> All ideas are greatly appreciated as Im quite desperate.
> --
> SQL2K SP3
> TIA, ChrisR
>

linked server login problem... with a particular login... on a particular box

Im having a problem with one particular Linked Server Login. I've created
two of them. Neither of which has an existing Login on the Linked Server and
both of which are mapped to a member of SA. In the below examply, Login1
will work, but Login2 will fail with:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login1'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login2'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
Again, please keep in mind that the Login on the Linked Server is in the SA
role, and that the top Login works. Another important tip, both of these
work successfully on another box, just not the one that counts.
All ideas are greatly appreciated as Im quite desperate.
SQL2K SP3
TIA, ChrisRI think its related to this issue but Im not sure.
http://support.microsoft.com/defaul...kb;en-us;238477
I don't really need a fix for this anyomore as I've found a workaround and
only needed this temporarily. More info: I had opened Query Analyzer under
the failing account on my local box... RClick/ Run as. But if I log directly
onto the box I was trying to run the query from it works fine. Which is why
Im thinking its related to the above article.
"ChrisR" <bla@.noemail.com> wrote in message
news:#uUSqB4EFHA.2608@.TK2MSFTNGP10.phx.gbl...
> Im having a problem with one particular Linked Server Login. I've created
> two of them. Neither of which has an existing Login on the Linked Server
and
> both of which are mapped to a member of SA. In the below examply, Login1
> will work, but Login2 will fail with:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login1'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login2'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> Again, please keep in mind that the Login on the Linked Server is in the
SA
> role, and that the top Login works. Another important tip, both of these
> work successfully on another box, just not the one that counts.
> All ideas are greatly appreciated as Im quite desperate.
> --
> SQL2K SP3
> TIA, ChrisR
>

linked server login problem... with a particular login... on a particular box

Im having a problem with one particular Linked Server Login. I've created
two of them. Neither of which has an existing Login on the Linked Server and
both of which are mapped to a member of SA. In the below examply, Login1
will work, but Login2 will fail with:
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login1'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
, @.useself = 'false'
, @.locallogin = 'domain\Login2'
, @.rmtuser = 'RmtLogin1'
, @.rmtpassword = 'password'
Again, please keep in mind that the Login on the Linked Server is in the SA
role, and that the top Login works. Another important tip, both of these
work successfully on another box, just not the one that counts.
All ideas are greatly appreciated as Im quite desperate.
SQL2K SP3
TIA, ChrisR
I think its related to this issue but Im not sure.
http://support.microsoft.com/default...b;en-us;238477
I don't really need a fix for this anyomore as I've found a workaround and
only needed this temporarily. More info: I had opened Query Analyzer under
the failing account on my local box... RClick/ Run as. But if I log directly
onto the box I was trying to run the query from it works fine. Which is why
Im thinking its related to the above article.
"ChrisR" <bla@.noemail.com> wrote in message
news:#uUSqB4EFHA.2608@.TK2MSFTNGP10.phx.gbl...
> Im having a problem with one particular Linked Server Login. I've created
> two of them. Neither of which has an existing Login on the Linked Server
and
> both of which are mapped to a member of SA. In the below examply, Login1
> will work, but Login2 will fail with:
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login1'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> sp_addlinkedsrvlogin @.rmtsrvname = 'server2'
> , @.useself = 'false'
> , @.locallogin = 'domain\Login2'
> , @.rmtuser = 'RmtLogin1'
> , @.rmtpassword = 'password'
> Again, please keep in mind that the Login on the Linked Server is in the
SA
> role, and that the top Login works. Another important tip, both of these
> work successfully on another box, just not the one that counts.
> All ideas are greatly appreciated as Im quite desperate.
> --
> SQL2K SP3
> TIA, ChrisR
>