April 7, 2016 at 4:53 am
Okay, this is weird and incredibly frustrating.
We have an SSIS package that has been working for a few months now without a problem. Yesterday it errored out because of a metadata issue. It can't implicitly convert between DT_STR and DT_WSTR.
Thing is, the file source is coded so all columns coming in are STR. When I check the Advanced Editor both External and Output reflect this. When I check the precedence link to the Derived Column Transformation, the metadata also shows STR. When I check the metadata on the precedence link between Derived Column and Destination (OLE DB), it also shows STR. And the Destination looks fine until I open it up, check mappings and hit OK. Suddenly it's erroring out on one single column which claims that it's coming in as WSTR.
When I check the Advanced Editor for the Destination, the external column properties show as WSTR and will not allow itself to be changed back to STR despite the fact that every other indication is that the column is set as STR. When I try adding the column to the Derived Column Transformation to force it to STR, it errors out there telling me it can't convert WSTR to STR.
Does anyone know what the heck is going on here? Google has nothing on this specific situation.
April 7, 2016 at 5:00 am
Nevermind. Someone changed the table definition on me. It had nothing to do with the package.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply