sql server replication:
Not sure why this keeps happening. The table is
not that large compared to others that we do.
This is with the 2 set on the logging and still
is pretty vague as far as the "general network
error".. Any ideas on how to make this snapshot
go through. Both our connection and theirs is a
stable wan connection..

tia
-comb

Bulk copying data into table 'dpvHstGndSale'
[11/30/2004 2:44:38 PM]DFW1-FTP3.distribution:
{call sp_MSadd_distribution_history(11, 3, ?, ?,
0, 0, 0.00, 0x00, 1, ?, 0, 0x01, 0x00)}
Bulk copied data into table 'dpvHstGndSale' (0
rows)
[11/30/2004 2:44:38 PM]DFW1-FTP3.distribution:
{call sp_MSadd_distribution_history(11, 3, ?, ?,
0, 0, 0.00, 0x00, 1, ?, 0, 0x01, 0x00)}
select * from "dpvHstItemSalesByInterval" where 1
= 2
[11/30/2004 2:44:38 PM]MORTONS.mos01: select *
from "dpvHstItemSalesByInterval" where 1 = 2

Bulk copying data into table
'dpvHstItemSalesByInterval'
[11/30/2004 2:44:38 PM]DFW1-FTP3.distribution:
{call sp_MSadd_distribution_history(11, 3, ?, ?,
0, 0, 0.00, 0x00, 1, ?, 0, 0x01, 0x00)}
Agent message code 20037. The process could not
bulk copy into table
'"dpvHstItemSalesByInterval"'.
[11/30/2004 2:48:53 PM]DFW1-FTP3.distribution:
{call sp_MSadd_distribution_history(11, 5, ?, ?,
0, 0, 0.00, 0x01, 1, ?, 9, 0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts:
ErrorId = 3311238,
Transaction Seqno = 0055ab0c000001c4000100000001,
Command ID = 9
Message: Replication-Replication Distribution
Subsystem: agent VSQL13\ENTERPRISE01-mos01-
MORTONS-11 scheduled for retry. The process could
not bulk copy into table
'"dpvHstItemSalesByInterval"'.[11/30/2004 2:48:53
PM]DFW1-FTP3.distribution: {call
sp_MSadd_repl_alert(3, 11, 3311238, 14152, ?, 9,
N'VSQL13\ENTERPRISE01', N'mos01', N'MORTONS',
N'mos01', ?)}
ErrorId = 3311238, SourceTypeId = 5
ErrorCode = '11'
ErrorText = 'General network error. Check your
network documentation.'
[11/30/2004 2:48:53 PM]DFW1-FTP3.distribution:
{call sp_MSadd_repl_error(3311238, 0, 5, ?,
N'11', ?)}

Category:SQLSERVER
Source: MORTONS
Number: 11
Message: General network error. Check your
network documentation.
[11/30/2004 2:48:53 PM]MORTONS.mos01: exec
dbo.sp_MSupdatelastsyncinfo N'VSQL13
\ENTERPRISE01',N'mos01', N'', 0, 5, N'The process
could not bulk copy into table
''"dpvHstItemSalesByInterval"''.'
Disconnecting from Subscriber 'MORTONS'
Disconnecting from Distributor 'DFW1-FTP3'
Disconnecting from Distributor History 'DFW1-
FTP3'
The agent failed with a 'Retry' status. Try to
run the agent at a later time.
Microsoft SQL Server Distribution Agent 8.00.194
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: VSQL13
\ENTERPRISE01-mos01-MORTONS-11

Startup Delay: 785 (msecs)
Connecting to Distributor 'DFW1-FTP3'
Connecting to Distributor 'DFW1-FTP3.'
[11/30/2004 2:49:54 PM]DFW1-FTP3.: exec
sp_helpdistpublisher N'VSQL13\ENTERPRISE01'
[11/30/2004 2:49:54 PM]DFW1-FTP3.distribution:

There is not much that can be done on the sql side, except to try to push
out less data. This error is usually caused by mdac or network issues.

1. Create a new profile for the distribution agent. (in enterprise manager,
right click on the distrib agent->agent profiles...). Specify the following
parameters:
-BcpBatchSize 10

** This is the number of rows to send in a bulk copy operation. When
performing a bcp in operation, the batch size is the number of rows to send
to the server as one transaction, and is also the number of rows that must
be sent before the Distribution Agent logs a bcp progress message. When
performing a bcp out operation, a fixed batch size of 1000 is used. A value
of 0 indicates no message logging.

-CommitBatchSize 10

** The number of transactions to be issued to the Subscriber before a
COMMIT statement is issued.

- CommitBatchThreshold 10
** This is the number of replication commands to be issued to the
Subscriber before a COMMIT statement is issued.

now restart your agent, capture a netmon trace simultaneously at the
distributor and subscriber. If the distribution agent still fails, have
your network admins analyze these traces. This error could be due mdac
issues or network issue (such as firewall issues).

Also, as a workaround you can create what is called a NOSYNC subscription,
per KB:
HOW TO: Manually Synchronize Replication Subscriptions by Using Backup -
ID: 320499
http://support.microsoft.com/?id=320499


Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Also, have your sysadmins doublecheck the firewalll configurations. Were
any changes recently made to your firewalll configuration?


Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx