SSIS error listing

SSIS error listing

• ogg

  Oh, yeah, and the VS_ISBROKEN validation status message is classic.
  

• Parripati

  Indeed, it seems SQL Server CTP shipped without error code #defines in header files in SDK directory \Program Files\Microsoft SQL Server\90\SDK\
  
  This makes it really hard to develop components!
  
  Microsoft team, will the listing of error codes be made available (and when)
  Thanks.
  
  

• Huckster

  By the way, if you see large negative number as error code, it's COM HRESULT (i.e. it follows COM policy for use of certain bit fields, see MSDN for more details). Convert it to hex and you get 0xC020901E. But what this means I can't tell you until we can get error header file for IS...
  

• Stevenls

  I think it's still hex, the L at the end is usually included in literals to denote the size of the integer - i.e. L = long, whatever that may be for the platform, 32bits in this case I'd imagine.
  
  -S
  
  
  
  
  

• ajes

  JimArgeropoulos wrote:

  Even looking at the header file doesn't add much information. Why did the look up fail I have been staring at a look up for nearly a day now and I don't have a clue why the look up is failing. It is a text-to-text compare. I have played with trimming, converting to/from Unicode. I don't see the reason for the failure. I am just stumped.

  
  Jim,
  What is the issue perhaps you could start another thread and we could try and help out.
  
  Regards
  Jamie
  
  
  

• Ozan

  Even looking at the header file doesn't add much information. Why did the look up fail
  
  I have been staring at a look up for nearly a day now and I don't have a clue why the look up is failing. It is a text-to-text compare. I have played with trimming, converting to/from Unicode. I don't see the reason for the failure. I am just stumped.

  
  

• a_vc3p

  The error codes seem stange, they are not hex but they look liek hex. 0xC0202002L is teh value listed, so why the L on th end When the errors are rasied and shown in the UI, they do not include the L.
  Que

  
  
  

• skolima

  Actually,
  
  I found the errors in the following file:
   \Microsoft SQL Server\90\SDK\Include\dtsmsg.h
  
  
  

• Goodwill

  Jim,
  Good to know! Thanks for sharing this - I certainly wasn't aware of this issue.
  
  -Jamie
  
  
  

• JustinHess

  Yep, you found it. DtsMsg.h is the header with the errors.
  
  

• tpickett

  My issue turned out to be string length.
  
  I have two databases A and B for the sake of discussion. A is a transactional database, and B is a dimensional design I am exploring. The A database contains a table with lots of constants. I populated a table in B from a subset of the constants as one of my dimensions.
  
  Later when trying to populate a fact table, I needed to do a look up to go from meaningless Id in A to meaningless Id B. I was matching on a string that existed in both A and B.
  
  If I ran without redirection, the error message is
  
  [Lookup 1 [239]] Error: The "component "Lookup 1" (239)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Output" (241)" specifies failure on error. An error occurred on the specified object of the specified component.
  
  If I ran with redirection, error code was -1071607778.
  
  Both should have been the same because I populated one from the other. Because the string existed in a table where many potential constants could be stored, the field size needed to be much larger. I shortened the field size in B, because I knew the content. However the look up failed because the strings were different lengths. A very subtle problem. But I finally found it.
  
• SSIS error listing