I can't even find my thread of a few days ago and I'm sure SOMEONE can help me with this 
, so here it is again:
(SQL Server 7.0)
Replication is set up and works fine in following config:
Server A is Publisher and Distributor.
Server B has a pull subscription onto a publication on Server A.
The problem occurs whenever we re-boot Server A. When Server A comes up again, the pull susbscription job no longer works. We get error:
Category:ODBC
Source: ODBC SQL Server Driver
Number: S1T00
Message: Timeout expired
and have to do a full snapshot etc. to get it all going again.
All timeout type settings are default. The re-boot takes approx 3 to 4 minutes.
Shouldn't replication handle such a situation automatically unless Server A is unreachable for (default) 72 hours? Should we stop/re-start the subscription job when re-booting publisher?
Thanks,
Rafi
, so here it is again:(SQL Server 7.0)
Replication is set up and works fine in following config:
Server A is Publisher and Distributor.
Server B has a pull subscription onto a publication on Server A.
The problem occurs whenever we re-boot Server A. When Server A comes up again, the pull susbscription job no longer works. We get error:
Category:ODBC
Source: ODBC SQL Server Driver
Number: S1T00
Message: Timeout expired
and have to do a full snapshot etc. to get it all going again.
All timeout type settings are default. The re-boot takes approx 3 to 4 minutes.
Shouldn't replication handle such a situation automatically unless Server A is unreachable for (default) 72 hours? Should we stop/re-start the subscription job when re-booting publisher?
Thanks,
Rafi