SSIS Job - Proxy Login Failure
-
If anybody can offer some advice on a problem with Integration Services I have I'll be eternally grateful. I'm all out of ideas and getting frustrated to say the least! :mad: 1. I have a SQL job that runs an Integration Services package 2. The job is set up to run using a proxy account. 3. When then job is run it fails with the following error: Could not load package because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed. 4. The package name is correct. 5. I’ve double-checked that the password used for the proxy account is correct. 6. I am able to connect to Integration Services using the same account as the proxy and run the job directly from there.
-
If anybody can offer some advice on a problem with Integration Services I have I'll be eternally grateful. I'm all out of ideas and getting frustrated to say the least! :mad: 1. I have a SQL job that runs an Integration Services package 2. The job is set up to run using a proxy account. 3. When then job is run it fails with the following error: Could not load package because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed. 4. The package name is correct. 5. I’ve double-checked that the password used for the proxy account is correct. 6. I am able to connect to Integration Services using the same account as the proxy and run the job directly from there.
lmaycock wrote:
(Login timeout expired)
I think that is your smoking gun. You can set the timeout on connections to infinite(usually 0 represents infinite as a value) to solve this sort of issue. Something like this: commandObj.CommandTimeout = 0
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
lmaycock wrote:
(Login timeout expired)
I think that is your smoking gun. You can set the timeout on connections to infinite(usually 0 represents infinite as a value) to solve this sort of issue. Something like this: commandObj.CommandTimeout = 0
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens