November 20, 2013 at 2:45 pm
When I set my SSIS package up as a job, I am getting :
Executed as user: RADAC\SC-DEV. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 4:30:00 PM Could not load package "\Data Collector\IMP_OTIF" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80040E4D (Login failed for user 'RADAC\SC-DEV'.). The SQL statement that was issued has failed.
So how do I set SSIS up to give the account we use for SQL Server Agent access to run packages?
November 21, 2013 at 2:26 am
The message:
Login failed for user 'RADAC\SC-DEV'
gives you a fairly strong clue as to what the problem is, I think. This is not package-related, rather it relates to the SQL instance to which the package is trying to connect.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
November 21, 2013 at 6:55 am
The account has access to SQL server... I have heard that to run SSIS through a job, the user has to have admin permissions... is this correct?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply