LogReader not starting after installing a new instance of 2K8 R2

  • Hi there,

    My server is running with SQL Server 2008 and i had to do an installation of a parallel instance with 2K8 R2.

    After i did the installation everything started going mad and now the Log Reader(replication job) is always retrying with the following error :

    Message

    2014-10-28 13:03:11.462 Copyright (c) 2008 Microsoft Corporation

    2014-10-28 13:03:11.462 Microsoft SQL Server Replication Agent: logread

    2014-10-28 13:03:11.462

    2014-10-28 13:03:11.462 The timestamps prepended to the output lines are expressed in terms of UTC time.

    2014-10-28 13:03:11.462 User-specified agent parameter values:

    -Publisher MyServer

    -PublisherDB Pub_Database

    -Distributor MyServer

    -DistributorSecurityMode 1

    -Continuous

    -XJOBID 0x7378643F7E7F0342B454DE6170125D53

    -XJOBNAME MyServer-PubDB

    -XSTEPID 2

    -XSUBSYSTEM LogReader

    -XSERVER MyServer

    -XCMDLINE 0

    -XCancelEventHandle 0000000000000824

    -XParentProcessHandle 00000000000007C0

    2014-10-28 13:03:11.736 Status: 0, code: 22014, text: 'OLE error. Function 'CoCreateInstance()' failed with return code 2147746132.'.

    2014-10-28 13:03:11.736 OLE error. Function 'CoCreateInstance()' failed with return code 2147746132.

    2014-10-28 13:03:11.736 Status: 0, code: 22007, text: 'The process could not create 'IReplDist Interface'.'.

    Has anyone ever had the same issue ? How did you fixed it ?

    Thanks !!!

  • Already fairly obvious from the error, but you can run calc.exe in Programmer mode, and convert decimal 2147746132 to hex. The result will be 80040154. Search msdn for 80040154 and you will find it is REGDB_E_CLASSNOTREG, or "Class not registered" (for the IReplDist Interface, per the error message).

    Check SQL Server's bootstrap folders that concern the latest installs (for the SQL Server 2008 R2 instance) - you should be looking for COM errors that were experienced during the/those installation(s) - start with the summary files. You or a coworker can also attempt to repair the SQL Server 2008 R2 setup, if you are certain you or a coworker effectively have full administrative rights on SQL Server's OS.

  • Thanks for your help.

    I've already looked at the bootstrap setup files and all of them have final resut 'Passed'.

    One thing that is particulary weird is that all the .exe files for replication just vanished from my 100 Folder.

    I copied them from another server where i have 2008 installed and the Snapshot agent started working again but the LogReader is always returning the error that i showed before.

    Thanks,

    T

  • Running a setup repair is the safest bet - who knows what other files went AWOL.

    You could try Method 1 in http://support.microsoft.com/kb/811008, but that is a rather old KB article, and SQL Server setup has changed in every major version of SQL Server :).

    But before trying Method 1, I think it would be best to first find the string "distrib.exe-regserver" within all of bootstrap's setup logs, by using one of the search methods offered by http://stackoverflow.com/questions/408079/findstr-or-grep-that-autodetects-chararacter-encoding-utf-16.

Viewing 4 posts - 1 through 4 (of 4 total)

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