September 13, 2011 at 6:08 am
Does anyone have an idea how to solve an SSIS error code -10716007685? I have searched endlessly for anwers but nothing really worthwhile.
I am trying to load a Fact table and keep getting the same error.
September 13, 2011 at 10:46 am
john.sliwinski (9/13/2011)
Does anyone have an idea how to solve an SSIS error code -10716007685? I have searched endlessly for anwers but nothing really worthwhile.I am trying to load a Fact table and keep getting the same error.
You will have to give more information...
Are you logging errors to the database or a text file? If not, you should do this first and see what the error description in the log is.
Secondly, have you used a data viewer in SSIS to try and identify the source of the errors?
Please post your package if possible, or at least a screenshot (and detailed explanation of the package). We need more info in order to help you.
September 13, 2011 at 12:20 pm
Thank you for your quick response.
I am logging the errors to a text file which display:
1. error code - the negative number I posted
2. error column - always zero
3. error description - ' no status available'
Also I have used the data viewer and checked for possible duplicates on the database which there are none and also do not have any contraints. In researching the error code, those were possible causes of the error itself.
Due to security reasons I am unable to send the package.
Does any of the above help?
September 13, 2011 at 12:38 pm
john.sliwinski (9/13/2011)
Thank you for your quick response.I am logging the errors to a text file which display:
1. error code - the negative number I posted
2. error column - always zero
3. error description - ' no status available'
Also I have used the data viewer and checked for possible duplicates on the database which there are none and also do not have any contraints. In researching the error code, those were possible causes of the error itself.
Due to security reasons I am unable to send the package.
Does any of the above help?
Unfortunately not much...
Is it possible to redirect error rows? Maybe that will help to identify bad data (if that is the source of the error).
Are you executing queries/stored procedures to populate your fact table? If so, why not run the queries/stored procs in SSMS. That should give you more descriptive errors (I hope).
Alternatively I would suggest that you do the following:
1. Create a test table, an exact duplicate of your destination.
2. Remove all constraints from the test table (including primary key), and see if the package succeeds. If it does, attempt to add the constraints/primary key/unique indexes one-by-one to see which one makes it fail. Doing this will help you identify if a constraint is the culprit (and bad data or code of course)
3. If the above still doesn't work, change the data types in your destination fields to varchar. If the package succeeds, you know it is a data type issue and you will also be able to run some sql queries on the data to identify the errors.
4. If all of this still doesn't work, your problem lies somewhere else...
Without more information about your package, the above is unfortunately all I can give you at this stage. The process of elimination is tedious, but a good way to go about resolving errors if it isn't obvious.
Hope this helps.
September 13, 2011 at 1:06 pm
Thanks again.
I am redirecting rows and nothing in the text file stands out since I manually took the data that failed and inserted into the table without issue.
In SSIS the Fact Table (OLE DB Destination) takes care of inserting the data via column mappings.
I will try your suggestions and see if that helps.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply