Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ginoitalo
Starting Member
1 Post |
 Posted - 2004-03-26 : 17:59:54
|
| I have tried many times to make a user to run jobs rather than run it using sa, where it gets tough is that the job is a repl-merge job, which needs the proxy account. So I made one, the local admin account who also a SQL Server sys admin.When I run the job using the 'userJob' that I made (who has access to the publication, distribution db, and exec on sp_start_job) or even using the sa account: Job step 1 - Starts and finishes perfectly.Job step 2 - Run agent, it starts the merge agent, merge agent completes it's job, but the job progress never gets off this job step and therefore the job stays in 'executing' status forever (never completing, or if step 2 fails it never gets to step 3)When I cancel the job, this is the message:The job was stopped prior to completion by User sa. The Job was invoked by User userJob. The last step to run was step 2 (Run agent.).What's with the hanging after the merge agent completes ?Thanks,John |
|
|
|
|
|
User to start repl-merge jobs