Error replication agent is not registered properly

We've been running transactional replication with updatable subscribers for
several months now. his morning we are seeing these errors in the LOG and
QUEUE READER logs.
You Receive Error Message: "The replication agent is not registered
properly. Rerun SQL Server setup.
Any ideas?
SQL Server 2000 SP3
Running the following command would likely resolve the issue:
"%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
Although I am curious to know if you have installed\uninstalled software
recently on the box that might have caused the problem in the first place.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
> We've been running transactional replication with updatable subscribers
> for
> several months now. his morning we are seeing these errors in the LOG and
> QUEUE READER logs.
>
> You Receive Error Message: "The replication agent is not registered
> properly. Rerun SQL Server setup.
>
> Any ideas?
> SQL Server 2000 SP3
>
|||Appreciate the info !
We are investigating if changes to either the OS or SQLServer itself are the
root cause of this problem. We are seeing that in addition to the queue
reader agent, these are also experiencing the same errors:
LOG READER agent
SNAPSHOT agent
DISTRIBUTION agent.
Does this means we also need to run the command below to register the above
agents as well or just 'qrdrsvc.exe' as you indicate?
==============
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
> Running the following command would likely resolve the issue:
> "%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
> Although I am curious to know if you have installed\uninstalled software
> recently on the box that might have caused the problem in the first place.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
>
|||This seems really strange, is this a clustered SQL Server instance or was
there a registry restore\repair on the box?
In any case, you can probably resolve the issue that you are seeing by
running the agent executables with the -RegServer parameter:
Snapshot agent - snapshot.exe
Logreader agent - logread.exe
Distribution agent - distrib.exe
If the problem is as extensive as it seems to be you may also need to
re-register the support dlls for the replication agents using regsvr32.exe.
Here is a list off the top of my head:
rinitcom.dll
repldp.dll
rdistcom.dll
-Raymond
"GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
> Appreciate the info !
>
> We are investigating if changes to either the OS or SQLServer itself are
> the root cause of this problem. We are seeing that in addition to the
> queue reader agent, these are also experiencing the same errors:
>
> LOG READER agent
> SNAPSHOT agent
> DISTRIBUTION agent.
>
> Does this means we also need to run the command below to register the
> above agents as well or just 'qrdrsvc.exe' as you indicate?
>
> ==============
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
>
|||This is a 2-node clustered SQLServer environment. Word were are getting is
that an attempt to install a new named instance on the cluster failed
(reason unknown) and had to be uninstalled. We are seeing these errors right
after this happened.
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
> This seems really strange, is this a clustered SQL Server instance or was
> there a registry restore\repair on the box?
> In any case, you can probably resolve the issue that you are seeing by
> running the agent executables with the -RegServer parameter:
> Snapshot agent - snapshot.exe
> Logreader agent - logread.exe
> Distribution agent - distrib.exe
> If the problem is as extensive as it seems to be you may also need to
> re-register the support dlls for the replication agents using
regsvr32.exe.[vbcol=seagreen]
> Here is a list off the top of my head:
> rinitcom.dll
> repldp.dll
> rdistcom.dll
> -Raymond
> "GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
> news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
software[vbcol=seagreen]
subscribers
>
|||It was determined that uninstalling one of the SQL instances on the cluster
caused the replication agents to be unregistered. We executed the commands
below and all went well with the exception of the QUEUE READER agent. When
we attempt to register the queue reader agent with 'qrdrsvc.exe regserver'
we get this error:
===================
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
=======================
Is there something special about registering queue reader agent ?
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> This is a 2-node clustered SQLServer environment. Word were are getting is
> that an attempt to install a new named instance on the cluster failed
> (reason unknown) and had to be uninstalled. We are seeing these errors
right[vbcol=seagreen]
> after this happened.
>
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
was[vbcol=seagreen]
> regsvr32.exe.
are[vbcol=seagreen]
> software
> subscribers
LOG
>
|||That seems kind of strange as I didn't get any messages when I tried the
same on my machine. But if you can start the queue reader agent from
SEM\SQLServerAgent then I wouldn't worry too much about it.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
> It was determined that uninstalling one of the SQL instances on the
> cluster
> caused the replication agents to be unregistered. We executed the commands
> below and all went well with the exception of the QUEUE READER agent.
> When
> we attempt to register the queue reader agent with
> 'qrdrsvc.exe -regserver'
> we get this error:
> ===================
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
> 2000 Microsoft Corporation
> Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
> exist or access denied.
> Unable to connect to Local Distributor
> Queue Reader aborting
> =======================
> Is there something special about registering queue reader agent ?
>
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> right
> was
> are
> LOG
>
|||I'm sorry. Can you please elaborate more on what you mean with
SEM\SQLServerAgent ? We are trying to start the queue reader agent from
Enterprise Manager and keep getting the error:
"The replication agent is not registered properly. Rerun SQL Server setup"
===================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> That seems kind of strange as I didn't get any messages when I tried the
> same on my machine. But if you can start the queue reader agent from
> SEM\SQLServerAgent then I wouldn't worry too much about it.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
commands[vbcol=seagreen]
(c)[vbcol=seagreen]
by[vbcol=seagreen]
to[vbcol=seagreen]
itself[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
Server\80\COM\qrdrsvc.exe" -RegServer[vbcol=seagreen]
first[vbcol=seagreen]
registered
>
|||Hi Mark,
When a replication agent is started through a SQL Server Agent job (which is
the same as starting a replication agent from SEM), SQL Server Agent will
activate the replication agent as a COM exe server rather than running it as
a regular executable. That is why I suspect that the COM registration
information for the replication agents was broken when you first reported
the problem. Now from what you have described, your SQL Server installation
was broken due to a clustered instance uninstall so a better course of
action is probably for you to reinstall SQL server rather than trying to fix
bits and pieces of it since nobody knows exactly what pieces are broken.
That said, it is still strange that running 'qrdrsvc.exe -regserver' didn't
return without errors for you (you would want to make sure that Word didn't
mangle the - for you...).
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
> I'm sorry. Can you please elaborate more on what you mean with
> SEM\SQLServerAgent ? We are trying to start the queue reader agent from
> Enterprise Manager and keep getting the error:
> "The replication agent is not registered properly. Rerun SQL Server setup"
> ===================
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...
> commands
> (c)
> by
> to
> itself
> the
> the
> Server\80\COM\qrdrsvc.exe" -RegServer
> first
> registered
>
|||In fact, this is what we are getting when running 'qrdrsvc.exe -regserver'
as a server administrator (with System Administrator role on the SQL server)
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
The process finished. Use CTRL+C to close this window.
=========================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23USLY0nAGHA.516@.TK2MSFTNGP15.phx.gbl...
> Hi Mark,
> When a replication agent is started through a SQL Server Agent job (which
is
> the same as starting a replication agent from SEM), SQL Server Agent will
> activate the replication agent as a COM exe server rather than running it
as
> a regular executable. That is why I suspect that the COM registration
> information for the replication agents was broken when you first reported
> the problem. Now from what you have described, your SQL Server
installation
> was broken due to a clustered instance uninstall so a better course of
> action is probably for you to reinstall SQL server rather than trying to
fix
> bits and pieces of it since nobody knows exactly what pieces are broken.
> That said, it is still strange that running 'qrdrsvc.exe -regserver'
didn't
> return without errors for you (you would want to make sure that Word
didn't[vbcol=seagreen]
> mangle the - for you...).
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
setup"[vbcol=seagreen]
the[vbcol=seagreen]
Copyright[vbcol=seagreen]
not[vbcol=seagreen]
failed[vbcol=seagreen]
errors[vbcol=seagreen]
seeing[vbcol=seagreen]
need[vbcol=seagreen]
to[vbcol=seagreen]
register[vbcol=seagreen]
message
>

Error Msg

On Feb 8, 4:19 pm, "Michael" <michae...@.gmail.com> wrote:
> Hi,
> If I use SQL Server Agent-Jobs to create a job agent to run a stored
> procedure. Where the error message from the stored procedure will go
> to? Say, I set the job from today to tomorrow, running every hour.
> Thanks!
> Mike
What I mean here Error Msg is the text I use RAISEERROR to put in the
output window. Where the text message will go if I use job agent?
Thanks,
Mike
Michael,
If you view job history and click "Show step details", you will see the
errors and messages in the text box at the bottom of the window. There is a
limit to what you can see here if there are a lot of messages or errors. You
can also:
select message from the msdb..sysjobhistory table
(watch the date and time columns, they are funky and will have to be
converted).
If you want to store it all for later review, send the text out to a file.
Edit a job step and open the Advanced tab and you'll see a place for file
name and a check box to determine if you should append to the file or not.
-- Bill
"Michael" <michaelnx@.gmail.com> wrote in message
news:1170970322.522398.278850@.q2g2000cwa.googlegro ups.com...
> On Feb 8, 4:19 pm, "Michael" <michae...@.gmail.com> wrote:
> What I mean here Error Msg is the text I use RAISEERROR to put in the
> output window. Where the text message will go if I use job agent?
> Thanks,
> Mike
>

Error Msg

Hi,
If I use SQL Server Agent-Jobs to create a job agent to run a stored
procedure. Where the error message from the stored procedure will go
to? Say, I set the job from today to tomorrow, running every hour.
Thanks!
MikeOn Feb 8, 4:19 pm, "Michael" <michae...@.gmail.com> wrote:
> Hi,
> If I use SQL Server Agent-Jobs to create a job agent to run a stored
> procedure. Where the error message from the stored procedure will go
> to? Say, I set the job from today to tomorrow, running every hour.
> Thanks!
> Mike
What I mean here Error Msg is the text I use RAISEERROR to put in the
output window. Where the text message will go if I use job agent?
Thanks,
Mike|||Michael,
If you view job history and click "Show step details", you will see the
errors and messages in the text box at the bottom of the window. There is a
limit to what you can see here if there are a lot of messages or errors. You
can also:
select message from the msdb..sysjobhistory table
(watch the date and time columns, they are funky and will have to be
converted).
If you want to store it all for later review, send the text out to a file.
Edit a job step and open the Advanced tab and you'll see a place for file
name and a check box to determine if you should append to the file or not.
-- Bill
"Michael" <michaelnx@.gmail.com> wrote in message
news:1170970322.522398.278850@.q2g2000cwa.googlegroups.com...
> On Feb 8, 4:19 pm, "Michael" <michae...@.gmail.com> wrote:
> What I mean here Error Msg is the text I use RAISEERROR to put in the
> output window. Where the text message will go if I use job agent?
> Thanks,
> Mike
>

Error Msg

Hi,
If I use SQL Server Agent-Jobs to create a job agent to run a stored
procedure. Where the error message from the stored procedure will go
to? Say, I set the job from today to tomorrow, running every hour.
Thanks!
MikeOn Feb 8, 4:19 pm, "Michael" <michae...@.gmail.com> wrote:
> Hi,
> If I use SQL Server Agent-Jobs to create a job agent to run a stored
> procedure. Where the error message from the stored procedure will go
> to? Say, I set the job from today to tomorrow, running every hour.
> Thanks!
> Mike
What I mean here Error Msg is the text I use RAISEERROR to put in the
output window. Where the text message will go if I use job agent?
Thanks,
Mike|||Michael,
If you view job history and click "Show step details", you will see the
errors and messages in the text box at the bottom of the window. There is a
limit to what you can see here if there are a lot of messages or errors. You
can also:
select message from the msdb..sysjobhistory table
(watch the date and time columns, they are funky and will have to be
converted).
If you want to store it all for later review, send the text out to a file.
Edit a job step and open the Advanced tab and you'll see a place for file
name and a check box to determine if you should append to the file or not.
-- Bill
"Michael" <michaelnx@.gmail.com> wrote in message
news:1170970322.522398.278850@.q2g2000cwa.googlegroups.com...
> On Feb 8, 4:19 pm, "Michael" <michae...@.gmail.com> wrote:
>> Hi,
>> If I use SQL Server Agent-Jobs to create a job agent to run a stored
>> procedure. Where the error message from the stored procedure will go
>> to? Say, I set the job from today to tomorrow, running every hour.
>> Thanks!
>> Mike
> What I mean here Error Msg is the text I use RAISEERROR to put in the
> output window. Where the text message will go if I use job agent?
> Thanks,
> Mike
>

Error message running a SSIS package in a Job

Hello,

I'm having problems when I try to run a package from a job in SQL Server Agent. I have the same package in a server and it works fine,but when I try to install it in a different server I keep getting this error:

Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started: 01:19:10 p.m.
Progress: 2007-01-30 13:19:10.40
Source: Delete scripts Execute Process Task
Operation Complete: 0% complete
End Progress
Error: 2007-01-30 13:19:10.57
Code: 0xC0029151
Source: Delete scripts Execute Process Task
Description: In Executing "C:\Project_SSIS\Delete_Items.bat" "" at "", The process exit code was "1" while the expected was "0".
End Error
Progress: 2007-01-30 13:19:10.57
Source: Delete scripts Execute Process Task
Operation Complete: 100% complete
End Progress
Warning: 2007-01-30 13:19:10.57
Code: 0x80019002
Source: Upload data
Description: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
End Warning
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 01:19:10 p.m.
Finished: 01:19:10 p.m.
Elapsed: 0.5 seconds

I can run it from Integration services Server, from BI, and I tried modifying the ProtectionLevel property to DontSaveSensitive and ServerStorage. I have other packages that run in jobs, and they work fine...but i don′t know what else to do....By the way, I'm using an administrator user to run the package.

Please help! =(

Does the SQL Server service account have access to the file, c:\project_ssis\delete_items.bat?|||Where can I check that?|||In the administrative control panel, open up the services. Then you'll have to look at the details of the SQL Server service, and see which user is listed. Then right-click on the file and look at its security properties to see if the user account has access. OR, skip all of that and right-click on the file and make sure that "Everyone" has read/execute access.

Phil|||

Hi Phil,

thank you for your replies. I checked the file's permissions and "Everyone" has read/execute access, but I still get the same message when executing from the job. The only diference I see is that the new server has Active Directory configured, and the one from my tests doesn't. Do I need to belong to certain group? Right now my user is only member of the Administrator group.

Error message after SQL SP3a.

Hi there;
I was trying to apply SQL SP3a on my windows 2000 server
(SP4), but the installation failed and when I rebooted my
server the SQL agent failed to start and I get the
following error:
SQLAGENT.exe - Entry Point Not Found
the procedure entry point SFMapi0GetProfiles could not be
located in the dynamic link library SEMMAP.dll
Now, I tried replying SQLSP3a, but that keeps on failing
and I keep getting this error message.
Any Idea .. Please help me.
Thank you.What's the error you get when upgrading to SP3a?
--
Michiel Wories, SQL Server PM
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"HUBCO" <anonymous@.discussions.microsoft.com> wrote in message
news:021601c395bd$4e33efd0$a101280a@.phx.gbl...
> Hi there;
> I was trying to apply SQL SP3a on my windows 2000 server
> (SP4), but the installation failed and when I rebooted my
> server the SQL agent failed to start and I get the
> following error:
> SQLAGENT.exe - Entry Point Not Found
> the procedure entry point SFMapi0GetProfiles could not be
> located in the dynamic link library SEMMAP.dll
> Now, I tried replying SQLSP3a, but that keeps on failing
> and I keep getting this error message.
> Any Idea .. Please help me.
> Thank you.