Could not load package "" because of error 0xC0014062. The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired).
I am getting following error while trying to run the SSIs package from command prompt using a bat file. (dtexec).
This package runs without any issues from SSIS server on my desktop machine (32 bit) but when I deploy it on development box it gives the folloing error. Package was initially working on the dev box(64 bit machine I guess) but after installilng the Business Intelligence studion over there it started giving this 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.
I have searched many places in the net and no where I could find answer
did you try using the 32 bit version of dtexec on the 64 bit server?
Using the 32 bit version of DTExec on a 64 bit machine:
SSIS 2005: C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe
SSIS 2008: C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtexec.exe
Duane Douglas, MCAD | http://www.ssisbi.com | Please mark the post(s) that answered your question.
Thanks for the reply. I found the problem to be a stupid one which very logical for a beginner.
I used the SSIS Integration server name to call the package from bat file using the /SQL option. I realise that you should use the dbserver name where the package is installed for that option. Also I learned other two options for calling pacakge.
/DTS. here u can use the dts server name. /file - you can use the location of the dtsx file.
- Proposed as answer by ETL vs ELTL Monday, March 29, 2010 12:00 PM
Could not load package "" because of error 0xC0014062.
The LoadFromSQLServer method has encountered OLE DB error code 0x80004005
In my job task, on the command line tab, step into, from the beginnig saw the command starts with "/SQL" + ETLpath
Wath do you think about, what's happened?, what i did wrong? The stange of this, is the ETL has been executing close 2 months, but today, show me this error, something to comment, if i manually
executes job task, or etl, all is fine, but the programatic task job is the problem.
I get the same error when launching simultaneously a great number of jobs which run the same package with different configuration.
It seems to be an overload issue.
In my case the solution is to configure a Retry when the job fails :
-Retry Attempt = 4 (for example)
-Retry Interval (minutes) = 11 (for example)
SQL Server Database Engine v10.50.2500