Named Pipes Provider: No process is on the other end of the pipe.

Who is online?  0 guests and 0 members
Home  »  Forums   »  microsoft business intelligence   »  integration services   » Named Pipes Provider: No process is on the other end of the pipe.

Named Pipes Provider: No process is on the other end of the pipe.

Topic RSS Feed

Posts under the topic: Named Pipes Provider: No process is on the other end of the pipe.

Posted: 4/20/2012

Jedi Youngling 9  points  Jedi Youngling
  • Joined on: 9/23/2011
  • Posts: 2

Hi, whenever i'm openeing a SSIS package on my local machine. Im getting this error:

Error	13	Error loading <PACKAGE NAME> 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: "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: "Communication link failure".  An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Named Pipes Provider: No process is on the other end of the pipe.  "	

 

help!!


Posted: 4/20/2012

Jedi Knight 2247  points  Jedi Knight
  • Joined on: 2/22/2010
  • Posts: 201

Few things:

Looks at your connection managers (OLEDB ones) in the package, what server are they pointing to? If it's a remote server...

Do you have permission to connect to the server that's in the connection manager? If you don't, that's what's happening. When you open an SSIS package it tries to validate all the connections and if you don't have access to the remote servers you'll get that message. 

The other possiblity is that instead of using an OLEDB connection manager someone tried to use a SQL Server Connection Manager, which only works if the package is running on the same server as the database its configured to connect to. Due to this limitation, that's why it's recommended you use OLEDB connection managers instead.


Page 1 of 1 (2 items)