Saturday, February 25, 2012

Agents failed to load

Using SQL2005 EE SP1
I'm trying to set up a simple transactional replication with initial
snapshot (1st time on this server). I create the publisher and it says it's
successful, however the error log shows:
Job cannot run because LogReader subsystem failed to load. Job has been
suspended.
Job cannot run because Snapshot subsystem failed to load. Job has been
suspended.
Did I not install the proper components during the SQL2005 install?
Thanks
Ron
Is it possible that you have Express Edition on this box and this is the one
you are using? This is installed with Visual Studion and sometimes people
have got the editions confused. Pls can you run select SERVERPROPERTY (
'edition') to double check, and just in case you are connected to the EE in
SSMS, have a look at your list of services to see what services SQL server
appears under. If this is not the case then I'll see what other things we
could look for.
HTH,
Paul Ibison
|||Paul, it's definitely SQLServer2005 "Enterprise Edition" SP1.
"Paul Ibison" wrote:

> Is it possible that you have Express Edition on this box and this is the one
> you are using? This is installed with Visual Studion and sometimes people
> have got the editions confused. Pls can you run select SERVERPROPERTY (
> 'edition') to double check, and just in case you are connected to the EE in
> SSMS, have a look at your list of services to see what services SQL server
> appears under. If this is not the case then I'll see what other things we
> could look for.
> HTH,
> Paul Ibison
>
|||I'm all set now, I've got it working. Turns out there were earlier errors
from a couple of months ago that stated: Subsystem "LogReader" could not be
loaded
as well as the subsystems.
I googled that and the fix was to update the msdb.dbo.syssubsystems table to
point to the correct DLL and executable.
Thanks anyway.
"Ron" wrote:
[vbcol=seagreen]
> Paul, it's definitely SQLServer2005 "Enterprise Edition" SP1.
> "Paul Ibison" wrote:
|||Hi Ron - thanks for the update. I've found a potential cause of this issue
here: http://support.microsoft.com/kb/914171.
I'll add this to my website.
Cheers,
Paul Ibison

No comments:

Post a Comment