Post reply

distribution DB not available due to server crash

  • January 22, 2009 at 2:58 am

    #204407

    Hi,

    Two publishing SQL 2000 server, one subscriber server with a distribution DB. The Subcriber has unfortunately crashed.

    SQL 2005 server was reinstalled, but they forgot that the distribution DB resided on that server. I have two publsihing SQL2000 server, now these server are unable to find the distributor DB, as a result I cannot setup replication again on both SQL 2000 servers.

    I already used the sp_removedbreplication to remove the publication from both SQL 2000 server but I'm stil unable to add a new publication because both servers are looking for the non existing Distribution DB on the re-installed server. I receive the following error:

    _______

    The distributor is not available.

    Error 18482: Could not connect to server 'reinstalled server' because 'Publishing server' is not defined as remote server. VErify that you have specified the correct server name.

    ________

    Any help?

    thanks,

    Remco

  • January 22, 2009 at 3:50 am

    #930972

    I think the following sequence should help you:

    1. Execute sp_adddistributor on master db of distributor.

    2. Execute sp_adddistributor on on master db of all publishers.

    3. Execute sp_adddistributiondb on the distributor.

    For parameters refer to BOL. Let us know if it works.

    -Vikas Bindra

  • January 22, 2009 at 6:56 am

    #931128

    hi vikas,

    I have tried your soultion, but I am still not succesful. I'll explain:

    >1. Execute sp_adddistributor on master db of distributor.

    This worked out perfectly on the Distributor (SQL 2005)

    >2. Execute sp_adddistributor on on master db of all publishers.

    This didn't work and generated the following, something with remote login not defined. The following erorr is given:

    Could not connect to server 'YYY' because 'distributor_admin' is not defined as a remote login at the server. Verify that you have specified the correct login name. .

    >3. Execute sp_adddistributiondb on the distributor.

    This worked perfectly.

    I'am not sure how to register these servers remotely on all SQL boxes. Maybe this be the issue?

    Thanks again.

    Remco

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply