The exact error message received was as shown below.

Executed as user: Domain\User. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.1600.1 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  11:11:37 PM  Error: 2011-01-03 23:11:37.14     Code: 0xC0011007     Source: {1BDBB290-5831-476E-97F5-78DA45F876F4}      Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.  End Error  Error: 2011-01-03 23:11:37.14     Code: 0xC0011002     Source: {1BDBB290-5831-476E-97F5-78DA45F876F4}      Description: Failed to open package file "C:\SSIS\MyPackage.dtsx" due to error 0x80070005 "Access is denied.".  This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.  End Error  Could not load package "D:\SSIS\MyPackage.dtsx" because of error 0xC0011002.  Description: Failed to open package file "D:\SSIS\MyPackage.dtsx" due to error 0x80070005 "Access is denied.".  This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.  Source: {1BDBB290-5831-476E-97F5-78DA45F876F4}  Started:  11:11:37 PM  Finished: 11:11:37 PM  Elapsed:  0.031 seconds.  Process Exit Code 4.  .  NOTE: The step was retried the requested number of times (5) without succeeding.  The step failed.

Since the error message is talking about access, verified whether the security account with which SQL Agent Service is running has access to the server folder in which SSIS package is stored. Noticed that the security account doesn't have the access and the job started working after giving the read & write permission on the folder.

Let me know if this has helped you.

Usually the intention of comparison is to find out the missing rows from either of the tables or both. This where the operator "EXCEPT" comes very handy. Let us see it with an example.

 --Create two Tables--

CREATE TABLE TableA(ID Int, Name Varchar(256))

GO

CREATE TABLE TableB(ID Int, Name Varchar(256))

GO

INSERT INTO TableA VALUES(1,'A'),(2,'B'),(3,'D')

INSERT INTO TableB VALUES(1,'A'),(2,NULL),(3,'C')

--Get rows from TableA that are not found in TableB--

SELECT * FROM TableA

EXCEPT

SELECT * FROM TableB

--Get rows from TableB that are not found in TableA--

SELECT * FROM TableB

EXCEPT

SELECT * FROM TableA

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

CREATE PROCEDURE CompareTableData

(

@SourceDB sysname

,@SourceSchema sysname

,@SourceTable sysname

,@TargetDB sysname

,@TargetSchema sysname

,@TargetTable sysname

)

AS

BEGIN

SET NOCOUNT ON

DECLARE @SQL NVarchar(Max)

DECLARE @ColList Varchar(Max)

--Concatenate the column list by excluding the data types that can't be used in comparision--

