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.
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Wednesday, March 21, 2012
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.
Friday, March 9, 2012
HELP! Can't connect to MSDE using Enterprise manger
I installed an instance (only one) of MSDE200 sp3a on one of the desktop machine (XP pro sp1), I would like to manage it by using the enterprise manager installed on another machine on the same network. I was getting the "SQL server does not exist or acce
ss denied" error. I am sure I have enter the proper login info and the MSDE is running.
Is there any configuration need to be done on the MSDE? any expert here can help me on this?
Thanks
Henry
hi Henry,
"Henry" <henryli1222@.msn.com> ha scritto nel messaggio
news:6AB45DD1-DA80-440E-B338-EA8F5467358F@.microsoft.com...
> I installed an instance (only one) of MSDE200 sp3a on one of the desktop
machine (XP pro sp1), I would like to manage it by using the enterprise
manager installed on another machine on the same network. I was getting the
"SQL server does not exist or access denied" error. I am sure I have enter
the proper login info and the MSDE is running.
> Is there any configuration need to be done on the MSDE? any expert here
can help me on this?
>
probably you installed the remote MSDE instance with the default parameter
which disable network protocols for it, not allowing remote connections to
that server...
please run svrnetcn.exe (Server Net Utility) on that server to verify the
desired network protocols are enabled...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks, it works. It's possible to enable the network protocals for the MSDE 2000 installation?
|||Hi Henry,
You can do this by executing svrnetcn.exe.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Henry" <anonymous@.discussions.microsoft.com> wrote in message
news:773EC08B-D846-4AB5-AA82-35034BD9375F@.microsoft.com...
> Thanks, it works. It's possible to enable the network protocals for the
MSDE 2000 installation?
ss denied" error. I am sure I have enter the proper login info and the MSDE is running.
Is there any configuration need to be done on the MSDE? any expert here can help me on this?
Thanks
Henry
hi Henry,
"Henry" <henryli1222@.msn.com> ha scritto nel messaggio
news:6AB45DD1-DA80-440E-B338-EA8F5467358F@.microsoft.com...
> I installed an instance (only one) of MSDE200 sp3a on one of the desktop
machine (XP pro sp1), I would like to manage it by using the enterprise
manager installed on another machine on the same network. I was getting the
"SQL server does not exist or access denied" error. I am sure I have enter
the proper login info and the MSDE is running.
> Is there any configuration need to be done on the MSDE? any expert here
can help me on this?
>
probably you installed the remote MSDE instance with the default parameter
which disable network protocols for it, not allowing remote connections to
that server...
please run svrnetcn.exe (Server Net Utility) on that server to verify the
desired network protocols are enabled...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks, it works. It's possible to enable the network protocals for the MSDE 2000 installation?
|||Hi Henry,
You can do this by executing svrnetcn.exe.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Henry" <anonymous@.discussions.microsoft.com> wrote in message
news:773EC08B-D846-4AB5-AA82-35034BD9375F@.microsoft.com...
> Thanks, it works. It's possible to enable the network protocals for the
MSDE 2000 installation?
Monday, February 27, 2012
Help!
Hello,
I am trying to copy user logins from one database to another on the same
instance of SQL.
I used DTS to export the data to the new database, when I should have used
the backup option.
I'm in a bet of trouble. Now the users can not access the copied database.
I followed the suggestion below:
But I get the error when I run the script. Server: Msg 195, Level 15, State
10, Procedure sp_help_revlogin, Line 52
'LOGINPROPERTY' is not a recognized function name.
How to transfer logins and passwords between instances of SQL Server
View products that this article applies to.
Article ID : 246133
Last Review : April 12, 2006
Revision : 5.0
Any help would appreciated. My neck is on the line :)
TerrySearch the archives for the name of the procedures. The KB by mistake includes code that only run on
2005, but there has been several postings with the original proc, that runs on 2000.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Terry" <tgwillett@.cox.net> wrote in message news:pgc2g.56484$gE.47798@.dukeread06...
> Hello,
> I am trying to copy user logins from one database to another on the same
> instance of SQL.
> I used DTS to export the data to the new database, when I should have used
> the backup option.
> I'm in a bet of trouble. Now the users can not access the copied database.
> I followed the suggestion below:
> But I get the error when I run the script. Server: Msg 195, Level 15, State
> 10, Procedure sp_help_revlogin, Line 52
> 'LOGINPROPERTY' is not a recognized function name.
> How to transfer logins and passwords between instances of SQL Server
> View products that this article applies to.
> Article ID : 246133
> Last Review : April 12, 2006
> Revision : 5.0
> Any help would appreciated. My neck is on the line :)
> Terry
>|||Thank You
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:O7%23iSQeZGHA.1228@.TK2MSFTNGP02.phx.gbl...
> Search the archives for the name of the procedures. The KB by mistake
> includes code that only run on 2005, but there has been several postings
> with the original proc, that runs on 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Terry" <tgwillett@.cox.net> wrote in message
> news:pgc2g.56484$gE.47798@.dukeread06...
>> Hello,
>> I am trying to copy user logins from one database to another on the same
>> instance of SQL.
>> I used DTS to export the data to the new database, when I should have
>> used
>> the backup option.
>> I'm in a bet of trouble. Now the users can not access the copied
>> database.
>> I followed the suggestion below:
>> But I get the error when I run the script. Server: Msg 195, Level 15,
>> State
>> 10, Procedure sp_help_revlogin, Line 52
>> 'LOGINPROPERTY' is not a recognized function name.
>> How to transfer logins and passwords between instances of SQL Server
>> View products that this article applies to.
>> Article ID : 246133
>> Last Review : April 12, 2006
>> Revision : 5.0
>> Any help would appreciated. My neck is on the line :)
>> Terry
>>
>
I am trying to copy user logins from one database to another on the same
instance of SQL.
I used DTS to export the data to the new database, when I should have used
the backup option.
I'm in a bet of trouble. Now the users can not access the copied database.
I followed the suggestion below:
But I get the error when I run the script. Server: Msg 195, Level 15, State
10, Procedure sp_help_revlogin, Line 52
'LOGINPROPERTY' is not a recognized function name.
How to transfer logins and passwords between instances of SQL Server
View products that this article applies to.
Article ID : 246133
Last Review : April 12, 2006
Revision : 5.0
Any help would appreciated. My neck is on the line :)
TerrySearch the archives for the name of the procedures. The KB by mistake includes code that only run on
2005, but there has been several postings with the original proc, that runs on 2000.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Terry" <tgwillett@.cox.net> wrote in message news:pgc2g.56484$gE.47798@.dukeread06...
> Hello,
> I am trying to copy user logins from one database to another on the same
> instance of SQL.
> I used DTS to export the data to the new database, when I should have used
> the backup option.
> I'm in a bet of trouble. Now the users can not access the copied database.
> I followed the suggestion below:
> But I get the error when I run the script. Server: Msg 195, Level 15, State
> 10, Procedure sp_help_revlogin, Line 52
> 'LOGINPROPERTY' is not a recognized function name.
> How to transfer logins and passwords between instances of SQL Server
> View products that this article applies to.
> Article ID : 246133
> Last Review : April 12, 2006
> Revision : 5.0
> Any help would appreciated. My neck is on the line :)
> Terry
>|||Thank You
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:O7%23iSQeZGHA.1228@.TK2MSFTNGP02.phx.gbl...
> Search the archives for the name of the procedures. The KB by mistake
> includes code that only run on 2005, but there has been several postings
> with the original proc, that runs on 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Terry" <tgwillett@.cox.net> wrote in message
> news:pgc2g.56484$gE.47798@.dukeread06...
>> Hello,
>> I am trying to copy user logins from one database to another on the same
>> instance of SQL.
>> I used DTS to export the data to the new database, when I should have
>> used
>> the backup option.
>> I'm in a bet of trouble. Now the users can not access the copied
>> database.
>> I followed the suggestion below:
>> But I get the error when I run the script. Server: Msg 195, Level 15,
>> State
>> 10, Procedure sp_help_revlogin, Line 52
>> 'LOGINPROPERTY' is not a recognized function name.
>> How to transfer logins and passwords between instances of SQL Server
>> View products that this article applies to.
>> Article ID : 246133
>> Last Review : April 12, 2006
>> Revision : 5.0
>> Any help would appreciated. My neck is on the line :)
>> Terry
>>
>
Sunday, February 19, 2012
help with understanding transactional replication
Hi everybody,
I was told that for transactional replication (see posts below) I need to
have snapshot scheduled to run for instance each night. But i dont
understand this.
This is my way of thinking how transactional replication should be
initiated:
- logreader, snapshot and distributer are stopped
- logreader is started so that it captures transactions that snapshot might
miss out on
- run snapshot immediately after logreader is started.
- snapshot starts doing its thing (copying the schema and the data in the
tables of the ddatabase). If for example snapshot has already processed
TableA and a change in data is made to TableA, logreader will pick this
change up and record it.
- once snapshot has completed its task, the distributer is started. The
distributer moves the snapshot to its destination and then reindexes the
tables. Finally it processes those transactions captured by the logreader.
Is this right?
I cant understand why the snapshot agent should be scheduled for
transactional replication, if the logreader is processing all future
transactions. My thought was that:
initial_snapshot
+
ongoing_transactions (as processed by the logreader)
=
current state of database
So why is there is a need to schedule snapshot for transactional
replication?
Any help in clearing up any of my misconceptions would be fantastic!
cheers, john
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23$2wX4c7FHA.3648@.tk2msftngp13.phx.gbl...
> The snapshot agent should be scheduled, perhaps each hour, or at a time
> when there are few users on your system. Note that a snapshot will only be
> generated if a subscriber needs one. Otherwise no snapshot will be
> generated. So, the only time you need to start this agent is when a
> subscriber needs one.
> The log reader agent should be running continuously.
> I normally run the distributation agent continuously. It doesn't matter in
> which order you start it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "john r" <johnr@.trailer.com> wrote in message
> news:ucO85ub7FHA.956@.TK2MSFTNGP10.phx.gbl...
>
John,
the snapshot agent runs for initialization and reinitialization only. If you
have loads of anonymous subscribers where you have no idea when they'll come
online, then perhaps there is a case for frequent snapshots (is this what
was being referred to by whoever it was who told you that the snapshot agent
needs to run every night?), but most likely this isn't the case for you. In
my setup, we have only ever run the snapshot agent once on some
publications. Certainly the snapshot agents are all disabled and only run
manually when necessary.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I was told that for transactional replication (see posts below) I need to
have snapshot scheduled to run for instance each night. But i dont
understand this.
This is my way of thinking how transactional replication should be
initiated:
- logreader, snapshot and distributer are stopped
- logreader is started so that it captures transactions that snapshot might
miss out on
- run snapshot immediately after logreader is started.
- snapshot starts doing its thing (copying the schema and the data in the
tables of the ddatabase). If for example snapshot has already processed
TableA and a change in data is made to TableA, logreader will pick this
change up and record it.
- once snapshot has completed its task, the distributer is started. The
distributer moves the snapshot to its destination and then reindexes the
tables. Finally it processes those transactions captured by the logreader.
Is this right?
I cant understand why the snapshot agent should be scheduled for
transactional replication, if the logreader is processing all future
transactions. My thought was that:
initial_snapshot
+
ongoing_transactions (as processed by the logreader)
=
current state of database
So why is there is a need to schedule snapshot for transactional
replication?
Any help in clearing up any of my misconceptions would be fantastic!
cheers, john
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23$2wX4c7FHA.3648@.tk2msftngp13.phx.gbl...
> The snapshot agent should be scheduled, perhaps each hour, or at a time
> when there are few users on your system. Note that a snapshot will only be
> generated if a subscriber needs one. Otherwise no snapshot will be
> generated. So, the only time you need to start this agent is when a
> subscriber needs one.
> The log reader agent should be running continuously.
> I normally run the distributation agent continuously. It doesn't matter in
> which order you start it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "john r" <johnr@.trailer.com> wrote in message
> news:ucO85ub7FHA.956@.TK2MSFTNGP10.phx.gbl...
>
John,
the snapshot agent runs for initialization and reinitialization only. If you
have loads of anonymous subscribers where you have no idea when they'll come
online, then perhaps there is a case for frequent snapshots (is this what
was being referred to by whoever it was who told you that the snapshot agent
needs to run every night?), but most likely this isn't the case for you. In
my setup, we have only ever run the snapshot agent once on some
publications. Certainly the snapshot agents are all disabled and only run
manually when necessary.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Subscribe to:
Posts (Atom)