June 18, 2012 at 3:22 am
Hi ,
I am using sql2008r2 edition, I have replication in same server with different database, I have stopped the SqlserverAgent , then while I am Creating tables OR Inserting records into tables, it is showing error,
"SQLServerAgent is not currently running so it cannot be notified of this action."
how i can resolve this issue, with out starting the agent.
I need to suppress that issue.
Thanks®ards
Ramana
June 18, 2012 at 3:44 am
Response please...?
June 18, 2012 at 4:31 am
I think this error message is NOT from replication.
It could be from CDC (change data capture) or some thing like that.
Do some investigation. Check all SQL Agent jobs, triggers, etc. in the server.
June 18, 2012 at 5:58 am
If started the Sql Agent, error is not coming, If it is stop then error is coming.
June 18, 2012 at 7:12 am
For replication it creates some job....
please specify why you want to do that with agent off.
there is a way in which you can use one utility from microsoft replmerg.exe to work as an agent.
I used this in the environment where I need to setup merge replication between
SQL Server Enterprise Edition(Publisher) , SQL Server Enterprise Express edition(subscriber) were aroung 400 subscribers and one publisher.
I think your problem is similar.
Sagar Sonawane
** Every DBA has his day!!:cool:
June 18, 2012 at 8:07 am
I am using transactional replication, some times as per my front End Application, We need to stop the agent. In that time it error is replicating.
June 18, 2012 at 8:57 am
When you stop SQL Agent, you are not just stopping the 1, 2, or 3 jobs that you have running for replication... You are stopping ALL jobs. This doesn't seem to make sense that a front end application needs you to completely stop the agent. What are you accomplishing by doing this? If you are simply stopping replication, then do it by stopping replication instead of disabling SQL Server Agent.
Jared
CE - Microsoft
June 18, 2012 at 11:23 pm
Ramana P (6/18/2012)
...I have replication in same server with different database,
Why are you replicating in same server with different database?
Have you checked the Replication Monitor? Have you checked the replication job history?
Do you have any CDC configured? Do you have triggers?
You need to need to answer these questions to resolve this issue.
June 19, 2012 at 4:55 am
Suresh B. (6/18/2012)
Ramana P (6/18/2012)
...I have replication in same server with different database,Why are you replicating in same server with different database?
Have you checked the Replication Monitor? Have you checked the replication job history?
Do you have any CDC configured? Do you have triggers?
You need to need to answer these questions to resolve this issue.
Why is any of this relevant? The problem is not with replication, it is with manipulating objects and data that are replicated while the agent is off. Which seems to be the problem... Also, I know of many cases where replication is used on the same server.
Jared
CE - Microsoft
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply