Replication Issue

aemhD 1

subscriber connection was down for days, after connection is back, the syncing process is not bi-directional any more!

I have checked the sp_replqueuemonitor at subscriber , the result is about 40K record!
Also, the queue reader agent continues failed showing an error
"Failed while applying queued message to publisher (Source: MSSQL_REPL, Error number: MSSQL_REPL36046)"
"the queue reader has encountered the error "could not find stored procedure *****""

Environment info:

SQL 2008 R2
Transactional Replication with updatable subscriptions

1 answer

AmeliaGu-MSFT 13,976 Reputation points Microsoft Vendor

2021-01-07T09:37:40.04+00:00

Hi aemhD-7221,
Can you find the stored procedure on the publisher database?
Could you please check if there are any detailed error messages? Please refer to this doc find errors with transactional replication.
In addition, you can try to install the latest SP and CU for SQL Server 2008 R2.
Best Regards,
Amelia
Please sign in to rate this answer.
aemhD 1 Reputation point

2021-01-07T12:41:05.603+00:00

HI Amelia, thanks for your replay

Actually I can't find the stored procedure on the publiaher DB, which is so weird!!
I have over a 36000 command in the queue reader with stored procedures can't be found suddenly!

I can't find any detailed messages, even SQL log file shows only
"Replication-Replication Transaction Queue Reader Subsystem: agent [SHROOUK-FEY].9 failed. The Queue Reader Agent has encountered the error ''Could not find stored procedure ''upd.sp_MSsync_upd_User_1''.'' when connecting to ''ERIS'' on ''SHROOUK-FEY''. Ensure that the publication and subscription are defined properly and that both servers are "

I tried the verbose logging, from the attached doc, but no file is created.

I need to mention that the transactions are working from publisher to subscriber, but not the other way, all hangs at the queue reader!

Latest updates are installed.

really hope you can help me.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Replication Issue

1 answer

Your answer