March 9, 2005 at 4:10 am
Hi All
I have already checked the answers in discussions to find a solution for my problem but I could not..
I am using Trancation Replication for my customer. There is one server (Publish) in a city and 5 more Subscription in different citys. We are only replicating one Table, that is called "Adresse"
So far I got 2 kind of problems.
1.One of them subscriptions being "inactive".
2.the other one is that some of the subscriptions have connection problem with Publisher DB.
For the Problem 1, if there is no transaction occurs within "14 days(default value)" between publishing server and subscription servers, becoming Subscriptions inactive. I changed this value as "never expired" but I am not sure it is a good idea. As I read, Distribution DB is growing. But only one Table is it a problem?
The 2. Problem that I yesterday had is connection Problem. 3 of subscriptions was working fine but 2 of them were not available.
The error messages are at replication monitor like this for these 2 server.
"The agent is suspect.No Response within last 10 minutes"
I know that is only a information messages.
But in subcription side, the error was;
"The Process could not connect to Distributor 'Server1' "
The customers Network is really bad and they are living disconnections very often.
Then, in replication monitor screen, I made right click to subcriptions which are not running and clicked "Start synchronizing".
After that, the transactions are made and the situations of these 2 subscriptions became normal and active.
Regarding this problem, if there is a network problem in Subcriptions, how can replication (synchronizing) start automatically, after the network is up again.
Because, its not good, everytime connecting to Customer server and start synchronizing. Could it be made with and stored procedures or with a Job, script??
Thanks alot in advance...
Tolga
March 9, 2005 at 9:38 am
Hi the replication agent goes suspect because of the connection to publisher database server. once the netwrok connection is up again try re activate the subscription and run the job again if that doens; goes successfully then you have to recreate the replication.
March 10, 2005 at 12:41 am
Hi
first of all thanks for your answer..Actually, if I did these, replication is working again..
But I am doing this job on customer server and its not good to do this operation everytime by connecting customer server remotely when same problem occurs.
Can I activate the subs automatically for example with defining a "Job" on sql server instead of using manually Sql Server Enterprise manager.???
Thanks
Tolga
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply