JOBS won't run | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

JOBS won’t run

I have just migrated a db from one SQL Server to another. Everything seems to work fine. All of my DTS’s work perfectly on the new system, however when I schedule the JOBS to run at night, the fail. This is what it says when I pull up the View Job History:<br /><br />DTSRun: Loading… Error: -2147217843 (80040E4D); Provider Error: 18456 (481<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ /> Error string: Login failed for user ”. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0. Process Exit Code 1. The step failed.<br /><br />I can’t remember how to give permission for the system to run JOBS.[<img src=’/community/emoticons/emotion-6.gif’ alt=’:(‘ />]<br /><br />Any and all help is appreciated.
Check the account which uis being used to run SQL Server Agent. Gaurav
Moderator
Man thrives, oddly enough, only in the presence of a challenging environment- L. Ron Hubbard

Verify that a SQL Server authentication login or a Windows authentication login exists in SQL Server. If not you have to create it. What type of security authentication are you using?
‘SQL Server’ (mixed) or ‘Windows Only’? If you’re using ‘Windows Only’ authentication, try using the mixed mode
authentication and assign a valid user id and password. Jon M

I have several logins already in the db. I use a mix. How do I check the account which is being used to run SQL Server Agent?
Try this,<br />From Enterprise Manager:<br />1. Click Management folder of your SQL Server.<br />2. Right-mouse click on SQL Server Agent -&gt; Properties.<br />3. Click ‘Connection’ Tab and view your SQL Server connection.<br /><br />Make sure that userid exists in SQL Server Security and you are supplying the correct password. [<img src=’/community/emoticons/emotion-2.gif’ alt=’:D‘ />]<br /><br />Jon M<br /><br />
Not specified version you’re using if its ver.7 then refer to this KBAhttp://support.microsoft.com/defaul…port/kb/articles/Q237/6/04.asp&NoWebContent=1 to fix the issue. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com

The SQL agent is using Window NT authentication.
So if your jobs need to access some resources other than local machine, you’ll have to start the agent under the domain account which has the required privilages on the required resources. Gaurav
Moderator
Man thrives, oddly enough, only in the presence of a challenging environment- L. Ron Hubbard

… as specified by the referred KBA.
And authentication is set on server level not on the service level. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com

I’M AN IDIOT I have solved the problem. When I moved the DTS’s from the old server, I forgot to change the connections within the DTS. They were still trying to pull the tables from my Oracle DB into my OLD SQL Server.
I’m glad you solved the problem!!! Rather than think of yourself as having a Homer moment, think of it more that you learnt something new.
]]>