Replication target and white space

[michel.weber]

We have been trying to find out why a particular replication did not work.

After scratching our heads for a couple of days, it turns out that replication does not like white space at the end of replication targets.

ie.: "http://search/texis/dowalk/" does work, but
"http://search/texis/dowalk/ " does not, and gives a list of obscure error messages :

000 2010-03-16 17:57:31 [dowalk] Connection to host "www.w3.org" failed for http URL "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd": [^] No error in the function http_open
000 2010-03-16 17:57:31 [dowalk] XML parsing error reported at byte offset 110
000 2010-03-16 17:58:32 [dowalk] XML parsing error reported at byte offset 345
000 2010-03-16 17:58:32 [dowalk] XML parsing error reported at byte offset 353
100 2010-03-16 17:58:32 [dowalk] Server error: http://search.coe.int/texis/dowalk/%20/replrecv.txt [^] returned code 500 (Vortex Error)

It took some time before i spotted the '%20' in one of the messages.

[michel.weber]

My problem now is that i have a replication queue with over 150 000 items which i can not re-index in the next couple of weeks.

going in with tsql and strip the white space from the end of the 'DestMachine' field does not seem to work.

What can i do to get the replication restarted, without reindexing?

[michel.weber]

Ok

I forgot to change the replication target in the profile itself.

Will this work?

[John]

It should. The table and profile should match, as the sender will loop over the destinations in the profile looking in the table for what to send.