SSIS Lookup issues

Using PGNP with MS SQL Server, Data Transformation Services (DTS), SQL Server Integration Services (SSIS), Linked Servers, Snapshot and Transactional Replication and more.

SSIS Lookup issues

Postby psimonis » Wed Jun 05, 2013 7:31 am

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?
psimonis
 
Posts: 5
Joined: Wed Jun 05, 2013 7:25 am

Re: SSIS Lookup issues

Postby Moderator » Thu Jun 06, 2013 11:43 pm

We are troubleshooting the issue. Will update shortly.
User avatar
Moderator
Site Admin
 
Posts: 302
Joined: Wed Oct 29, 2008 11:27 pm

Re: SSIS Lookup issues

Postby psimonis » Sun Jun 09, 2013 1:12 pm

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
psimonis
 
Posts: 5
Joined: Wed Jun 05, 2013 7:25 am

Re: SSIS Lookup issues

Postby psimonis » Mon Jun 24, 2013 11:55 am

Any updates yet?
psimonis
 
Posts: 5
Joined: Wed Jun 05, 2013 7:25 am

Re: SSIS Lookup issues

Postby Moderator » Mon Jun 24, 2013 10:59 pm

The issue is caused by internal error when matching column identifiers. We are working on the fix.
User avatar
Moderator
Site Admin
 
Posts: 302
Joined: Wed Oct 29, 2008 11:27 pm

Re: SSIS Lookup issues

Postby psimonis » Fri Aug 02, 2013 12:04 am

Still nothing?
psimonis
 
Posts: 5
Joined: Wed Jun 05, 2013 7:25 am

Re: SSIS Lookup issues

Postby Moderator » Wed Aug 07, 2013 11:08 pm

Sorry for delay in updating the thread. We found a workaround: setting property hasSideEffect="true" on Lookup Input Column (and a few other components) makes the package run. Could you try the workaround and see if it worked on your system?

However, we have not been able to find why the package execution failed. This issue is temporarily on hold. We will return to investigation shortly.
User avatar
Moderator
Site Admin
 
Posts: 302
Joined: Wed Oct 29, 2008 11:27 pm

Re: SSIS Lookup issues

Postby geoftak » Sun Sep 22, 2013 11:55 am

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 ?
geoftak
 
Posts: 3
Joined: Sun Sep 22, 2013 11:54 am

Re: SSIS Lookup issues

Postby Moderator » Wed Oct 09, 2013 4:11 am

Method 1 "From BIDS UI". Right mouse click on "OLE DB Destination" and click "Show Advanced Editor...". On the "Input and Output properties" tab select "OLE DB Destination Input" in the left pane. HasSideEffect will be shown in Common Properties on the right.
Method 2. Edit dstx file in notepad. Find hasSideEffects property and change it to true.
User avatar
Moderator
Site Admin
 
Posts: 302
Joined: Wed Oct 29, 2008 11:27 pm

Re: SSIS Lookup issues

Postby geoftak » Wed Oct 16, 2013 1:33 am

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 ?
geoftak
 
Posts: 3
Joined: Sun Sep 22, 2013 11:54 am

Next

Return to SQL Server/DTS/SSIS/Linked servers/Replication

Who is online

Users browsing this forum: No registered users and 2 guests

cron