we upgraded servers and now i can't link to an oracle server
old config:
windows2000
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
new config:
windows2003
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
the oracle db is 9.2.
i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005:]
i've scoured the internet and found numerous solutions to this, none of
which work.
i found an article in oracle technet that said to redo all permissions
on the oraclehome
directory. that didn't work.
i made sure the registry entries pointed to the correct oracle dll's.
no help.
i tried the 10g client with latest patch. no help.
i deleted and readded the linked server. no help.
i can use sqlplus or netmanager and connect to the oracle db just fine
from the sql server.
i don't know what else to try.
i'm wondering if it's windows2003 that's screwing things up.
has anybody been able to link to an oracle server from a win2003 server
running sql server sp4?
Some additional questions:
What platform is the Oracle database?
Is connection pooling being used?
What language is doing the call or are you doing linked servers (four level
table qualifier)?
That particular error has a lot of possibles, as you found. Don't want to
re-hash what you have already ruled out.
Joseph R.P. Maloney, CSP,CCP,CDP
"ch" wrote:
> we upgraded servers and now i can't link to an oracle server
> old config:
> windows2000
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> new config:
> windows2003
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> the oracle db is 9.2.
> i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
> returned 0x80004005:]
> i've scoured the internet and found numerous solutions to this, none of
> which work.
> i found an article in oracle technet that said to redo all permissions
> on the oraclehome
> directory. that didn't work.
> i made sure the registry entries pointed to the correct oracle dll's.
> no help.
> i tried the 10g client with latest patch. no help.
> i deleted and readded the linked server. no help.
> i can use sqlplus or netmanager and connect to the oracle db just fine
> from the sql server.
> i don't know what else to try.
> i'm wondering if it's windows2003 that's screwing things up.
> has anybody been able to link to an oracle server from a win2003 server
> running sql server sp4?
>
Showing posts with label linked. Show all posts
Showing posts with label linked. Show all posts
Friday, March 23, 2012
Help! Oracle linked server not working
we upgraded servers and now i can't link to an oracle server
old config:
windows2000
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
new config:
windows2003
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
the oracle db is 9.2.
i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005:]
i've scoured the internet and found numerous solutions to this, none of
which work.
i found an article in oracle technet that said to redo all permissions
on the oraclehome
directory. that didn't work.
i made sure the registry entries pointed to the correct oracle dll's.
no help.
i tried the 10g client with latest patch. no help.
i deleted and readded the linked server. no help.
i can use sqlplus or netmanager and connect to the oracle db just fine
from the sql server.
i don't know what else to try.
i'm wondering if it's windows2003 that's screwing things up.
has anybody been able to link to an oracle server from a win2003 server
running sql server sp4?Some additional questions:
What platform is the Oracle database?
Is connection pooling being used?
What language is doing the call or are you doing linked servers (four level
table qualifier)?
That particular error has a lot of possibles, as you found. Don't want to
re-hash what you have already ruled out.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"ch" wrote:
> we upgraded servers and now i can't link to an oracle server
> old config:
> windows2000
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> new config:
> windows2003
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> the oracle db is 9.2.
> i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
> returned 0x80004005:]
> i've scoured the internet and found numerous solutions to this, none of
> which work.
> i found an article in oracle technet that said to redo all permissions
> on the oraclehome
> directory. that didn't work.
> i made sure the registry entries pointed to the correct oracle dll's.
> no help.
> i tried the 10g client with latest patch. no help.
> i deleted and readded the linked server. no help.
> i can use sqlplus or netmanager and connect to the oracle db just fine
> from the sql server.
> i don't know what else to try.
> i'm wondering if it's windows2003 that's screwing things up.
> has anybody been able to link to an oracle server from a win2003 server
> running sql server sp4?
>
old config:
windows2000
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
new config:
windows2003
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
the oracle db is 9.2.
i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005:]
i've scoured the internet and found numerous solutions to this, none of
which work.
i found an article in oracle technet that said to redo all permissions
on the oraclehome
directory. that didn't work.
i made sure the registry entries pointed to the correct oracle dll's.
no help.
i tried the 10g client with latest patch. no help.
i deleted and readded the linked server. no help.
i can use sqlplus or netmanager and connect to the oracle db just fine
from the sql server.
i don't know what else to try.
i'm wondering if it's windows2003 that's screwing things up.
has anybody been able to link to an oracle server from a win2003 server
running sql server sp4?Some additional questions:
What platform is the Oracle database?
Is connection pooling being used?
What language is doing the call or are you doing linked servers (four level
table qualifier)?
That particular error has a lot of possibles, as you found. Don't want to
re-hash what you have already ruled out.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"ch" wrote:
> we upgraded servers and now i can't link to an oracle server
> old config:
> windows2000
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> new config:
> windows2003
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> the oracle db is 9.2.
> i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
> returned 0x80004005:]
> i've scoured the internet and found numerous solutions to this, none of
> which work.
> i found an article in oracle technet that said to redo all permissions
> on the oraclehome
> directory. that didn't work.
> i made sure the registry entries pointed to the correct oracle dll's.
> no help.
> i tried the 10g client with latest patch. no help.
> i deleted and readded the linked server. no help.
> i can use sqlplus or netmanager and connect to the oracle db just fine
> from the sql server.
> i don't know what else to try.
> i'm wondering if it's windows2003 that's screwing things up.
> has anybody been able to link to an oracle server from a win2003 server
> running sql server sp4?
>
Help! Oracle linked server not working
we upgraded servers and now i can't link to an oracle server
old config:
windows2000
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
new config:
windows2003
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
the oracle db is 9.2.
i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005:]
i've scoured the internet and found numerous solutions to this, none of
which work.
i found an article in oracle technet that said to redo all permissions
on the oraclehome
directory. that didn't work.
i made sure the registry entries pointed to the correct oracle dll's.
no help.
i tried the 10g client with latest patch. no help.
i deleted and readded the linked server. no help.
i can use sqlplus or netmanager and connect to the oracle db just fine
from the sql server.
i don't know what else to try.
i'm wondering if it's windows2003 that's screwing things up.
has anybody been able to link to an oracle server from a win2003 server
running sql server sp4?Some additional questions:
What platform is the Oracle database?
Is connection pooling being used?
What language is doing the call or are you doing linked servers (four level
table qualifier)?
That particular error has a lot of possibles, as you found. Don't want to
re-hash what you have already ruled out.
Joseph R.P. Maloney, CSP,CCP,CDP
"ch" wrote:
> we upgraded servers and now i can't link to an oracle server
> old config:
> windows2000
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> new config:
> windows2003
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> the oracle db is 9.2.
> i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initializ
e
> returned 0x80004005:]
> i've scoured the internet and found numerous solutions to this, none of
> which work.
> i found an article in oracle technet that said to redo all permissions
> on the oraclehome
> directory. that didn't work.
> i made sure the registry entries pointed to the correct oracle dll's.
> no help.
> i tried the 10g client with latest patch. no help.
> i deleted and readded the linked server. no help.
> i can use sqlplus or netmanager and connect to the oracle db just fine
> from the sql server.
> i don't know what else to try.
> i'm wondering if it's windows2003 that's screwing things up.
> has anybody been able to link to an oracle server from a win2003 server
> running sql server sp4?
>
old config:
windows2000
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
new config:
windows2003
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
the oracle db is 9.2.
i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005:]
i've scoured the internet and found numerous solutions to this, none of
which work.
i found an article in oracle technet that said to redo all permissions
on the oraclehome
directory. that didn't work.
i made sure the registry entries pointed to the correct oracle dll's.
no help.
i tried the 10g client with latest patch. no help.
i deleted and readded the linked server. no help.
i can use sqlplus or netmanager and connect to the oracle db just fine
from the sql server.
i don't know what else to try.
i'm wondering if it's windows2003 that's screwing things up.
has anybody been able to link to an oracle server from a win2003 server
running sql server sp4?Some additional questions:
What platform is the Oracle database?
Is connection pooling being used?
What language is doing the call or are you doing linked servers (four level
table qualifier)?
That particular error has a lot of possibles, as you found. Don't want to
re-hash what you have already ruled out.
Joseph R.P. Maloney, CSP,CCP,CDP
"ch" wrote:
> we upgraded servers and now i can't link to an oracle server
> old config:
> windows2000
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> new config:
> windows2003
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> the oracle db is 9.2.
> i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initializ
e
> returned 0x80004005:]
> i've scoured the internet and found numerous solutions to this, none of
> which work.
> i found an article in oracle technet that said to redo all permissions
> on the oraclehome
> directory. that didn't work.
> i made sure the registry entries pointed to the correct oracle dll's.
> no help.
> i tried the 10g client with latest patch. no help.
> i deleted and readded the linked server. no help.
> i can use sqlplus or netmanager and connect to the oracle db just fine
> from the sql server.
> i don't know what else to try.
> i'm wondering if it's windows2003 that's screwing things up.
> has anybody been able to link to an oracle server from a win2003 server
> running sql server sp4?
>
Wednesday, March 21, 2012
HELP! Linked Server Problem
I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 instanc
e
on a 64bit Win 2003 Server. Both systems are using the same user id &
password.
Both instances use windows authentication mode.
In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
linked server to the SQL 2000 instance. I used the login as the current logi
n
context.
From the server itself, I can execute queries from the linked server.
My problems lies when I use the SQL Server Enterprise Manager in my computer
(I am in the admin group on both machines and I have sysadmin roles on both)
when executing the same query I get:
OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
"Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I dont understand this as I'm using Windows Autherntication on everything.Have you tried to use Named Pipes on your client network configuration?
"Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current
> login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my
> computer
> (I am in the admin group on both machines and I have sysadmin roles on
> both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote
> host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.|||Tried Pipes, but not the issue.
For some reason, the windows authentication mode is not working properly.
"Immy" wrote:
> Have you tried to use Named Pipes on your client network configuration?
> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>
>|||Howard Carr wrote:[vbcol=seagreen]
> Tried Pipes, but not the issue.
> For some reason, the windows authentication mode is not working properly.
> "Immy" wrote:
>
You might take a look at Security Account Delegation in Books On Line.
In order to use Windows authentication you must enable the servers for
Account Delegation, and also the SQL server usr account must be enabled
for delegation. I think the problem is that when you try from your own
machine, you use an account and computer that isn't trusted.
Regards
Steen|||I believe you are experincing the two-hop problem? You can't pass Windows
authentication credentials across a link in SQL Server. If you define a
static SQL ID for the link and use that, you should be fine
"Howard Carr" wrote:
> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 insta
nce
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current lo
gin
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my comput
er
> (I am in the admin group on both machines and I have sysadmin roles on bot
h)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote hos
t.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
e
on a 64bit Win 2003 Server. Both systems are using the same user id &
password.
Both instances use windows authentication mode.
In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
linked server to the SQL 2000 instance. I used the login as the current logi
n
context.
From the server itself, I can execute queries from the linked server.
My problems lies when I use the SQL Server Enterprise Manager in my computer
(I am in the admin group on both machines and I have sysadmin roles on both)
when executing the same query I get:
OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
"Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I dont understand this as I'm using Windows Autherntication on everything.Have you tried to use Named Pipes on your client network configuration?
"Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current
> login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my
> computer
> (I am in the admin group on both machines and I have sysadmin roles on
> both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote
> host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.|||Tried Pipes, but not the issue.
For some reason, the windows authentication mode is not working properly.
"Immy" wrote:
> Have you tried to use Named Pipes on your client network configuration?
> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>
>|||Howard Carr wrote:[vbcol=seagreen]
> Tried Pipes, but not the issue.
> For some reason, the windows authentication mode is not working properly.
> "Immy" wrote:
>
You might take a look at Security Account Delegation in Books On Line.
In order to use Windows authentication you must enable the servers for
Account Delegation, and also the SQL server usr account must be enabled
for delegation. I think the problem is that when you try from your own
machine, you use an account and computer that isn't trusted.
Regards
Steen|||I believe you are experincing the two-hop problem? You can't pass Windows
authentication credentials across a link in SQL Server. If you define a
static SQL ID for the link and use that, you should be fine
"Howard Carr" wrote:
> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 insta
nce
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current lo
gin
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my comput
er
> (I am in the admin group on both machines and I have sysadmin roles on bot
h)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote hos
t.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
HELP! Linked Server Problem
I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 instance
on a 64bit Win 2003 Server. Both systems are using the same user id &
password.
Both instances use windows authentication mode.
In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
linked server to the SQL 2000 instance. I used the login as the current login
context.
From the server itself, I can execute queries from the linked server.
My problems lies when I use the SQL Server Enterprise Manager in my computer
(I am in the admin group on both machines and I have sysadmin roles on both)
when executing the same query I get:
OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
"Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I dont understand this as I'm using Windows Autherntication on everything.
Have you tried to use Named Pipes on your client network configuration?
"Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current
> login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my
> computer
> (I am in the admin group on both machines and I have sysadmin roles on
> both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote
> host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
|||Tried Pipes, but not the issue.
For some reason, the windows authentication mode is not working properly.
"Immy" wrote:
> Have you tried to use Named Pipes on your client network configuration?
> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>
>
|||Howard Carr wrote:[vbcol=seagreen]
> Tried Pipes, but not the issue.
> For some reason, the windows authentication mode is not working properly.
> "Immy" wrote:
You might take a look at Security Account Delegation in Books On Line.
In order to use Windows authentication you must enable the servers for
Account Delegation, and also the SQL server usr account must be enabled
for delegation. I think the problem is that when you try from your own
machine, you use an account and computer that isn't trusted.
Regards
Steen
|||I believe you are experincing the two-hop problem? You can't pass Windows
authentication credentials across a link in SQL Server. If you define a
static SQL ID for the link and use that, you should be fine
"Howard Carr" wrote:
> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my computer
> (I am in the admin group on both machines and I have sysadmin roles on both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
on a 64bit Win 2003 Server. Both systems are using the same user id &
password.
Both instances use windows authentication mode.
In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
linked server to the SQL 2000 instance. I used the login as the current login
context.
From the server itself, I can execute queries from the linked server.
My problems lies when I use the SQL Server Enterprise Manager in my computer
(I am in the admin group on both machines and I have sysadmin roles on both)
when executing the same query I get:
OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
"Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I dont understand this as I'm using Windows Autherntication on everything.
Have you tried to use Named Pipes on your client network configuration?
"Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current
> login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my
> computer
> (I am in the admin group on both machines and I have sysadmin roles on
> both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote
> host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
|||Tried Pipes, but not the issue.
For some reason, the windows authentication mode is not working properly.
"Immy" wrote:
> Have you tried to use Named Pipes on your client network configuration?
> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>
>
|||Howard Carr wrote:[vbcol=seagreen]
> Tried Pipes, but not the issue.
> For some reason, the windows authentication mode is not working properly.
> "Immy" wrote:
You might take a look at Security Account Delegation in Books On Line.
In order to use Windows authentication you must enable the servers for
Account Delegation, and also the SQL server usr account must be enabled
for delegation. I think the problem is that when you try from your own
machine, you use an account and computer that isn't trusted.
Regards
Steen
|||I believe you are experincing the two-hop problem? You can't pass Windows
authentication credentials across a link in SQL Server. If you define a
static SQL ID for the link and use that, you should be fine
"Howard Carr" wrote:
> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my computer
> (I am in the admin group on both machines and I have sysadmin roles on both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
HELP! Linked Server Problem
I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 instance
on a 64bit Win 2003 Server. Both systems are using the same user id &
password.
Both instances use windows authentication mode.
In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
linked server to the SQL 2000 instance. I used the login as the current login
context.
From the server itself, I can execute queries from the linked server.
My problems lies when I use the SQL Server Enterprise Manager in my computer
(I am in the admin group on both machines and I have sysadmin roles on both)
when executing the same query I get:
OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
"Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I dont understand this as I'm using Windows Autherntication on everything.Have you tried to use Named Pipes on your client network configuration?
"Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current
> login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my
> computer
> (I am in the admin group on both machines and I have sysadmin roles on
> both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote
> host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.|||Tried Pipes, but not the issue.
For some reason, the windows authentication mode is not working properly.
"Immy" wrote:
> Have you tried to use Named Pipes on your client network configuration?
> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
> >I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
> >instance
> > on a 64bit Win 2003 Server. Both systems are using the same user id &
> > password.
> > Both instances use windows authentication mode.
> >
> > In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> > linked server to the SQL 2000 instance. I used the login as the current
> > login
> > context.
> > From the server itself, I can execute queries from the linked server.
> >
> > My problems lies when I use the SQL Server Enterprise Manager in my
> > computer
> > (I am in the admin group on both machines and I have sysadmin roles on
> > both)
> > when executing the same query I get:
> > OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> > "Communication link failure".
> > Msg 10054, Level 16, State 1, Line 0
> > TCP Provider: An existing connection was forcibly closed by the remote
> > host.
> > Msg 18456, Level 14, State 1, Line 0
> > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > I dont understand this as I'm using Windows Autherntication on everything.
>
>|||Howard Carr wrote:
> Tried Pipes, but not the issue.
> For some reason, the windows authentication mode is not working properly.
> "Immy" wrote:
>> Have you tried to use Named Pipes on your client network configuration?
>> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
>> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>> instance
>> on a 64bit Win 2003 Server. Both systems are using the same user id &
>> password.
>> Both instances use windows authentication mode.
>> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
>> linked server to the SQL 2000 instance. I used the login as the current
>> login
>> context.
>> From the server itself, I can execute queries from the linked server.
>> My problems lies when I use the SQL Server Enterprise Manager in my
>> computer
>> (I am in the admin group on both machines and I have sysadmin roles on
>> both)
>> when executing the same query I get:
>> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
>> "Communication link failure".
>> Msg 10054, Level 16, State 1, Line 0
>> TCP Provider: An existing connection was forcibly closed by the remote
>> host.
>> Msg 18456, Level 14, State 1, Line 0
>> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>> I dont understand this as I'm using Windows Autherntication on everything.
>>
You might take a look at Security Account Delegation in Books On Line.
In order to use Windows authentication you must enable the servers for
Account Delegation, and also the SQL server usr account must be enabled
for delegation. I think the problem is that when you try from your own
machine, you use an account and computer that isn't trusted.
Regards
Steen|||I believe you are experincing the two-hop problem? You can't pass Windows
authentication credentials across a link in SQL Server. If you define a
static SQL ID for the link and use that, you should be fine
"Howard Carr" wrote:
> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my computer
> (I am in the admin group on both machines and I have sysadmin roles on both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
on a 64bit Win 2003 Server. Both systems are using the same user id &
password.
Both instances use windows authentication mode.
In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
linked server to the SQL 2000 instance. I used the login as the current login
context.
From the server itself, I can execute queries from the linked server.
My problems lies when I use the SQL Server Enterprise Manager in my computer
(I am in the admin group on both machines and I have sysadmin roles on both)
when executing the same query I get:
OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
"Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I dont understand this as I'm using Windows Autherntication on everything.Have you tried to use Named Pipes on your client network configuration?
"Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current
> login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my
> computer
> (I am in the admin group on both machines and I have sysadmin roles on
> both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote
> host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.|||Tried Pipes, but not the issue.
For some reason, the windows authentication mode is not working properly.
"Immy" wrote:
> Have you tried to use Named Pipes on your client network configuration?
> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
> >I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
> >instance
> > on a 64bit Win 2003 Server. Both systems are using the same user id &
> > password.
> > Both instances use windows authentication mode.
> >
> > In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> > linked server to the SQL 2000 instance. I used the login as the current
> > login
> > context.
> > From the server itself, I can execute queries from the linked server.
> >
> > My problems lies when I use the SQL Server Enterprise Manager in my
> > computer
> > (I am in the admin group on both machines and I have sysadmin roles on
> > both)
> > when executing the same query I get:
> > OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> > "Communication link failure".
> > Msg 10054, Level 16, State 1, Line 0
> > TCP Provider: An existing connection was forcibly closed by the remote
> > host.
> > Msg 18456, Level 14, State 1, Line 0
> > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > I dont understand this as I'm using Windows Autherntication on everything.
>
>|||Howard Carr wrote:
> Tried Pipes, but not the issue.
> For some reason, the windows authentication mode is not working properly.
> "Immy" wrote:
>> Have you tried to use Named Pipes on your client network configuration?
>> "Howard Carr" <HowardCarr@.discussions.microsoft.com> wrote in message
>> news:BB430B53-5AA8-47FA-B8EB-215ABF91BB49@.microsoft.com...
>> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005
>> instance
>> on a 64bit Win 2003 Server. Both systems are using the same user id &
>> password.
>> Both instances use windows authentication mode.
>> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
>> linked server to the SQL 2000 instance. I used the login as the current
>> login
>> context.
>> From the server itself, I can execute queries from the linked server.
>> My problems lies when I use the SQL Server Enterprise Manager in my
>> computer
>> (I am in the admin group on both machines and I have sysadmin roles on
>> both)
>> when executing the same query I get:
>> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
>> "Communication link failure".
>> Msg 10054, Level 16, State 1, Line 0
>> TCP Provider: An existing connection was forcibly closed by the remote
>> host.
>> Msg 18456, Level 14, State 1, Line 0
>> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>> I dont understand this as I'm using Windows Autherntication on everything.
>>
You might take a look at Security Account Delegation in Books On Line.
In order to use Windows authentication you must enable the servers for
Account Delegation, and also the SQL server usr account must be enabled
for delegation. I think the problem is that when you try from your own
machine, you use an account and computer that isn't trusted.
Regards
Steen|||I believe you are experincing the two-hop problem? You can't pass Windows
authentication credentials across a link in SQL Server. If you define a
static SQL ID for the link and use that, you should be fine
"Howard Carr" wrote:
> I have a SQL 2000 instance on a 32 bit Win2000 server and a SQL 2005 instance
> on a 64bit Win 2003 Server. Both systems are using the same user id &
> password.
> Both instances use windows authentication mode.
> In the SQL Server Enterprise Manager on the SQL 2005 instance I created a
> linked server to the SQL 2000 instance. I used the login as the current login
> context.
> From the server itself, I can execute queries from the linked server.
> My problems lies when I use the SQL Server Enterprise Manager in my computer
> (I am in the admin group on both machines and I have sysadmin roles on both)
> when executing the same query I get:
> OLE DB provider "SQLNCLI" for linked server "SQL2000" returned message
> "Communication link failure".
> Msg 10054, Level 16, State 1, Line 0
> TCP Provider: An existing connection was forcibly closed by the remote host.
> Msg 18456, Level 14, State 1, Line 0
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
> I dont understand this as I'm using Windows Autherntication on everything.
Help! Linked Server between 6.5 and 2000 error
Hi
I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
on Server A, I added Server B as a remote server and added a remote login
(trust) from Server B via Enterprise Manager.
on Server B, I added Server A as a linked server and add remote login (the
same login as server A and password) via Enterprise manager.
On Server B, I can make RPC on Server A. But on Server A, when I do the
following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at Line:0
Message:Could not connect to server 'ServerB' because 'mylogin' is not
defined as a remote login at the server.
What is the problem here? I actually already have sa have the same setting
between A and B. It works both ways. Why the one I just added does not work?
Need help!
Julia
> Hi
> I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
> on Server A, I added Server B as a remote server and added a remote login
> (trust) from Server B via Enterprise Manager.
> on Server B, I added Server A as a linked server and add remote login
(the
> same login as server A and password) via Enterprise manager.
> On Server B, I can make RPC on Server A. But on Server A, when I do the
> following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at
Line:0
> Message:Could not connect to server 'ServerB' because 'mylogin' is not
> defined as a remote login at the server.
> What is the problem here? I actually already have sa have the same
setting
> between A and B. It works both ways. Why the one I just added does not
work?
> Need help!
> Julia
SQL 6.5 connecting to SQL 2000 won't work. SQL 2000 did not exist when SQL
6.5 was designed. Hence, SQL 6.5 does not support SQL Server 2000 as a
remote server.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
on Server A, I added Server B as a remote server and added a remote login
(trust) from Server B via Enterprise Manager.
on Server B, I added Server A as a linked server and add remote login (the
same login as server A and password) via Enterprise manager.
On Server B, I can make RPC on Server A. But on Server A, when I do the
following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at Line:0
Message:Could not connect to server 'ServerB' because 'mylogin' is not
defined as a remote login at the server.
What is the problem here? I actually already have sa have the same setting
between A and B. It works both ways. Why the one I just added does not work?
Need help!
Julia
> Hi
> I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
> on Server A, I added Server B as a remote server and added a remote login
> (trust) from Server B via Enterprise Manager.
> on Server B, I added Server A as a linked server and add remote login
(the
> same login as server A and password) via Enterprise manager.
> On Server B, I can make RPC on Server A. But on Server A, when I do the
> following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at
Line:0
> Message:Could not connect to server 'ServerB' because 'mylogin' is not
> defined as a remote login at the server.
> What is the problem here? I actually already have sa have the same
setting
> between A and B. It works both ways. Why the one I just added does not
work?
> Need help!
> Julia
SQL 6.5 connecting to SQL 2000 won't work. SQL 2000 did not exist when SQL
6.5 was designed. Hence, SQL 6.5 does not support SQL Server 2000 as a
remote server.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
Help! Linked Server between 6.5 and 2000 error
Hi
I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
on Server A, I added Server B as a remote server and added a remote login
(trust) from Server B via Enterprise Manager.
on Server B, I added Server A as a linked server and add remote login (the
same login as server A and password) via Enterprise manager.
On Server B, I can make RPC on Server A. But on Server A, when I do the
following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at Line:0
Message:Could not connect to server 'ServerB' because 'mylogin' is not
defined as a remote login at the server.
What is the problem here? I actually already have sa have the same setting
between A and B. It works both ways. Why the one I just added does not wor
k?
Need help!
Julia> Hi
> I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
> on Server A, I added Server B as a remote server and added a remote login
> (trust) from Server B via Enterprise Manager.
> on Server B, I added Server A as a linked server and add remote login
(the
> same login as server A and password) via Enterprise manager.
> On Server B, I can make RPC on Server A. But on Server A, when I do the
> following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at
Line:0
> Message:Could not connect to server 'ServerB' because 'mylogin' is not
> defined as a remote login at the server.
> What is the problem here? I actually already have sa have the same
setting
> between A and B. It works both ways. Why the one I just added does not
work?
> Need help!
> Julia
--
SQL 6.5 connecting to SQL 2000 won't work. SQL 2000 did not exist when SQL
6.5 was designed. Hence, SQL 6.5 does not support SQL Server 2000 as a
remote server.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
on Server A, I added Server B as a remote server and added a remote login
(trust) from Server B via Enterprise Manager.
on Server B, I added Server A as a linked server and add remote login (the
same login as server A and password) via Enterprise manager.
On Server B, I can make RPC on Server A. But on Server A, when I do the
following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at Line:0
Message:Could not connect to server 'ServerB' because 'mylogin' is not
defined as a remote login at the server.
What is the problem here? I actually already have sa have the same setting
between A and B. It works both ways. Why the one I just added does not wor
k?
Need help!
Julia> Hi
> I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
> on Server A, I added Server B as a remote server and added a remote login
> (trust) from Server B via Enterprise Manager.
> on Server B, I added Server A as a linked server and add remote login
(the
> same login as server A and password) via Enterprise manager.
> On Server B, I can make RPC on Server A. But on Server A, when I do the
> following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at
Line:0
> Message:Could not connect to server 'ServerB' because 'mylogin' is not
> defined as a remote login at the server.
> What is the problem here? I actually already have sa have the same
setting
> between A and B. It works both ways. Why the one I just added does not
work?
> Need help!
> Julia
--
SQL 6.5 connecting to SQL 2000 won't work. SQL 2000 did not exist when SQL
6.5 was designed. Hence, SQL 6.5 does not support SQL Server 2000 as a
remote server.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Help! Linked Server between 6.5 and 2000 error
Hi
I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
on Server A, I added Server B as a remote server and added a remote login
(trust) from Server B via Enterprise Manager.
on Server B, I added Server A as a linked server and add remote login (the
same login as server A and password) via Enterprise manager.
On Server B, I can make RPC on Server A. But on Server A, when I do the
following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at Line:0
Message:Could not connect to server 'ServerB' because 'mylogin' is not
defined as a remote login at the server.
What is the problem here? I actually already have sa have the same setting
between A and B. It works both ways. Why the one I just added does not work?
Need help!
Julia> Hi
> I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
> on Server A, I added Server B as a remote server and added a remote login
> (trust) from Server B via Enterprise Manager.
> on Server B, I added Server A as a linked server and add remote login
(the
> same login as server A and password) via Enterprise manager.
> On Server B, I can make RPC on Server A. But on Server A, when I do the
> following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at
Line:0
> Message:Could not connect to server 'ServerB' because 'mylogin' is not
> defined as a remote login at the server.
> What is the problem here? I actually already have sa have the same
setting
> between A and B. It works both ways. Why the one I just added does not
work?
> Need help!
> Julia
--
SQL 6.5 connecting to SQL 2000 won't work. SQL 2000 did not exist when SQL
6.5 was designed. Hence, SQL 6.5 does not support SQL Server 2000 as a
remote server.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
on Server A, I added Server B as a remote server and added a remote login
(trust) from Server B via Enterprise Manager.
on Server B, I added Server A as a linked server and add remote login (the
same login as server A and password) via Enterprise manager.
On Server B, I can make RPC on Server A. But on Server A, when I do the
following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at Line:0
Message:Could not connect to server 'ServerB' because 'mylogin' is not
defined as a remote login at the server.
What is the problem here? I actually already have sa have the same setting
between A and B. It works both ways. Why the one I just added does not work?
Need help!
Julia> Hi
> I have 2 servers: Server A: SQL 6.5 and Server B: SQL 2000.
> on Server A, I added Server B as a remote server and added a remote login
> (trust) from Server B via Enterprise Manager.
> on Server B, I added Server A as a linked server and add remote login
(the
> same login as server A and password) via Enterprise manager.
> On Server B, I can make RPC on Server A. But on Server A, when I do the
> following: serverB.mydb.dbo.sp_helpuser, I got error: Error:18483 at
Line:0
> Message:Could not connect to server 'ServerB' because 'mylogin' is not
> defined as a remote login at the server.
> What is the problem here? I actually already have sa have the same
setting
> between A and B. It works both ways. Why the one I just added does not
work?
> Need help!
> Julia
--
SQL 6.5 connecting to SQL 2000 won't work. SQL 2000 did not exist when SQL
6.5 was designed. Hence, SQL 6.5 does not support SQL Server 2000 as a
remote server.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Monday, March 19, 2012
HELP! How get user NT login
Hi,
I want to retrieve reports that use the Windwos authentication to filter
data linked to the user (e.g.: only sales for a specific user)
I tried to use a parameter which uses the property
system.security.principal.WindowsIdentity.GetCurrent.name,
It works fine when I run it from the designer, but when I deploy the report
on the ReportManager, I go an error:
Error during processing of 'login' report parameter.
(rsReportParameterProcessingError)
Any idea about this problem, or how to get the login by using another way?
Thanks,
StéphanieYou can use the built in RS parameter User!UserID.Value. This returns the
Windows login name, pre-Windows 2000 style.
If you need to strip of the domain name, I've written a post on how to do it
here
http://blogs.spipp.net/kaisa/archive/2005/04/15/255.aspx
Kaisa
"StephyB" <ssss@.zz.fr> wrote in message
news:%23GBha18zFHA.800@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I want to retrieve reports that use the Windwos authentication to filter
> data linked to the user (e.g.: only sales for a specific user)
> I tried to use a parameter which uses the property
> system.security.principal.WindowsIdentity.GetCurrent.name,
> It works fine when I run it from the designer, but when I deploy the
> report on the ReportManager, I go an error:
> Error during processing of 'login' report parameter.
> (rsReportParameterProcessingError)
> Any idea about this problem, or how to get the login by using another way?
> Thanks,
> Stéphanie
>
I want to retrieve reports that use the Windwos authentication to filter
data linked to the user (e.g.: only sales for a specific user)
I tried to use a parameter which uses the property
system.security.principal.WindowsIdentity.GetCurrent.name,
It works fine when I run it from the designer, but when I deploy the report
on the ReportManager, I go an error:
Error during processing of 'login' report parameter.
(rsReportParameterProcessingError)
Any idea about this problem, or how to get the login by using another way?
Thanks,
StéphanieYou can use the built in RS parameter User!UserID.Value. This returns the
Windows login name, pre-Windows 2000 style.
If you need to strip of the domain name, I've written a post on how to do it
here
http://blogs.spipp.net/kaisa/archive/2005/04/15/255.aspx
Kaisa
"StephyB" <ssss@.zz.fr> wrote in message
news:%23GBha18zFHA.800@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I want to retrieve reports that use the Windwos authentication to filter
> data linked to the user (e.g.: only sales for a specific user)
> I tried to use a parameter which uses the property
> system.security.principal.WindowsIdentity.GetCurrent.name,
> It works fine when I run it from the designer, but when I deploy the
> report on the ReportManager, I go an error:
> Error during processing of 'login' report parameter.
> (rsReportParameterProcessingError)
> Any idea about this problem, or how to get the login by using another way?
> Thanks,
> Stéphanie
>
Monday, February 27, 2012
HELP!
hi!
I have a table who name is table0. its have a values like colum0: 01 colum1
: d01 and other table(this name is table1) have linked values to 01 and
d01. I want to update d01 value in table1, look from table0. I have
32000-35000 value in table0 and table1.So how can I do it?
Thanks,,,,,,
<m_guner18@.hotmail.com> wrote in message news:...
> hi!
> I have a table who name is table0. its have a values like colum0: 01
colum1
> : d01 and other table(this name is table1) have linked values to 01 and
> d01. I want to update d01 value in table1, look from table0. I have
> 32000-35000 value in table0 and table1.So how can I do it?
> Thanks,,,,,,
>
|||update table0
set colum0= 01, colum1= d01
from table0,table1
where table1.column0=table0.column0 and table1.column1=table0.column1
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"m_guner18@.hotmail.com" wrote:
> hi!
> I have a table who name is table0. its have a values like colum0: 01 colum1
> : d01 and other table(this name is table1) have linked values to 01 and
> d01. I want to update d01 value in table1, look from table0. I have
> 32000-35000 value in table0 and table1.So how can I do it?
> Thanks,,,,,,
>
>
I have a table who name is table0. its have a values like colum0: 01 colum1
: d01 and other table(this name is table1) have linked values to 01 and
d01. I want to update d01 value in table1, look from table0. I have
32000-35000 value in table0 and table1.So how can I do it?
Thanks,,,,,,
<m_guner18@.hotmail.com> wrote in message news:...
> hi!
> I have a table who name is table0. its have a values like colum0: 01
colum1
> : d01 and other table(this name is table1) have linked values to 01 and
> d01. I want to update d01 value in table1, look from table0. I have
> 32000-35000 value in table0 and table1.So how can I do it?
> Thanks,,,,,,
>
|||update table0
set colum0= 01, colum1= d01
from table0,table1
where table1.column0=table0.column0 and table1.column1=table0.column1
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"m_guner18@.hotmail.com" wrote:
> hi!
> I have a table who name is table0. its have a values like colum0: 01 colum1
> : d01 and other table(this name is table1) have linked values to 01 and
> d01. I want to update d01 value in table1, look from table0. I have
> 32000-35000 value in table0 and table1.So how can I do it?
> Thanks,,,,,,
>
>
Help!
Can anyone explain me what i am doing wrong:
I have a script that creates a linked server to them exec
a cmd through it.. when i do this through a cursor i get
this error:
MSDTC on server XPTO is unavailable (whcih is not true)
The operation could not be performed because the OLE DB
provider was unable to begin a ditributed transaction.
However if i do it seperatley.. without cursor.. it works..
Can anyone help me?
P.S
I posted a previous question asking about how to insert
sp_space used in a table.. however either way suggest
doesnt work.. any other suggestions?First of all choose an appropriate subject for your
posting. We all need help here but obviously some are
expert in one domain and others in a different domain.
Your subject does not help your cause.
Second what verison of Sql are you using? Can you post the
actual error message and text. There are a few bugs with
Linked servers and i suspect you are encoutering one.
>--Original Message--
>Can anyone explain me what i am doing wrong:
>I have a script that creates a linked server to them exec
>a cmd through it.. when i do this through a cursor i get
>this error:
>MSDTC on server XPTO is unavailable (whcih is not true)
>The operation could not be performed because the OLE DB
>provider was unable to begin a ditributed transaction.
>However if i do it seperatley.. without cursor.. it
works..
>Can anyone help me?
>P.S
>I posted a previous question asking about how to insert
>sp_space used in a table.. however either way suggest
>doesnt work.. any other suggestions?
>.
>
I have a script that creates a linked server to them exec
a cmd through it.. when i do this through a cursor i get
this error:
MSDTC on server XPTO is unavailable (whcih is not true)
The operation could not be performed because the OLE DB
provider was unable to begin a ditributed transaction.
However if i do it seperatley.. without cursor.. it works..
Can anyone help me?
P.S
I posted a previous question asking about how to insert
sp_space used in a table.. however either way suggest
doesnt work.. any other suggestions?First of all choose an appropriate subject for your
posting. We all need help here but obviously some are
expert in one domain and others in a different domain.
Your subject does not help your cause.
Second what verison of Sql are you using? Can you post the
actual error message and text. There are a few bugs with
Linked servers and i suspect you are encoutering one.
>--Original Message--
>Can anyone explain me what i am doing wrong:
>I have a script that creates a linked server to them exec
>a cmd through it.. when i do this through a cursor i get
>this error:
>MSDTC on server XPTO is unavailable (whcih is not true)
>The operation could not be performed because the OLE DB
>provider was unable to begin a ditributed transaction.
>However if i do it seperatley.. without cursor.. it
works..
>Can anyone help me?
>P.S
>I posted a previous question asking about how to insert
>sp_space used in a table.. however either way suggest
>doesnt work.. any other suggestions?
>.
>
Sunday, February 19, 2012
HELP WITH UPDATE QUERY AND INNER JOIN AND OPENQUERY
If some could show me the syntax for updating a table in my database
with information in a linked table. the table I want to update is
called WorkList and I want to create an inner join query to a linked
table called public.FISCAL. This is all I have so far to create the
join...
SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
Now how can I change it to make and Update query on field B.[I-Plan] =
A.[I_PLAN]?
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join SCH.[public].FISCAL
on Account_ID = B.[ACCOUNT#]
"mike11d11" wrote:
> If some could show me the syntax for updating a table in my database
> with information in a linked table. the table I want to update is
> called WorkList and I want to create an inner join query to a linked
> table called public.FISCAL. This is all I have so far to create the
> join...
> SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
> AS A
> INNER JOIN WorkList AS B
> ON A.Account_ID = B.[ACCOUNT#]
> Now how can I change it to make and Update query on field B.[I-Plan] =
> A.[I_PLAN]?
>
|||So this is what I have...
Select * FROM OPENQUERY(SCH,'SELECT [Account_ID], [I_PLAN] FROM
[public.FISCAL]') AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join A
on Account_ID = B.[ACCOUNT#]
I'll give it a try!
|||Here is the error I get when I use it.
Server: Msg 208, Level 16, State 1, Line 4
Invalid object name 'SCH.public.FISCAL'.
|||anybody have an idea?
with information in a linked table. the table I want to update is
called WorkList and I want to create an inner join query to a linked
table called public.FISCAL. This is all I have so far to create the
join...
SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
Now how can I change it to make and Update query on field B.[I-Plan] =
A.[I_PLAN]?
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join SCH.[public].FISCAL
on Account_ID = B.[ACCOUNT#]
"mike11d11" wrote:
> If some could show me the syntax for updating a table in my database
> with information in a linked table. the table I want to update is
> called WorkList and I want to create an inner join query to a linked
> table called public.FISCAL. This is all I have so far to create the
> join...
> SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
> AS A
> INNER JOIN WorkList AS B
> ON A.Account_ID = B.[ACCOUNT#]
> Now how can I change it to make and Update query on field B.[I-Plan] =
> A.[I_PLAN]?
>
|||So this is what I have...
Select * FROM OPENQUERY(SCH,'SELECT [Account_ID], [I_PLAN] FROM
[public.FISCAL]') AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join A
on Account_ID = B.[ACCOUNT#]
I'll give it a try!
|||Here is the error I get when I use it.
Server: Msg 208, Level 16, State 1, Line 4
Invalid object name 'SCH.public.FISCAL'.
|||anybody have an idea?
HELP WITH UPDATE QUERY AND INNER JOIN AND OPENQUERY
If some could show me the syntax for updating a table in my database
with information in a linked table. the table I want to update is
called WorkList and I want to create an inner join query to a linked
table called public.FISCAL. This is all I have so far to create the
join...
SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
Now how can I change it to make and Update query on field B.[I-Plan] =
A.[I_PLAN]?update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join SCH.[public].FISCAL
on Account_ID = B.[ACCOUNT#]
"mike11d11" wrote:
> If some could show me the syntax for updating a table in my database
> with information in a linked table. the table I want to update is
> called WorkList and I want to create an inner join query to a linked
> table called public.FISCAL. This is all I have so far to create the
> join...
> SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]'
)
> AS A
> INNER JOIN WorkList AS B
> ON A.Account_ID = B.[ACCOUNT#]
> Now how can I change it to make and Update query on field B.[I-Plan] =
> A.[I_PLAN]?
>|||So this is what I have...
Select * FROM OPENQUERY(SCH,'SELECT [Account_ID], [I_PLAN] FROM
[public.FISCAL]') AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join A
on Account_ID = B.[ACCOUNT#]
I'll give it a try!|||Here is the error I get when I use it.
Server: Msg 208, Level 16, State 1, Line 4
Invalid object name 'SCH.public.FISCAL'.|||anybody have an idea?
with information in a linked table. the table I want to update is
called WorkList and I want to create an inner join query to a linked
table called public.FISCAL. This is all I have so far to create the
join...
SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
Now how can I change it to make and Update query on field B.[I-Plan] =
A.[I_PLAN]?update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join SCH.[public].FISCAL
on Account_ID = B.[ACCOUNT#]
"mike11d11" wrote:
> If some could show me the syntax for updating a table in my database
> with information in a linked table. the table I want to update is
> called WorkList and I want to create an inner join query to a linked
> table called public.FISCAL. This is all I have so far to create the
> join...
> SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]'
)
> AS A
> INNER JOIN WorkList AS B
> ON A.Account_ID = B.[ACCOUNT#]
> Now how can I change it to make and Update query on field B.[I-Plan] =
> A.[I_PLAN]?
>|||So this is what I have...
Select * FROM OPENQUERY(SCH,'SELECT [Account_ID], [I_PLAN] FROM
[public.FISCAL]') AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join A
on Account_ID = B.[ACCOUNT#]
I'll give it a try!|||Here is the error I get when I use it.
Server: Msg 208, Level 16, State 1, Line 4
Invalid object name 'SCH.public.FISCAL'.|||anybody have an idea?
HELP WITH UPDATE QUERY AND INNER JOIN AND OPENQUERY
If some could show me the syntax for updating a table in my database
with information in a linked table. the table I want to update is
called WorkList and I want to create an inner join query to a linked
table called public.FISCAL. This is all I have so far to create the
join...
SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
Now how can I change it to make and Update query on field B.[I-Plan] = A.[I_PLAN]?update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join SCH.[public].FISCAL
on Account_ID = B.[ACCOUNT#]
"mike11d11" wrote:
> If some could show me the syntax for updating a table in my database
> with information in a linked table. the table I want to update is
> called WorkList and I want to create an inner join query to a linked
> table called public.FISCAL. This is all I have so far to create the
> join...
> SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
> AS A
> INNER JOIN WorkList AS B
> ON A.Account_ID = B.[ACCOUNT#]
> Now how can I change it to make and Update query on field B.[I-Plan] => A.[I_PLAN]?
>|||So this is what I have...
Select * FROM OPENQUERY(SCH,'SELECT [Account_ID], [I_PLAN] FROM
[public.FISCAL]') AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join A
on Account_ID = B.[ACCOUNT#]
I'll give it a try!|||Here is the error I get when I use it.
Server: Msg 208, Level 16, State 1, Line 4
Invalid object name 'SCH.public.FISCAL'.|||anybody have an idea?
with information in a linked table. the table I want to update is
called WorkList and I want to create an inner join query to a linked
table called public.FISCAL. This is all I have so far to create the
join...
SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
Now how can I change it to make and Update query on field B.[I-Plan] = A.[I_PLAN]?update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join SCH.[public].FISCAL
on Account_ID = B.[ACCOUNT#]
"mike11d11" wrote:
> If some could show me the syntax for updating a table in my database
> with information in a linked table. the table I want to update is
> called WorkList and I want to create an inner join query to a linked
> table called public.FISCAL. This is all I have so far to create the
> join...
> SELECT DSK FROM OPENQUERY(SCH,'SELECT Account_ID FROM [public.FISCAL]')
> AS A
> INNER JOIN WorkList AS B
> ON A.Account_ID = B.[ACCOUNT#]
> Now how can I change it to make and Update query on field B.[I-Plan] => A.[I_PLAN]?
>|||So this is what I have...
Select * FROM OPENQUERY(SCH,'SELECT [Account_ID], [I_PLAN] FROM
[public.FISCAL]') AS A
INNER JOIN WorkList AS B
ON A.Account_ID = B.[ACCOUNT#]
update WorkList
set [I-Plan] = A.[I_PLAN]
from Worklist B
inner join A
on Account_ID = B.[ACCOUNT#]
I'll give it a try!|||Here is the error I get when I use it.
Server: Msg 208, Level 16, State 1, Line 4
Invalid object name 'SCH.public.FISCAL'.|||anybody have an idea?
Subscribe to:
Posts (Atom)