SET @SQL = 'SELECT @ColList = CASE WHEN @ColList IS NULL THEN '''' ELSE @ColList + '','' END + SC.Name FROM ' + @SourceDB + '.sys.columns SC '

SET @SQL = @SQL + ' INNER JOIN ' + @SourceDB + '.sys.Types ST ON SC.system_type_id = ST.system_type_id WHERE object_id = object_id(@SourceTable) '

SET @SQL = @SQL + ' AND ST.Name NOT IN (''xml'',''Text'',''Image'',''Geometry'',''Geography'')'

EXEC sp_executesql @SQL,N'@ColList varchar(Max) OUTPUT,@SourceTable sysname',@ColList OUTPUT,@Sourcetable

--Get the rows that are missing from Target table--

SET @SQL = 'SELECT ''' + @TargetTable + ''' as RowMissingFrom,' + @ColList + ' FROM ' + @SourceDB + '.' + @SourceSchema + '.' + @SourceTable

SET @SQL = @SQL + ' EXCEPT '

SET @SQL = @SQL + ' SELECT ''' + @TargetTable + ''' as RowMissingFrom,' + @ColList + ' FROM ' + @TargetDB + '.' + @TargetSchema + '.' + @TargetTable

EXEC sp_executesql @SQL,N'@ColList varchar(Max)',@ColList

--Get the rows that are missing from Source table--

SET @SQL = ' SELECT ''' + @SourceTable + ''' as RowMissingFrom,' + @ColList + ' FROM ' + @TargetDB + '.' + @TargetSchema + '.' + @TargetTable

SET @SQL = @SQL + ' EXCEPT '

SET @SQL = @SQL + 'SELECT ''' + @SourceTable + ''' as RowMissingFrom,' + @ColList + ' FROM ' + @SourceDB + '.' + @SourceSchema + '.' + @SourceTable

EXEC sp_executesql @SQL,N'@ColList varchar(Max)',@ColList

END

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

Sample usgae of the procedure is:  EXEC  CompareTableData 'DB1','dbo','TableA','DB2','HR','TableB' 

 Please share your feedback if you find this interesting.

https://visualstudiogallery.msdn.microsoft.com/en-us/3e8c9b68-6e39-4577-b9b7-78489b5cb1da

Hope this helps :-)

Msg 22832, Level 16, State 1, Procedure sp_cdc_enable_table_internal, Line 607

Could not update the metadata that indicates table [dbo].[MyTable] is enabled for Change Data Capture. The failure occurred when executing the command '[sys].[sp_cdc_add_job] @job_type = N'capture''. The error returned was 916: 'The server principal "S-1-9-3-3045654011-13150378417-261222020-2009464159." is not able to access the database "msdb" under the current security context.'. Use the action and error to determine the cause of the failure and resubmit the request.

Since the failure message is saying the error occured while creating the Capture job, we tried explicitly creating the same using the system procedure "sp_cdc_add_job" as shown below and it solved the issue for us.

USE MyDatabase

EXECUTE sys.sp_cdc_enable_db

EXEC [sys].[sp_cdc_add_job] @job_type = N'capture'

EXECUTE sys.sp_cdc_enable_table @source_schema = N'dbo', @source_name = 'AdjustmentReason', @role_name = N'cdc_admin', @supports_net_changes = 1, @index_name = null, @captured_column_list = null, @filegroup_name = N'PRIMARY'

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

If you want more details on the above error, you can refer to the link https://msdn.microsoft.com/en-us/library/ee342155.aspx.

Please drop me an encouraging note if this work around has helped in solving your error. Thanks in advance. 

We started getting the "Unspecified Error" at random intervals of time and the jobs always failed at the Data Flow Task only. 

The job's error log has the following message. However, when the error is captured using an event handler in the package, an error code of "-2147467259" is reported.  

Code: 0x80004005

Source: <Data Flow Task Name> SSIS.Pipeline

Description: Unspecified error End Error

DTExec: The package execution returned DTSER_FAILURE (1)

After struggling for two weeks with the error, we finally fixed it by limiting the SQL Server Memory usage. We restricted SQL Server to consume 50% at the max. The reason for doing this is to leave enough memory to other services like Integration Services. Otherwise, over a period of time, SQL Server consumes almost all the available memory and releases it only when demanded by OS.

Here is the exact script we used, which you can tweak based on the percentage you want to allocate depending on your project requirement. Let me know if this blog has helped you.

The job continuously failed with the following error and in each run the failure occured at a different table.

Source: DFT_MyTable Source - MyTable

Description: 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: "Protocol error in TDS stream". An OLE DB record is available

The issue is solved when the Network Protocol used to connect to the source SQL Server is changed from TCP/IP to NamedPipes. Basically, an alias for the source is created on the destination server using the below steps.

1. Go to Start--> All Programs--> Microsoft SQL Server 2008--> Configuration Tools --> SQL Server Configuration Manager

2. Expand the node SQL Native Client 10.0 Configuration

3. Right click on "Aliases" and then select "New Alias..."

4. Provide the IP address of the Source SQL server against the "Server" field and specify the Source server name against the "Alias Name" field.

5. Choose the protocol as "NamedPipes" and click OK

The fix for this is to change the databse owner to "sa" by executing the below script.

USE <Database>

EXEC sp_changedbowner 'sa'

Read the below KB article for more details.

https://support.microsoft.com/kb/913423

After struggling for some time, I noticed that an "Instead of Insert" Trigger exist on the Table. The interesting thing is, no change is happening to the Idenity column in the Trigger definition. However, disabling that Trigger fixed the issue miraculously :-)

Let me know if this fix has helped you too. 

1. Run SSIS Package using dtexec.exe (Either from a command file or through a Job running on SQL Server 2008)

2. Open SSIS package using VS2008 or BIDS

If you have a log file for the job, the exact error essage you see would be as follows:

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

Microsoft (R) SQL Server Execute Package Utility
Version 10.0.1600.22 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Error: 
   Code: 0xC0011007
   Source: {95765D16-E9AA-4DDA-9932-9DF1281E1208}
   Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.
End Error
Error: 
   Code: 0xC0011002
   Source: {95765D16-E9AA-4DDA-9932-9DF1281E1208}
   Description: Failed to open package file "E:\MyPackage.dtsx" due to error 0x80070020 "The process cannot access the file because it is being used by another process.".  This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
End Error
Could not load package "E:\MyPackage.dtsx" because of error 0xC0011002.
Description: Failed to open package file "E:\MyPackage.dtsx" due to error 0x80070020 "The process cannot access the file because it is being used by another process.".  This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
Source: {95765D16-E9AA-4DDA-9932-9DF1281E1208}

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

Fix: The fix is same as the one I explained in my other blog. The physical path of SQL Server 2008's DTEXEC.exe should appear first in the PATH environment variable.

This message disappeared after installing VSTS 2008 Power Tools. The download link is provided for your quick reference here. 

https://www.microsoft.com/downloads/details.aspx?FamilyId=FBD14EEA-781F-45A1-8C46-9F6BA2F68BF0&displaylang=en

Please share your feedback if the same fix has helped you.