Multiple SSIS Package errors

Question

I have an SSIS package that was built 3 years ago by someone else that is long gone. I have ran it multiple times over the past year, and now I am getting these errors and I do not know why they are coming up. This ssis package imports from an excel doc to a temporary table. Once the info is on the temp table the second time it is run, it takes from the temp table and inserts it with additional columns into the production table. These are the errors I am getting:

[OLE DB Destination [162]] 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: "Unspecified error".

[OLE DB Destination [162]] Error: There was an error with input column "UserProfileID" (299) on 
input "OLE DB Destination Input" (175). The column status returned was: "The value violated the 
integrity constraints for the column.".

[OLE DB Destination [162]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.  The
"input "OLE DB Destination Input" (175)" failed because error code 0xC020907D occurred, and 
the error row disposition on "input "OLE DB Destination Input" (175)" specifies failure on 
error. An error occurred on the specified object of the specified component.  There may be 
error messages posted before this with more information about the failure.

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on 
component "OLE DB Destination" (162) failed with error code 0xC0209029 while processing input 
"OLE DB Destination Input" (175). The identified component returned an error from the 
ProcessInput method. The error is specific to the component, but the error is fatal and will
cause the Data Flow task to stop running.  There may be error messages posted before this with 
more information about the failure.

When I saw "error with input column 'UserProfileID'" i looked at it in the temp table and it is null. This is one of the columns that the package is supposed to find when it is run. But I don't know if that info is found with the second run or if it is supposed to populate the first time. So I am unsure if that is what the problem I am having is.

I appreciate any help that I can get. If any additional info is needed I can try and provide it. Thank you to anyone that can offer help.

Answer 1

Has the table had it's structure changed recently? If the field did not have a constraint before, and has one now, then you need to address the issue in your SSIS package to move any records which do not meet the constraint to an exception table or you need to find out why the constraint was added when it is not appropriate for the type of data being imported.

The next place I would look is the Excel file. When a package has been running a file for some time and suddenly has problems and there have been no changes to the structure of the table the data is being inserted into, then it is likely the data in the file is wrong.