RE: Web Synchronization: Could not connect to distributor

Tech-Archive recommends: Fix windows errors by optimizing your registry

Note that the error says "could not connect to the Distributor". So ensure
that the the login that the merge agent is using has the right permissions on
the Distributor and has the permissions to its default database (and also the
distribution database).

Thanks
Emaniel


"John Van Vliet" wrote:

After re-creating everything for subscriber #10 I am now getting a different
error. It seems like the snapshot is applied properly but the synchronization
fails during the merge phase after applying the snapshot. It tries to connect
10 times and then fails with the following errors (on the subscriber):

"The process could not connect to the Distributor '<ServerName>'"
"Cannot open user default database. Login failed."
"Login failed for user '<UserName>'"

The default database is correct and I have checked the permissions many
times. Any ideas?

"John Van Vliet" wrote:

Thank you for the response Emaniel.

I have tried many times to create a new agent profile with verbose logging
using Management Studio. The dialog box that is used to set profile params
will not accept a string for -Output. Is there another way to configure the
agent profiles?

I have tried using the "Verbose history agent profile" but I can't find
where the history is logged. What table should I be looking in?

Subscriber #9 is working now after deleting and re-creating the database
user, SQL login, Windows user, publication access list entry, and data
partition. I am going to try the same with subscriber #10. If that doesn't
work I will try changing the other params as you suggested.

Thanks again.

"Emaniel Chekelea" wrote:

John,
The -Output parameter should work I am not sure why it is giving you the
error. That parameter takes a filename as input value. It is the
-Outputverboselevel that takes 0/1/2/3 as input.

For debugging you could try using the "Verbose history agent profile"
instead of using the -Output parameter. This profile should log the agent
history in the database itself and you can view it by looking at the agent's
log.

Also you might want to consider creating a custom profile for your merge
agents of subscribers 9 & 10. Try tuning the following parameters :

-BcpBatchsize (decrease this)
-DownloadGenerationsperBatch (decrease this)
-QueryTimeout (increase this)

HTH
Emaniel

"John Van Vliet" wrote:

I have a SQL Server Standard publisher which is publishing to 10 SQL Server
Express subscribers. Each subscriber has its own partition based on
SUSER_SNAME. I was able to setup the first eight subscribers with no problem,
but numbers 9 and 10 are not working.

Initializing the subscription seems to go well -- data is bulk copied,
scripts are applied, and tables are readied for replication. The
synchronization then fails with the following errors (errors logged on the
subscriber):

"The merge process was unable to deliver the snapshot to the Subscriber. If
using Web synchronization, the merge process may have been unable to create
or write to the message file. When troubleshooting, restart the
synchronization with verbose history logging and specify an output file to
which to write."

"The process could not bulk copy into table '"dbo"."MSmerge_contents"'."

"Field size too large"

"End of file reached, terminator missing or field data incomplete"

I have attempted to enable verbose logging on the publisher but I can't get
it to work. The Management Studio GUI does not allow a path for the -output
option for the distribution agent (it fails with an error that -output must
be an integer).

Any help would be greatly appreciated. I've been fighting with this for two
days and nights.

.

Relevant Pages

  • Re: push or pull, local or remote
    ... > replication use a remote distributor. ... > agent runs on the subscriber. ... not pull. ...
    (microsoft.public.sqlserver.replication)
  • Server SQLTEST1 is not prepared to run the offloaded agent
    ... Right-clicking on the distribution agent offers an option, ... Box comes up that says "Subscriber must be prepared ..." ... Server 'SQLTEST1" is not prepared to run the offloaded agent. ... The agent failed to connect to the Distributor due to the ...
    (microsoft.public.sqlserver.replication)
  • Re: Transactional Replication SQL 2005 Cannot connect to the subscriber
    ... I turned on the logging level for the agent. ... Connecting to Distributor 'STLDBA-STG1.Dist_MSNWSSQLSTG1' ... Subscriber security mode: 0, login name: sa. ... Microsoft SQL Server Distribution Agent 8.00.2039 ...
    (microsoft.public.sqlserver.replication)
  • RE: Web Synchronization: Could not connect to distributor
    ... If the replication agents are being executed as SQL Agent jobs then your ... I have tried many times to create a new agent profile with verbose logging ... I have tried using the "Verbose history agent profile" but I can't find ... I am going to try the same with subscriber #10. ...
    (microsoft.public.sqlserver.replication)
  • Re: Server SQLTEST1 is not prepared to run the offloaded agent
    ... add the account the SQL Server agent runs under on the publisher. ... I think you would be best to use a pull agent running off your subscriber. ... The agent failed to connect to the Distributor due to the ...
    (microsoft.public.sqlserver.replication)