June 16, 2017 at 12:56 pm
Hi,
On a server running SQL Server 2008 R2 10.50.4042 (I know, SP2 is outdated...), there is multiple SSIS packages scheduled to run regularly.
Once in a while, a packages fails with this error:
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: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe. ".
I also noticed CA Unified Infrastructure Manager (Nimsoft)'s sqlserver probe failing with same error
I was able to force the sqlserver probe to use TCP/IP protocole by prefixing the server name with "tcp:" in the connection string. Since then, I didn't get any connection error for the sqlserver probe.
I don't have any control on how the SSIS packages connect to the SQL instance, so I can't force them to use tcp/ip. So, I was wondering if the shared memory protocole has any known limitations, like number of concurrent connections?
Thank you very much
June 17, 2017 at 4:26 am
Eric Prévost - Friday, June 16, 2017 12:56 PMHi,
On a server running SQL Server 2008 R2 10.50.4042 (I know, SP2 is outdated...), there is multiple SSIS packages scheduled to run regularly.Once in a while, a packages fails with this error:
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: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe. ".
I also noticed CA Unified Infrastructure Manager (Nimsoft)'s sqlserver probe failing with same error
I was able to force the sqlserver probe to use TCP/IP protocole by prefixing the server name with "tcp:" in the connection string. Since then, I didn't get any connection error for the sqlserver probe.I don't have any control on how the SSIS packages connect to the SQL instance, so I can't force them to use tcp/ip. So, I was wondering if the shared memory protocole has any known limitations, like number of concurrent connections?
Thank you very much
Shared Memory is a simple non-configurable, local only protocol. Connection limits are therefore only the local resource limitations. Are the SSIS packages running on the same instance as the SQL Server?
😎
June 19, 2017 at 6:35 am
Yes, the SSIS packages are run locally through SQL Agent jobs
June 19, 2017 at 7:31 am
Eric Prévost - Monday, June 19, 2017 6:35 AMYes, the SSIS packages are run locally through SQL Agent jobs
What are the permissions of the account that the SSIS package run?
😎
June 19, 2017 at 8:09 am
Way too much permissions for its own good... sysadmin of the SQL Server instance and member of Domain Admins group. (Please don't shoot the messenger, I didn't set this up)
Connection doesn't fail every time. It happens randomly on a regular basis.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply