Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Error 0x80004005 when trying to specify connect string for connection manager with config environment variable

$
0
0

I'm using a configuration which specifies a connect string to a config database via an environment variable:

Data Source=QASQLONEPRI;Initial Catalog=SSISConfig;Provider=SQLNCLI10.1;FailoverPartner=QASQLONEFAL;Integrated Security=SSPI;

When I run my package from a remote machine, with a config environment variable set up as above I get, the following, this is despite the fact that I can connect to the database server: QASQLONEPRI from the remote machine using management studio without any issues, I have also tried using the OLDEDB client, but this leads to the same problem also. Can someone please advise as to how I can resolve this issue.

Error: 2012-08-22 11:34:10.54
   Code: 0xC0202009
   Source: ImportMain Connection manager "SSISConfig"
   Description: 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 err
or has occurred while establishing a connection to SQL Server. Server is not fou
nd or not accessible. Check if instance name is correct and if SQL Server is con
figured to allow remote connections. For more information see SQL Server Books O
nline.".
An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0
"  Hresult: 0x80004005  Description: "Named Pipes Provider: Could not open a con
nection to SQL Server [53]. ".
End Error
Warning: 2012-08-22 11:34:10.54
   Code: 0x80012059
   Source: ImportMain
   Description: Failed to load at least one of the configuration entries for the
 package. Check configuration entries for "Inbound Interface Config" and previou
s warnings to see descriptions of which configuration failed.
End Warning
Started:  11:33:09 AM
Finished: 11:34:10 AM
Elapsed:  60.875 seconds


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>