The RPC security information for the Publisher is missing or invalid.

  • I have created Transaction-updatable replication between two databases in sqlserver 2005. At the subscriber end if i make any changes i get the following error while saving changes made to the table.

    No row was updated

    The data in row 1 was not committed.

    Error Source: .Net SqlClient Data Provider.

    Error Message: The RPC security information for the Publisher is missing or invalid. Use sp_link_publication to specify it.

    Updateable Subscriptions: Rolling back transaction.

    The transaction ended in the trigger. The batch has been aborted.

    Please provide help.

  • Exactly the same problme here. If I find a fix I'll let you know.

  • n_padma (11/5/2008)


    I have created Transaction-updatable replication between two databases in sqlserver 2005. At the subscriber end if i make any changes i get the following error while saving changes made to the table.

    No row was updated

    The data in row 1 was not committed.

    Error Source: .Net SqlClient Data Provider.

    Error Message: The RPC security information for the Publisher is missing or invalid. Use sp_link_publication to specify it.

    Updateable Subscriptions: Rolling back transaction.

    The transaction ended in the trigger. The batch has been aborted.

    Please provide help.

    Have you ran sp_link_publication in the subscriber database?

    sp_link_publication @publisher = '{publisher instance name}'

    , @publisher_db = '{published database name}'

    , @publication = '{publication name}'

    , @security_mode = '1'

    , @login = '{sql server login account to connect publisher}'

    , @password = '{password}'

    , @distributor = '{distributor instance name}'


    * Noel

  • Hi,

    I did but the syntax I deduced from the ms web site was a bit different.

    I’ll try your syntax on Monday.

    Thanks a lot and have a great weekend.

    Paul

  • Good Luck


    * Noel

  • The sp_link_publication did not work.

    I have changed the options in security configuration of MSDTC section of the component services to 'allow remote administration' and 'allow inbound' and 'allow outbound' under transaction manager communication.

    This setup is on a two node cluster. Do I have to restart the servers after making this change or I should be restarting the MSDTC resource alone?

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

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