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?

We are troubleshooting the issue. Will update shortly.

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?

The issue is caused by internal error when matching column identifiers. We are working on the fix.

Still nothing?