Hi guys - I have a problem. So I have a SSIS package (2008). They use an environment variable configuration that points to a dtsConfig file that has the connection string to the configuration database. This database is on a same server with the packages. I am using a stored procedure to call that SSIS package along with it's config file using DTEXEC command. But getting following error. Error 2 Error loading Package.dtsx: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. ". Even when I am just executing that package along with the particular config, using dtx utility window, I get the same error. I have tried to create a .udl file and I get success on the connection for the same server and DB.Thoughts? Thanks!

your package cannot connect to underlying SQL Server ; A network-related or instance-specific error has occurred while establishing a connection to SQL Server could you check the connection managers? did you used sql authentication or windows authentication? what is protection Level of package? http://www.rad.pasfu.com

Thanks for your Reply. It is resolved now.

What was the ultimate resolution for this? I'm getting the same error and can't figure it out. Here's my setup: SQL Server 2008; SQL Server service and Agent service both running as the same domain account; Windows Server 2008 R2; it's all 64-bit; package installed to MSDB; package using XML configuration I have two database connections set up in my package. Both connections point to databases on the server that the package is running on. The first db connection points to a database with the source data and the destination tables. The second connection points to my SSIS_Log database for writing error logs. When I execute my package that has been installed on the server, the source/destination db connection fails with the same error you posted. The second db connection works just fine and it actually writes error messages to the error log table. Below are the package configuration entries from the XML file for connecting to the two databases. I used to have the config for both connections setup by specifying the dbname and dbservername. Since that wasn't working for the source/destination connection, I switched it to provide it the whole connection string. I have this same basic thing working in production for the last several years in SQL Server 2005. <Configuration ConfiguredType="Property" Path="\Package.Variables[User::cIDB_DbConnectionString].Properties[Value]" ValueType="String"><ConfiguredValue>Data Source=db-server;Initial Catalog=DBv5;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;Application Name=scale2SAP_v5;Persist Security Info=False;</ConfiguredValue></Configuration> <Configuration ConfiguredType="Property" Path="\Package.Variables[User::cLog_DbName].Properties[Value]" ValueType="String"><ConfiguredValue>SSIS_Log</ConfiguredValue></Configuration> <Configuration ConfiguredType="Property" Path="\Package.Variables[User::cLog_DbServerName].Properties[Value]" ValueType="String"><ConfiguredValue>db-server</ConfiguredValue></Configuration> Any thoughts?