Well I have run out of ideas, so I will hopefully get some from this forum.
We have a single master replication server that supports pull replications form 4 clients.
Here is the wildness. Three out of the four are working fine. No problems.
So I dropped the pull replications on the fourth box, figuring I would just make a clean sweep of things and start over. This is what ended up happening. I found out that the subscriptions on the master were not there, but they we still on the fourth server. No idea how hey were deleted from the distributor but still on the target server. This is why I deleted and started over.
After doing that, I re-created the pull subscription. It does register, so far so good. Next, I run the spapshot agent. It runs with out a problem. I am thinkg fine so far. Now when I go to the distribution agent, and start it. It never starts. The staus never changes and replication never occurs. I have tried start the distribution agent several time. The server does not even show the failure to start in any of the event logs. So I mark the subscription to re-initialize and start the process again. Same result.
I am about to go crazy over this one. I am not an expert in replication, but I have been an SQL DBA for 9 years, and this is the first time I have seen this kind of abberant behavior.
Any suggestions? Any help would be greatly appreciated.