Post reply

Replication subsystems failed to load

  • September 4, 2009 at 3:18 pm

    #210297

    I am running SQL 2008 Enterprize Edition with SP1 on Windows 2008. I am trying to set up replication. I have completed the following:

    1. Created distribution Database

    2. Created publisher

    3. Granted SQL Agent access to the ...MSSQL\100\Com folder to execute the agent_exe files

    4. Granted SQL Agent access to ...\MSSQL\binn where the subsystem_dll files are located

    5. Granted SQL Agent write permissions to ...\MSSQL\repldata in order the write the bcp files

    Each time I try to initialize the snapshot, I get the following errors in the SQL Agent Log

    1. Log Step.......cannot be run because the LogReader subsystem failed to load. The job has been suspended.

    2. Log Step.......cannot be run because the Snapshot subsystem failed to load. The job has been suspended.

    I found posts where the records in the msdb.dbo.syssubsystems pointed to different folders than where the dll and exe files are located. So, I checked that, but they are correct.

    The SQL Agent has sysadmin on the SQL Server and is using a windows service account.

    I believe it is a security issue because I can run the executables from the command prompt to generate the snapshot for the publication. Have I missed the forest for the trees?

    Any help would be greatly appreciated.

    :crying:

  • September 8, 2009 at 11:59 am

    #1050694

    FYI. When installing replication after the initial installation, you need to restart SQL Server Agent. That fixed the problem.:-)

  • May 2, 2010 at 9:59 pm

    #1161070

    Thx, was indeed the answer.

  • January 25, 2013 at 8:09 am

    #1581062

    Yup - restart of the Agent fixed it for me too. Feel like a newb for not thinking of that. 🙂

  • May 15, 2013 at 7:04 am

    #1615401

    It even works at 4:00am during a really hectic upgrade!!! Thanks!!!!

  • November 25, 2013 at 9:20 am

    #1668856

    Thanks! This worked for me too. Was spinning my wheels all morning trying to figure this one out. I knew it had to be a simple trick.

  • March 25, 2014 at 12:23 pm

    #1700020

    After 1659 days of this question, still helping.

    Thanks a lot.

  • January 27, 2015 at 9:12 am

    #1773411

    Saved the day, thanks. SQL agent service restart fixed the problem.

  • February 25, 2015 at 5:01 pm

    #1780092

    Cheers, this worked for me.

  • May 18, 2016 at 2:33 am

    #1879761

    Much appreciated, this worked for me as well. Wasted 30-40mins looking in various log files.

Viewing 10 posts - 1 through 9 (of 9 total)

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