Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Job Fails 1/2 Way Through When Scheduled, Completes Manually


Job Fails 1/2 Way Through When Scheduled, Completes Manually

Author
Message
homebrew01
homebrew01
SSCrazy
SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)

Group: General Forum Members
Points: 2980 Visits: 9071
I've got a bit of a puzzle. I have a job that restores the production databases to reporting servers every morning, then runs a step to fix the logins so they have permissions to the restored databases.

Basically, it loops through all the logins, and for each one it runs:
sp_grantdbaccess
sp_changegroup
sp_defaultdb


When the job runs automatically, it gets partway through the list, then fails, but I don't see why. If I run the stored procedure, it completes. If the users are already in the database, I will get the message:

User, group, or role 'Angie' already exists in the current database.

But the SP keeps running until they are all processed.

Is there some limiter that causes it to fail after a certain # of errors in a scheduled job?

The scheduled job processed 6 of the 20 logins, even though "Angie" is first and throws an error. I can run the SP manually and after all the logins have been processed and in the DB, they all throw errors, but the SP at least runs all the way through.



Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)

Group: General Forum Members
Points: 44994 Visits: 39880
I'd be interested in knowing the answer to this because I have a similar problem with a backup proc. I specifically programmed it to catch an error in a TRY/CATCH and then continue. When I run it manually, it works correctly by noting the error in my "run log" table and continues. If I run it as a scheduled job, it fails and quits instead of continuing.

I know I'm going to feel like an idiot when someone exposes a simple answer for this but that' the tradeoff I'm willing to make for the fix for this problem... if it can be fixed.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
     Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search