Replication porblem

Hi everybody,

i got this error message while i'm trying to execute my replication job.

"error 4813"

Expected the text length in data stream for bulk copy of
text, ntext, or image data."

Does anybody have an idea about it?
thanks

Let me know if the workarounds in the below link do not work for you.

http://www.starquest.com/Supportdocs/techSQDR/SQV00DR0013_BCPError.html

|||It seems to work! Thanks
I wonder if there is a Microsoft's KB article about it, 'cause i didn't find any!!

Replication ntext only by UPDATE

Dear group,
in the SQL-Server documentation it says:
"Merge replication supports the replication of text, ntext, and image
columns only if they have been updated explicitly by an UPDATE statement
because it causes a trigger to fire that updates meta data ensuring that the
transaction gets propagated to other Subscribers."
Is this also valid for INSERT-Statements?
In our case we have a table where only INSERTS of new rows occur (incl.1
ntext column). Can we replicate this by merge replication without problems?
Do you have a URL to 'prove' this? ;-)
thanks a lot,
regards,
ERic
I understand that you have to have a trigger that fires on insert, to update
the text column in the row again.
I haven't tried this myself.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Eric Voigt" <eric@.ericvoigt.de> wrote in message
news:2ubq8aF28taboU1@.uni-berlin.de...
> Dear group,
> in the SQL-Server documentation it says:
> "Merge replication supports the replication of text, ntext, and image
> columns only if they have been updated explicitly by an UPDATE statement
> because it causes a trigger to fire that updates meta data ensuring that
the
> transaction gets propagated to other Subscribers."
> Is this also valid for INSERT-Statements?
> In our case we have a table where only INSERTS of new rows occur (incl.1
> ntext column). Can we replicate this by merge replication without
problems?
> Do you have a URL to 'prove' this? ;-)
> thanks a lot,
> regards,
> ERic
>
>

Replication LogReader

Once i configured the replication throwing the following error on logreader

2007-02-08 16:47:39.641 Status: 0, code: 1007, text: 'Another logreader agent for the subscription(s) is running or the server is working on a previous request by the same agent.'.
2007-02-08 16:47:39.641 Another logreader agent for the subscription(s) is running or the server is working on a previous request by the same agent.
2007-02-08 16:47:39.641 Status: 0, code: 22037, text: 'The last step did not log any message!'.

Please let me know if you have any solutions to fix this issue.

Can you provide more detail about your replication setup?

Gary

|||My guesss is you have two logreader agent jobs running against the same publisher db. Stop one of the jobs, then delete/disable it, you should have only one logreader agent job per published database. If you do not have two jobs, then somehow the logreader agent process when you ran it the first time did not shut down properly. THe safest way to clear this issue is to restart the SQL Server service on the distributor machine.|||

I have multiple publisher and multiple subscriber for same db.when i configure it this way it is thorowing the above error?