March 24, 2005 at 7:01 am
We have SQL agent acting as an overall job scheduler. I have 2 issues:
1) On one job, the VB app runs fine when executed from the command line, but not when executed from the SQL Agent (does not run - no log). Suspecting a permissions issue, I checked the setup. It is set up to use trusted connections, SQL Server is logging in with an administrator account that mapped to the server admistrator group. What else should I check?
2) Periodically, some Agent jobs that normally complete, fail with out errors. These are jobs that combine TSQL with VB or Crystal Reports jobs. Any ideas where to look?
March 25, 2005 at 1:00 pm
1) You are probably right on about Permissions, but it is the permissions of the account running the job. Check the account that SQLServer Agent service is using, and for each job step, check the parameter "Run as user..." (under Advanced). Those are the accounts that the job runs under, not the account that you log into for SQL server EM or the SQL Server service.
2) Check for deadlocks? Often developers don't handle those too well.
Mark
May 17, 2005 at 11:25 am
Sorry for the delay. Got pulled several directions at once. Everything checked OK, but now we'll not know, because the jobs were switched to a 3rd party scheduler and the problem disappeared.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply