Broken Linked Server

Been running SQL 7.0 sp4 for 1 1/2 years on two NT4.0 sp6a
servers on the same subnet with no problems. ServerA is
linked to ServerB, and ServerB is linked to ServerA.
I haven't loaded any new software. This past Monday, all
the jobs on ServerA that use data from ServerB failed.
All the jobs on ServerB that use data on ServerA failed.
I have not been able to figure out what caused the
problem, nor have I been able to correct the problem. I
deleted the link on each server, and tried recreating the
link but failed with the errorlog showing "Login failed
for user "ServerA(B)\Administrator". Same error on both
machines. Yet, both servers are able to successfully
register with each other through EM. The audit log shows
the message "Login succeeded for user 'ServerA(B)
\Administrator'.connection:Trusted." So, I would assume,
that they can communicate with each other.
I even deleted all my network services/protocols then
reinstalled them with no help.
Any ideas?
Did the passwords change on the Administrator account?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Nope. Nobody else admins the account. I thought the same thing, and
just in
case recent them. It didn't help. What I don't get is the server,
through EM,
can successfully register both servers (which uses the account I logged
in with),
but can't link the servers (which I map to the very same account).
Kevin McDonnell [MSFT] wrote:

>Did the passwords change on the Administrator account?
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
>

Breaking Replication??

Hi All
I have servers A, B and C with databases. Server A is a Publisher and Server
B is the Distributor/Subscriber. Server C is a Subscriber. Server A
replicates 7 publications to both server B and C. Initially when the
publications were very small, there were snapshot replications from A to both
B and C. Thereafter there have been transactional replications. The total
size of the databases has grown to about 30G.
My problem is I want to replace server C with a new server D. I have only 12
hrs to do this. If I do a snapshot replication to server D, it might take me
about 60hrs which I can’t do as this has to be done on a Sunday and ready for
Monday morning. I have a 150K pipe. I would like to avoid breaking the
replication on server B if possible. How can I do this replication within
12hours without breaking replication on server B?
Currently:
A>>>B
A>>>C
Future:
A>>>B
A>>>D
Thank you in advance.
You could create the snapshot, zip it up (WinZip 9.0), ftp, unzip and
restore, then specify an alternative snapshot location when initializing
server D. Alternatively you could zip up a backup of the database, ftp,
unzip restore then synchronize any changes to the data (if it is possible
there could be some). Prevent any further changes then do a nosync
initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Since server D is a new server, why don't you just set this new server as an
additional subscriber while you are still replicating to server C? Once D
has received the snapshot and is replicating normally you can pull server C.
I'm not sure how far away from your datacenter server D will be, but you
could also do the snapshot stuff on the local network (where server A&B are)
and then ship it to it's final location. One sticking point may be if you
are planning on using the same machine name for server D that you have for
server C, but it may not be an issue if you are using anonymous subscribers.
"MittyKom" wrote:

> Hi All
> I have servers A, B and C with databases. Server A is a Publisher and Server
> B is the Distributor/Subscriber. Server C is a Subscriber. Server A
> replicates 7 publications to both server B and C. Initially when the
> publications were very small, there were snapshot replications from A to both
> B and C. Thereafter there have been transactional replications. The total
> size of the databases has grown to about 30G.
> My problem is I want to replace server C with a new server D. I have only 12
> hrs to do this. If I do a snapshot replication to server D, it might take me
> about 60hrs which I can’t do as this has to be done on a Sunday and ready for
> Monday morning. I have a 150K pipe. I would like to avoid breaking the
> replication on server B if possible. How can I do this replication within
> 12hours without breaking replication on server B?
> Currently:
> A>>>B
> A>>>C
> Future:
> A>>>B
> A>>>D
> Thank you in advance.
>