Post reply

Changed database context to 'master' in Replication

  • May 30, 2011 at 7:05 am

    #240550

    While configuring replication i am getting the below error , could anyone help me!

    ------------------------------

    SQL Server could not configure 'XXXXX-PC' as a Distributor.

    ------------------------------

    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    Invalid destination path C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data.

    Changed database context to 'master'. (Microsoft SQL Server, Error: 14430)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14430&LinkId=20476

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

    Regards,
    Saravanan

  • May 30, 2011 at 7:14 am

    #1331619

    Are you using scripts or GUI?

    M&M

  • May 30, 2011 at 7:34 am

    #1331622

    I have used both.. Error remains the same.

    Regards,
    Saravanan

  • May 30, 2011 at 7:43 am

    #1331627

    Can you do a sp_helpdb master and share details of filename

    M&M

  • May 30, 2011 at 7:50 am

    #1331631

    Hi Mohammed ,

    Please find the details..even in sys.master_files the filenames are same...

    master1C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdfPRIMARY4096 KBUnlimited10%data only

    mastlog2C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldfNULL1280 KBUnlimited10%log only

    Regards,
    Saravanan

  • May 30, 2011 at 8:09 am

    #1331639

    Saravanan,

    I found some links related to the issue you are facing currently.

    http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/2c9bca8c-59c8-4d13-9ba3-dfc7e19139dd

    Hope it helps, but the solution isn't there in those links.

    M&M

  • November 25, 2011 at 11:29 am

    #1413050

    hi saravanan,

    i am facing this problem since last five days.

    whatever i have discovered about this problem is that this occurs due dropping the distributor accidentally. if this problem has occurred than first remove all of your publications on that server.

    after that run the procedure "sp_removedbreplication".

    then configure the distribution.

    after that create your publication.

    hope this will solve the problem.

Viewing 7 posts - 1 through 6 (of 6 total)

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