Replication Error of MS SQL server2k

Distribution Agents come with a error and stop between two SQL2000 server.
The error messages is:

The query processor could not produce a query plan from the optimizer
because a query cannot update a text, ntext, or image column and a
clustering key at the same time. (Source: Some Server (Data source); Error number:
8629)

How can I fix it?Is it transactional replication?
If yes - and you are using Identity fields (with not for replication) then check prsp_MSupd_**** stored procedures on subscriber and remove updating Identity field.

replication distribution server agents keep time out

Hi,
We have a distribution server that have all of our
transactional replications on it. All the distribution
agents and log reader agents keep time out and we have to
keep restart the agents.
What's the roob cause of this? Too many replications on
one distribution box? Or too many agents running at the
same time schedule?
Many thanks.
JJDon't the distribution agents keep trying for a certain number of times
before they error out? While they keep trying, you don't need to manually
restart them.
Distribution agents often times out in our environment. Causes I have found
are:
1. Blocking on the subscriber;
2. No more space on the subscriber database;
3. Server connection problem;
Richard
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:01a501c39284$479d5ee0$a401280a@.phx.gbl...
> Hi,
> We have a distribution server that have all of our
> transactional replications on it. All the distribution
> agents and log reader agents keep time out and we have to
> keep restart the agents.
> What's the roob cause of this? Too many replications on
> one distribution box? Or too many agents running at the
> same time schedule?
> Many thanks.
> JJ

Replication and distribution: Agents

Hi all replication experts...

I have created transactional replication on my servers (production server and backup server) and created pull subscription at the backup server. On my production server that also is a distributor and publisher there exist two agents, Snapshot agent and Log reader in the Publishers folder under replication Monitor.

There are also another agent with the backup server name and database name: BackServ:DBName having the type Pull and 'No replicated transactions are available' as Last Action. My question is: What is this? Must it be there?

Grateful for answers

Best,
/M

Its hard to say exactly what this is, but it appears to be your distribution agent. You appear to have a pull agent configured on your subscriber.

It is essential for your transactional replication topology. Do not remove it.

Hilary

|||OK, thanks :)

Replication - distribution agents?

When distribution is scheduled to run at specific times for specific user, but that user is not connected to the server. Distribution tries to find that subscription, the error comes back:

The step was retried the requested number of times(10) without succeeding.

Where/how can I change the requested number to try two or three times.

My problem is that it takes 10-15 minutes for those re-trys and which sometimes causes overlap with the next subscription coming in.Check sp_update_jobstep in BOL, look for @.retry_attempts and @.retry_interval
The best way would be to use a PULL subscription at the subscriber instead of PUSH at the publisher.

Originally posted by cruzin
When distribution is scheduled to run at specific times for specific user, but that user is not connected to the server. Distribution tries to find that subscription, the error comes back:

The step was retried the requested number of times(10) without succeeding.

Where/how can I change the requested number to try two or three times.

My problem is that it takes 10-15 minutes for those re-trys and which sometimes causes overlap with the next subscription coming in.|||You can also identify the job in Enterprise Manager (Management->SQL Server Agent-> Jobs) then find the step and change the retry attempts there.

Originally posted by dbadelphes
Check sp_update_jobstep in BOL, look for @.retry_attempts and @.retry_interval
The best way would be to use a PULL subscription at the subscriber instead of PUSH at the publisher.