Replication - setting up Publication. URGENT

[dky1e]

Hi,

I'm trying to setup publication on one of the databases through SQL Server Enterprise manager.

After I press finish on the wizzard, the server goes through the steps and it fails on
"Creating Publication".

The error I'm getting is:
Error 0: This server has been disconnected. You must reconnect to perform this operation.

I've never seen it before, and I need to set this up and get it working ASAP.

I appreciate your help.

 

[dky1e]

I'm running SQL Server2000, sp3.

Here's an error I found in the SQL Server Log:
Stored function 'xp_MSADEnabled' in the library 'xpstar.dll' generated an access violation. SQL Server is terminating process 55..

I happens as the 'New Publication' wizzard errors out.

 

[dky1e]

Is it possible to create replication using t-sql script?

I want to try it, see maybe I can get more descriptive error message.

 

[mrdenny]

I know that it can be done via stored procedures. In Books online pull up System Stored Procedures (subsection listed).

About 1/3 of the way down is the list of the procedures needed for replication.

Perhaps your copy of xpstar.dll got corrupt and needs to be replaced?

Denny

 

[dky1e]

I have gotten a very interesting and insightful response from one of the members on the google groups having the same problem. His reply leads me to believe that this could be an Active Directory issue.

I not sure which direction to continue. What should I look for? Is there a white paper somewhere listing AD requirements for replication? I can't seem to find anything useful on google...

Regarding the "Error 0:" problem .. I have not found a solution yet. I have SP3 installed on all replication participants. My setup is a simple publisher/distributor on the same instance and one subscriber on a separate machine. The problem occurs only on the publishing instance and appears to be a result of Microsoft's Active Directory (MSAD) service being unable to validate the computer's account against the domain controller (PDC). I've noticed that indeed the computer's name does not show up in the list of computers on the PDC, which is supposed to be added automatically (likely at boot up time of the host of the publishing instance). On the publishing machine, the event viewer contains lots of messages about W32time service getting invalid time stamps, and many errors regarding MxSMB (or something like that). Also, I believe the job log from the publishing job had some clues about an MSADHelper (or something similar) returning some error.

Symptoms and indicators make me believe the problem lies in Active Directory services and/or MS Time services because one or both cannot successfully complete a security check. Active Directory services DO play a very active role in replication.

 

[mrdenny]

Unfortunitally I won't be able to address any Active Directory issues. We are still running in an NT4 domain.

Be sure that all the clocks on all your machines are in sync. I do know that if they get out of sync the domain will freak out, and give all sorts of errors.

Denny