Consider the following scenario for either SQL Server 2005 or SQL Server 2008 environments:

• You configure your SQL Server to use SSL for connections.
• You configure your SQL server to use a network packet size that is greater than the default value (4K)

In this scenario, you will notice the following:

• An attempt to either save SSIS packages to the MSDB package store will fail with the following error message:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Communication link failure).The SQL statement that was issued has failed. 

Note: You also run into the above error message when saving maintenance plans created in SQL Server Management Studio as SSIS packages to MSDB databases since that operation inherently uses encryption for connections to SQL Server.

• Data collector feature in SQL Server 2008 that uses SSIS, runs into various issues as noted below:
• • A Data Collection Set job reports the following errors in the Job History: 

dcexec: Error: Internal error at Main (Reason: The system cannot find the file specified).
dcexec: Error: Internal error at Main (Reason: The handle is invalid).

Package "Set_{7B191952-8ECF-4E12-AEB2-EF646EF79FEF}_Master_Package_Collection" failed.

If you review the Data Collector logs you will find an error message similar to the following.

SSIS error. Component name: TaskForCollectionItem_1, Code: -1073602332, Subcomponent: (null), Description: Error 0xC0014062 while preparing to load the package. The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Communication link failure).  The SQL statement that was issued has failed. 

Note: The problem could happen with any operation that uses either LoadFromSqlServer orSaveToSqlServer methods when both the conditions (encryption and large packet size) 

--------------------------

To resolve this problem, specify a network packet size that is smaller than 16384 (16K) bytes.You may use the following code to set the network packet size configuration option of thesp_configure system stored procedure:

EXEC sp_configure 'network packet size', 16383

RECONFIGURE WITH OVERRIDE 

GO 

The network packet size can also be altered via the Server Properties page in Object Explorer. Select the Advanced option and type in the new value for Network Packet Size and click OK.

Note: You do not need to restart SQL Server for the change to be effective.