none
Uninitialized subscription 2016 Sp1 RRS feed

  • Question

  • On newly added subscription on 2016 Sp1 says “uninitialised subscription”  I tried “reinitialise subscription” but no luck. Any idea why is this and how to resolve use backup. When I check Agen jobs on Server C, I didnt find the job distributions  to subscriber job to start sync(log reader.) I am not sure why did't create the SQL Agent job for new subscript on the steps I did. 

    Environment

    I have transaction replication 2008R8(server A)  to 2014 pull subscription on 2014 (Server B).

    Please note distribution database configured on Server B( subscriber site). This has configured initialisation using backup and restore to subscribers

    Now I need to configure other subscriptions(Server B 2016 SP1 ) using same publisher Server A(2008 SP3). I need to configure other separate distribution server for Server C itself and should  subscriptions.

    Steps I did:

    Add distribution database on Server C

    Restore database full backup and log backup

    Create subscriber on publisher(sever A) using log backup

    use DB
    --go
    --EXEC sp_addsubscription
    -- @publication = N'DB', 
    -- @subscriber = N'Subscriber2', 
    -- @destination_db = N'DB', 
    -- @sync_type = N'initialize with backup',
    -- @backupdevicetype='Disk', 
    -- @backupdevicename='DISK_backup_201908271145.trn',
    -- @subscription_type = N'pull', 
    -- @update_mode = N'read only'

    ***But Agent job I referred didn't created  on Subscription site.

    Create  new subscriber on server C(This shows as uninitialised subscription




    • Edited by ashwan Tuesday, August 27, 2019 5:29 AM
    Tuesday, August 27, 2019 3:52 AM

All replies

  • Have you started to run the agent manually on the subscriber?
    Tuesday, August 27, 2019 3:30 PM
    Moderator
  • Hi Hilary, Thank you for the sharing  information . 

    IS that mean Server B "Log reader Agent job" will run the sync for both Server B(2014 version)  and Server C(2016 version). ? no other separate  "Log reader Agent job" for Server C(2016). Is that correct?

    regards

    Tuesday, August 27, 2019 11:35 PM
  • Hi Hilary, Thank you for the sharing  information . 

    IS that mean Server B "Log reader Agent job" will run the sync for both Server B(2014 version)  and Server C(2016 version). ? no other separate  "Log reader Agent job" for Server C(2016). Is that correct?

    regards

    Hi ashwan,

    Each Publisher can be assigned to only a single Distributor instance, but multiple publishers can share a Distributor. So, in your enviroment, server B is the only Distributor server, when you use the same publisher.

    Best regards,
    Cathy Ji

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com


    Wednesday, August 28, 2019 10:03 AM