My own issue is not similar to those mentioned in this forum.
I have got some SSIS packages stored in MSDB database. Exporting some of them gives this type of error
Communication link failure Shared Memory Provider: No process
is on the other end
of the pipe. (Microsoft sql
Disabling Shared Memory Protocol and exporting the package again reports error on the other protocols (TCP and Named Pipe) depending on which of them at the top of priority list.
I have had a look at the server
and client protocols configurations. These settings seems to be working fine. I even had to disable and reorder them but the error still persists.
The irony of it is that the error is not coming up on all the packages.
I have restarted the engine and looked at the error log.
The log reports are as follows:
SQL Server is now ready for client connections. This is an informational message; no user action is required. Server is listening on [ 127.0.0.1 <ipv4> 1434]. Server named pipe provider
is ready to accept connection
on [ \\.\pipe\sql\query ]. Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. Server is listening on [ 'any' <ipv4> 1433].
I'm suspecting these packages but they are running
fine without any errors.
There is no certificate installed on the box.
Does anyone have a clue why this is happening?
One more thing the server configs are:
Win 2003 SP1, SQL 2005 RTM.
I'm not suspecting SQL service pack since the issues are not occurring on production with the same configurations. I'm planning to apply SP3 on the box though.