October 18, 2007 at 10:40 am
I am getting the following errors when I try to connect to certain databases. Thanks for any help. Do I need to use the Surface area configuration tools to allow remote connections? This is occurring on SQL Server 2000 instances too. I know there is no way to enable remote desktop because there is no Surface Area Configuration Tool in 2000. Also, I can connect to the instance through Management Studio. Any help is appreciated. I have bolded the most important errors. Also, it keeps referring to a 2000 instance as a 2005 instance. This is very weird.
Error: 0xC0202009 at Populate_DBA_REP, Connection manager "MultiServer": SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login timeout expired".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [2]. ".
Error: 0xC020801C at Load Servers, OLE DB Source [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "MultiServer" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Load Servers, DTS.Pipeline: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Load Servers, DTS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Load Servers: There were errors during task validation.
October 18, 2007 at 11:25 am
Could it be an FW issue? Can you telnet to the MSSQL server on TCP 1433 from wherever the package is running. i.e. Start -> Run -> cmd -> telnet HOST 1433
Tommy
Follow @sqlscribeOctober 27, 2007 at 10:07 am
Inside the package at the connection manager (pointing sql 2005) which authentication mode you are using??? If sql then you should use the remote sql login (login in sql 2005 server) and make a test connection from the connection manager itself.
Regards..Vidhya Sagar
SQL-Articles
October 29, 2007 at 3:45 am
Maybe a network problem. Ask comms to check the firewall(s) and routers to ensure you are being allowed through.
Also, have you installed Oracle client services on the users computers?
October 29, 2007 at 6:48 am
The server is mixed mode. I can connect through the connection manager, so I can't figure out what could be the problem.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply