i've had a rash of these lately. seems like upgrading to SP2 or reinstalling SP4 on sql 2000 helps

for the curious, seems to be a bug. we had two published db's of the same name and two published tables of the same name as well going through one distributor to the same subscribers with the destination tables being named different.

changed it for one of the publishers to be it's own distributor