Help! I am in a jam and need help suggestions and ideas ASAP!
After performing an in-service operating system upgrade from Win 2000 to Win
2003 both of our SQL Server applications are behaving very badly. The SQL
applications are either giving us errors or unable to run at all. Veritas
Backup Exec is unablel to b
rowse the SQL Database and after working with them for several hours they ar
e stumped.
Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix thi
s mess? Or is the best fix going to be an all night server format and reins
tall of Windows 2003, SQL 2000, and all of the applications?
Thanks! in advance for anything you can give me.
NC Beach BumReapply SP3a.
Uninstall Veritas agent.
Reinstall Veritas agent.
What other application connectivity errors are you getting?
Check your alias settings in Client Network Utility. You may need remove
any alias settings that force named pipes connection to a local instance. I
have seen some problems with SQL Agent on those circumstances
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:66808E92-5A64-45AB-91C0-25321EC56C6C@.microsoft.com...
> Help! I am in a jam and need help suggestions and ideas ASAP!
> After performing an in-service operating system upgrade from Win 2000 to
Win 2003 both of our SQL Server applications are behaving very badly. The
SQL applications are either giving us errors or unable to run at all.
Veritas Backup Exec is unablel to browse the SQL Database and after working
with them for several hours they are stumped.
> Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix
this mess? Or is the best fix going to be an all night server format and
reinstall of Windows 2003, SQL 2000, and all of the applications?
> Thanks! in advance for anything you can give me.
> NC Beach Bum
>|||Jeff,
THANKS! for your quick reply.
What I see in the applications are unable to make connections.
The web application is getting this error "Method '~' of object '~' failed."
It looks like the SQL Connections have been trashed.
One Accounting product is getting an error about not being able to log onto
the database.
Another Accounting product on the same SQL Server is not allowing us to post
data to the database.
I can live with the Veritas issues but the Accounting folks are getting a bi
t nasty.
Have you heard of this before and how confident are you that SQL SP3a will p
ut us back to normal?
NC Beach Bum|||"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:DF20331F-C553-48C8-8D31-9A5745A81F24@.microsoft.com...
> Jeff,
> THANKS! for your quick reply.
> What I see in the applications are unable to make connections.
Try to add this in your connection string:
"Network Library=DBMSSOCN"|||Geoff,
I am going to try and update MDAC and the SQL Service Pack
1) Run the MDAC 2.8 install
2) Run the SQL SP3a install
Does this make sense to you and is this the order you would suggest?
Thanks! NC Beach Bum|||That is the correct order. It shouldn't hurt.
You should start checking connectivity an dsee what does and doesn't
connect. Start with IP connectivity (Ping) and then work on SQL
connectivity with query analyzer. Try local and remote from Query Analyzer
and see what happens. Find out what connectivity works and what does not.
If you can connect locally, what does 'SELECT @.@.Version' return? Windows
2003 will disable the IP stack for SQL without SP3a to protect from the
Slammer worm.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:59DBF52D-F7AE-4ACD-81A4-639C8E7E4D95@.microsoft.com...
> Geoff,
> I am going to try and update MDAC and the SQL Service Pack
> 1) Run the MDAC 2.8 install
> 2) Run the SQL SP3a install
> Does this make sense to you and is this the order you would suggest?
> Thanks! NC Beach Bum
Showing posts with label win. Show all posts
Showing posts with label win. Show all posts
Monday, March 26, 2012
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.
Monday, March 12, 2012
HELP! Couple questions for newbie
Hi, I'm new to database and server. I have some questions.
1. Is it hard to connect a computer to a server?
2. Is it possible to connect from win xp (client) to win 2000 (server)?
3. I've tried to connect my computer to server but failed. I cannot find my client computer name on my server.
Can somebody tell me how to connect a client to a server step-by-step? Or maybe is there any online resources i can read about it?
Thank you. I really appreciate it.1. Providing you know your server details and your network is set up to allow you to connect then it sould be easy.
2. Definately possible.
3. First things... make sure your computer can see the server, try pinging it and visa versa make sure the server can see your machine (ping again). Once network connectivity is assured then you can move on to connecting to your server. What are you connecting via? The Enterprise Manager or something else?
1. Is it hard to connect a computer to a server?
2. Is it possible to connect from win xp (client) to win 2000 (server)?
3. I've tried to connect my computer to server but failed. I cannot find my client computer name on my server.
Can somebody tell me how to connect a client to a server step-by-step? Or maybe is there any online resources i can read about it?
Thank you. I really appreciate it.1. Providing you know your server details and your network is set up to allow you to connect then it sould be easy.
2. Definately possible.
3. First things... make sure your computer can see the server, try pinging it and visa versa make sure the server can see your machine (ping again). Once network connectivity is assured then you can move on to connecting to your server. What are you connecting via? The Enterprise Manager or something else?
Subscribe to:
Posts (Atom)