we're having a problem with one publication out of 50 or 60. SQL 2000 publisher with sql 2005 distributor and sql 2005/2000 subscribers.

best way to troubleshoot is to make sure...

my favorites are in replication when you have a varchar column with more than 4000 characters it changes it to ntext. if you have a sql2000 subscriber you are out...

save yourself the headache and use dbmail

how many mail servers in the system? you might have to allow relaying.

aren't there documented issues going back years when installing anything on a domain controller? I remember reading that MS doesn't want you to install SQL, Exchange and a whole list...

i think there is a memory leak in the client components, a bug in replication the put in on purpose, a few other bugs in replication that make it more...

how did you originally create the publication? have you tried to reinitialize it?

do an sp_who on your distributor and see if there is any blocking

we have a distributor and noticed that the clean up job was running for a very long time...

try copying the install files locally, i had an issue a few times when installing from a share

we have an open case with MS and they said very soon, most likely this month

check your surface area configuration for features. almost everything is turned off buy default on a new install

are you installing from CD? maybe it's scratched? Try copying all the files to the HD or somewhere on the network and installing from there

the agent is working but it was taking over 6 hours to run. this distributor is replicating a few tables with close to 500 million rows between them.

opteron is 64bit

i've read of some issues when you go from 64bit to 32bit

turn on the logging to see where the hold up is. are you comparing running it at the same times?