| Author |
Topic |
|
BigSam
Starting Member
30 Posts |
 Posted - 2006-05-05 : 09:51:51
|
| I'm trying to setup transaction replication between 2 servers. This is a one-way replication: Server A to Server B, not Server B to Server A.My snapshot publication keeps failing & I cannot determine why. I added commands to the agent so that it would create an output file, possibly with more or better information, but now I'm lost even more. Below is a portion of the output file that should explain the trouble I'm having:SourceTypeId = 5SourceName = PublicationErrorCode = 11ErrorText = General network error. Check your network documentation.The process could not bulk copy out of table '[dbo].[syncobj_0x3531313845304531]'.Repl Agent Status: 5Disconnecting from Publisher 'Publication'The agent failed with a 'Retry' status. Try to run the agent at a later time.I've tried running the snapshot numerous times with the same results.Any help is appreciated.Thanks,BigSam |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-05 : 10:00:27
|
| how about the job history for the snapshot agent?distribution agent?if it's still network documentation, you might want to ask your netadmins if packets are being dropped...--------------------keeping it simple... |
 |
|
|
BigSam
Starting Member
30 Posts |
Posted - 2006-05-05 : 10:52:31
|
| Job Agent History only shows:The process could not bulk copy out of table '[dbo].[syncobj_....]'. Note: The step was retried the requested number of times (10) without succeeding. The step failed. date/timeThe Distribution Agent History shows:The initial snapshot for publication 'Publication' is not yet available. date/timeI don't understand why packets would be dropped. I can share files & query databases between the servers without incident. The only thing in the Event Logs (Application) is the Job Agent History. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-05 : 11:00:18
|
| how many records are you dealing with?--------------------keeping it simple... |
|
|
|
BigSam
Starting Member
30 Posts |
Posted - 2006-05-05 : 11:38:44
|
| Based on my observation of the agent while it is running, it completes the bulk copy without an error when the table has 0 records, but if it has as few as 10 or greater than 100,000 it returns this message. In fact it returns this message for every table it attempts to copy that has greater than 0 records. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-07 : 02:10:10
|
| are there triggers on the destination tables,something that will prevent the bulkcopy to completeblocked spidstry to recreate the snapshot and apply it again, be sure to specify to drop the tables if they are existing--------------------keeping it simple... |
|
|
|
BigSam
Starting Member
30 Posts |
Posted - 2006-05-09 : 09:21:33
|
| There are no triggers in the database.I don't believe there are any blocked spids. I was able to query the table in question from both servers - 0 records were returned.I've recreated the snapshot multiple times & each time I've Re-initilized the destination database & included a drop if exists.Big Sam |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-09 : 22:30:01
|
| if you check the sql server logs, is there any message on the replication job that can give you a clue?or a full transaction log file or disk space not enough?if it's still about network, ask your netadmin if there are packets being dropped and ask them to monitor the traffic between the two servers in question while you're doing the snapshot--------------------keeping it simple... |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-09 : 22:32:41
|
you checked this in the subscriber's side? oh, be sure to have more than zero records on the publisher so you can troubleshoot this betterquote:
Originally posted by BigSam
There are no triggers in the database.I don't believe there are any blocked spids. I was able to query the table in question from both servers - 0 records were returned.I've recreated the snapshot multiple times & each time I've Re-initilized the destination database & included a drop if exists.Big Sam
--------------------keeping it simple... |
|
|
|
|
Transaction Replication