Replication errors

I have been trying to get replication to work and have been having
nothing but problems.
I have a bunch of jobs set up in my EM and they all have red circles
with an X through it ( I assume this is because they all failed).
I have been trying to set up the publisher and distributer on the same
server.
Here is one of the jobs I can't get to work. I get an error on the
first step if I copy it to Query and run it. But when I right click the
job and look at the history I get the following message:
The job failed. The Job was invoked by User DINO\tfs. The last step to
run was step 3 (Detect nonlogged agent shutdown.).
According to this, I assume that it got to step 3 and died, but if I run
the Query (as I mentioned), it dies at step 1. The error I got was:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
If it couldn't find the stored procedure in Query, how could it find it
in the Job I ran?
Here are the steps that are running.
*******************************************************************
Step 1
Step Name: Log agent startup message.
Type: Transact-SQL Script(TSQL)
Database: Distribution
sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
@.runstatus = 1,
@.comments = 'Starting agent.'
I get an error here when running here from Query:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
Step 2
Step Name: Run Agent
Type: Replication Snapshot
Database: Distribution
-Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
-Publication [Northwind] -DistributorSecurityMode 1
Step 3
Step Name: Detect nonlogged agent shutdown.
Type: Transact-SQL Script(TSQL)
Database: Distribution
sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
***********************************************************************
The messages I get from history are not very helpful as it doesn't tell
me much. I had a job that got an error because a table didn't exist. I
know this because I tried it in Query. But the history of the job
always shows the same type of message. Just that the last step run was
X. But not why it died. Query knows why, why doesn't the Sql Agent?
Thanks,
Tom.Hi,
Check whether you can extract any information from the following url
http://www.cis.usouthal.edu/share/New%20Folder/Microsoft%20SQL%20Server/MSSQL/Install/instdist.sql
This contains the sp_MSdetect_nonlogged_shutdown stored procedure. At
present i am not able to provide any information coz i am unsure of the
setup you have installed there. I will try my best to sort this out.
Regards,
Jagan Mohan
"Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
news:3FC98D38.1020506@.deltanet.com...
> I have been trying to get replication to work and have been having
> nothing but problems.
> I have a bunch of jobs set up in my EM and they all have red circles
> with an X through it ( I assume this is because they all failed).
> I have been trying to set up the publisher and distributer on the same
> server.
> Here is one of the jobs I can't get to work. I get an error on the
> first step if I copy it to Query and run it. But when I right click the
> job and look at the history I get the following message:
> The job failed. The Job was invoked by User DINO\tfs. The last step to
> run was step 3 (Detect nonlogged agent shutdown.).
> According to this, I assume that it got to step 3 and died, but if I run
> the Query (as I mentioned), it dies at step 1. The error I got was:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>
> If it couldn't find the stored procedure in Query, how could it find it
> in the Job I ran?
> Here are the steps that are running.
> *******************************************************************
> Step 1
> Step Name: Log agent startup message.
> Type: Transact-SQL Script(TSQL)
> Database: Distribution
> sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
> @.runstatus = 1,
> @.comments = 'Starting agent.'
> I get an error here when running here from Query:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>
> Step 2
> Step Name: Run Agent
> Type: Replication Snapshot
> Database: Distribution
> -Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
> -Publication [Northwind] -DistributorSecurityMode 1
> Step 3
> Step Name: Detect nonlogged agent shutdown.
> Type: Transact-SQL Script(TSQL)
> Database: Distribution
> sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
> ***********************************************************************
> The messages I get from history are not very helpful as it doesn't tell
> me much. I had a job that got an error because a table didn't exist. I
> know this because I tried it in Query. But the history of the job
> always shows the same type of message. Just that the last step run was
> X. But not why it died. Query knows why, why doesn't the Sql Agent?
> Thanks,
> Tom.
>|||Jagan Mohan wrote:
> Hi,
> Check whether you can extract any information from the following url
> http://www.cis.usouthal.edu/share/New%20Folder/Microsoft%20SQL%20Server/MSSQL/Install/instdist.sql
> This contains the sp_MSdetect_nonlogged_shutdown stored procedure. At
> present i am not able to provide any information coz i am unsure of the
> setup you have installed there. I will try my best to sort this out.
I looked at it, but it won't tell me anything as the error says it can't
find the procedure. But the Server Agent got to the 3rd step, but
failed, so I assume it did step 1 correctly. Not sure what the
difference is.
> Regards,
> Jagan Mohan
> "Thomas Scheiderich" <tfs@.deltanet.com> wrote in message
> news:3FC98D38.1020506@.deltanet.com...
>>I have been trying to get replication to work and have been having
>>nothing but problems.
>>I have a bunch of jobs set up in my EM and they all have red circles
>>with an X through it ( I assume this is because they all failed).
>>I have been trying to set up the publisher and distributer on the same
>>server.
>>Here is one of the jobs I can't get to work. I get an error on the
>>first step if I copy it to Query and run it. But when I right click the
>>job and look at the history I get the following message:
>>The job failed. The Job was invoked by User DINO\tfs. The last step to
>>run was step 3 (Detect nonlogged agent shutdown.).
>>According to this, I assume that it got to step 3 and died, but if I run
>>the Query (as I mentioned), it dies at step 1. The error I got was:
>>Server: Msg 2812, Level 16, State 62, Line 1
>>Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>>
>>If it couldn't find the stored procedure in Query, how could it find it
>>in the Job I ran?
>>Here are the steps that are running.
>>*******************************************************************
>>Step 1
>>Step Name: Log agent startup message.
>>Type: Transact-SQL Script(TSQL)
>>Database: Distribution
>>sp_MSadd_distribution_history @.perfmon_increment = 0, @.agent_id = 2,
>>@.runstatus = 1,
>>@.comments = 'Starting agent.'
>>I get an error here when running here from Query:
>>Server: Msg 2812, Level 16, State 62, Line 1
>>Could not find stored procedure 'sp_MSdetect_nonlogged_shutdown'.
>>
>>Step 2
>>Step Name: Run Agent
>>Type: Replication Snapshot
>>Database: Distribution
>>-Publisher [DINO] -PublisherDB [Northwind] -Distributor [DINO]
>>-Publication [Northwind] -DistributorSecurityMode 1
>>Step 3
>>Step Name: Detect nonlogged agent shutdown.
>>Type: Transact-SQL Script(TSQL)
>>Database: Distribution
>>sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 2
>>***********************************************************************
>>The messages I get from history are not very helpful as it doesn't tell
>>me much. I had a job that got an error because a table didn't exist. I
>>know this because I tried it in Query. But the history of the job
>>always shows the same type of message. Just that the last step run was
>>X. But not why it died. Query knows why, why doesn't the Sql Agent?
>>Thanks,
>>Tom.
>>
>

