Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
WEBINAR June 25, 2025: Build on Apache Iceberg with Qlik Open Lakehouse - REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
piotr-bratek
Creator
Creator

Strange symptoms of a data gateway connection. Connector error DirectAccess-1006.

Hi,
we've already set up a data gateway connection to SAP following all recommendations and best practices.
We've created a new connection in the Qlik Cloud and when we reload our data the result is quite strange:

* the 1st table  works fine - it is being loaded 
* the 2nd one usually crahses with the error given below
* sometimes it loads two tables before it crashes

Yes, we also changed the order of the first 3 apps - all combinations - no difference.

As you can see on the screenshot, we also tested the app with limited load (1000 rows) just to exclude potential performance issues. No difference.

I'm waiting for log access but hope that someone has already solved a similar issue.

sap-datagateway.jpg

I would understand if it didn't work at all, but as you can see it starts fine and it crashes soon after the 1st or a 2nd table.

The most experienced Qlik Trainer in Central Europe
Labels (2)
3 Replies
henrikalmen
Specialist II
Specialist II

Other people seem to have had this issue as well. Perhaps this thread can help you: https://community.qlik.com/t5/Connectivity-Data-Prep/Help-Connector-error-Invalid-load-request-Direc...

And this article mentions that error 1006 has been resolved in version "Direct Access gateway 1.6.0", perhaps you need to upgrade? https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/direct-access-g... 

piotr-bratek
Creator
Creator
Author

Hi henrikalmen,

well, the problem occured with the newest DG version which unfortunately means it is still valid.
Another strange thing though is, that the day after, we tried again, removed FIRST N prefixes and it worked well. Yet I still don't know when it comes back.

The most experienced Qlik Trainer in Central Europe
mshann01
Creator
Creator

Did you try adding a "Disconnect" statement after each load and then reconnecting right before each load?  You shouldn't have to do this but might help with troubleshooting or at least help get the load to run if it's a production job.