December 29, 2003 at 7:17 am
I click start syncronizing and start agent and nothing happens.
The error for Merge replication states the publication doesn't exist (so I told the snapshot agent to start). Nothing happens.
The transactional replication says general network error. I tried starting syncronization with no response. So I tried starting the snap shot with no response.
I have marked one of the merge replication subscribers for reinitiallization, but it says that won't occur until the merge or distribution agent runs again and I can't get the snap shot agent to start.
How can I get these to start?
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
December 29, 2003 at 7:20 am
Sorry, forgot the details.
All SQL Servers are SQL Server 2000 with SP3. The SQL Server Agents seem to be running. The transactional replication is one way.
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
December 29, 2003 at 7:30 am
I have found the job that is for the snap shot for the merge replication that is not working. Can I just tell this job to start?
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
December 29, 2003 at 8:35 am
I created a merge replication test in our development environment and started the snap shot job. That worked fine. But when I start it in production it doesn't start. I get no errors. When I view the job history, the job never started.
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
December 30, 2003 at 8:31 am
Do you have any history details in the snapshot job?
Are you sure the publication still exists?
To really know what is happening it is better to start the snapshot agent by the command line.
Locate the snapshot.exe file in you disk and also check the parameters in BOL.
You can copy the parameters from the Snapshot job, in the step nro 2 (Run Agent).
Also specify -OutputVerboseLevel 2, so it will log more to the screen.
If found any errors please post them here.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply