Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Job Fails 1/2 Way Through When Scheduled, Completes Manually Expand / Collapse
Author
Message
Posted Thursday, August 29, 2013 7:37 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:15 PM
Points: 2,832, Visits: 8,508
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.



Post #1489721
Posted Thursday, August 29, 2013 9:17 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:08 AM
Points: 35,366, Visits: 31,901
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1489986
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse