SSIS Lookup issues

When using the PGNP Native OLEDB Provider in Microsoft SQL Server Integration Services (SSIS), it shows strange behaviour.

I’m constructing a SSIS package with an OLEDB DB Source which connects to a PostgreSQL database, nothing out of the ordinary here.
This source provides the expected records from the database. All seems well.

After this step however, the records move towards a lookup Transaction. This transaction causes the SSIS Package to stop.
No errors or warnings in advance, it just stops.

When examining this package in Visual Studio 2008, the lookup transaction does show a correct preview for the results from the database.
So the lookup is able to connect to the database.

Does anyone have any idea's on how to debug or possibly even fix the lookup transaction?

Below the content of "SQLDUMPER_ERRORLOG.txt" created after running a package with a lookup.

(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 5652
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 00000000006D0B58
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 5652
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x00000000006D0B58
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x0000000000000000
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x0000000000000000
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(1828:16F8) 06/09/13 21:48:33, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\100\Shared\ErrorDumps\SQLDmpr0003.mdmp
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll'
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE'
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '2009.100:1600.1'
(1828:16F8) 06/09/13 21:48:34, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '10.50:1600.1'
(1828:16F8) 06/09/13 21:48:34, ACTION, DtsDebugHost.exe, Watson Invoke: No

Any updates yet?

Still nothing?

Hello, this error is also a problem for us.

Could you give us some explaination on how to set property hasSideEffect="true", as this property seems to be read only ?

Hello, thank you, but the method 1 is not possible for me as the property is read-only in the BIDS. Is there a way to make it editable ?

The method 2 is not convenient and I had problems while testing it.

Are you planning to fix the issue ?

Hello, any news on this issue ?

I have the same issue. Lookup connection to PostgreSQL causes the same issue mentioned above. For now I transfer the lookup table to cache and set the connection to cache table.

I set the property hasSideEffect="true" (I did it textually since it is read only in the Lookup component editor) on Lookup Input Column, but it did not help, same problem occurs.

Hi,

We have a somewhat different problem. We use a MsSQL DB as source and PostGres as destination. Before inserting, I want to make sure the rows do not exist via a lookup. When no rows are in the destination, the flow runs fine, but when there are already rows in the destination, it throws errors at pre-processing:

[Lookup P2S [805]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21.
[Lookup P2S [805]] Error: OLE DB error occurred while populating internal cache. Check SQLCommand and SqlCommandParam properties.
[Lookup P2S [805]] Information: The component "Lookup P2S" (805) failed to process the rows in the cache. The processing time was 0.125 second(s).
[SSIS.Pipeline] Error: component "Lookup P2S" (805) failed the pre-execute phase and returned error code 0xC020824E.

I changed the hasSideEffect="true", but that did not work.

I also changed to "no cache", but that returns, while processing:

[Lookup P2S [805]] Error: OLE DB error occurred while fetching parameterized row. Check SQLCommand and SqlCommandParam properties.