Replication Breaks after applying SP4

Hi
I installed SP4 on our enterprise server this morning and now all
replication jobs fail with the message "No such interface supported"
Has anyone seen this before / know how to resolve this?
We run Enterprise Edition on Win2003
Many Thanks
D
nope. I suggest you re-register the replication dll's and exes. I think you
can find them in c:\program files\microsoft sql server\mssql\80\com
"DJ" <DJ@.discussions.microsoft.com> wrote in message
news:CA106D94-FD82-4099-A342-BF75A0910D5B@.microsoft.com...
> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||There was apparently an as yet not fully explained registry ACLing problem in
SP4 setup per the following thread (reported by Tomasz Skorupa originally):
http://groups.google.com/group/micro...85 a5a37097d4
With more than one person hitting the same problem, I would like to try
again and see if I can find out more about the cause of it. Was the user
running SP4 setup on the machine the same as the one running SQL Server Agent
service? If not, did the account running SP4 have privilege for enumerating
account information for the SQL Server Agent service account?
-Raymond Mak
"DJ" wrote:

> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||Thanks for the reply Raymond and apologies for not replying sooner but I have
been off work.
I tried re-registering the dll following the steps you mentioned in the
other thread but this did not work for me.
I re-registered them and stopped and started SQL Agent. Did I need to do
anything else?
The version of sqlrepss.dll on my instance is :2000.80.2039.0
I was not connected as the service account so I may not have had the
prvilages for enumeration the account informaion.
I can run the replication from the command line but I always get the error
when using Enterprise Manager.
Do you have any other suggestions to resolve this?
Many Thanks
Daryl
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> There was apparently an as yet not fully explained registry ACLing problem in
> SP4 setup per the following thread (reported by Tomasz Skorupa originally):
> http://groups.google.com/group/micro...85 a5a37097d4
> With more than one person hitting the same problem, I would like to try
> again and see if I can find out more about the cause of it. Was the user
> running SP4 setup on the machine the same as the one running SQL Server Agent
> service? If not, did the account running SP4 have privilege for enumerating
> account information for the SQL Server Agent service account?
> -Raymond Mak
>
> "DJ" wrote:
sql

Replication

I have replication configured in an sql 2005 environment. I have
executed the wizard twice but each time the following maintenance jobs
are missing
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
Expired subscription clean up
If someone can tell me what most be done to have these jobs created
or why the wizard failed to create them it would be a big help.What do you set up exactly? Distributor, Publisher and Subscriber? Also what
Replication method do you setup? Merge, Transactional, Snapshot?
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>I have replication configured in an sql 2005 environment. I have
> executed the wizard twice but each time the following maintenance jobs
> are missing
>
> Reinitialize subscriptions having data validation failures
> Agent history clean up: distribution
> Replication monitoring refresher for distribution.
> Replication agents checkup
> Distribution clean up: distribution
> Expired subscription clean up
> If someone can tell me what most be done to have these jobs created
> or why the wizard failed to create them it would be a big help.
>|||On Oct 8, 4:22 pm, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also w=hat
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem =D6nsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide q=uoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.|||Hello,
What version of SQL 2005 you are using. As there was bug prior SP1. try
increasing the size of your model db try configuring again.
Thanks
Ajay Rengunthwar
MCDBA,MCTS
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191876823.867493.221310@.50g2000hsm.googlegroups.com...
On Oct 8, 4:22 pm, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also
> what
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem Önsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide
> > quoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.