Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Bucharest on Sept 18th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Bernard_rosencrantz
Contributor
Contributor

The following error occurred: (Connector error: Invalid row status 5 at 4)

Hi, over the weekend something changed in my database I kept getting this error when I try to load the data:

The following error occurred:
(Connector error: Invalid row status 5 at 4).

I assume I have faulty data in my database and want qlik to ignore it. The database has a lot of entries so it is impossible for me to go through the database and find the value.
 
The database is a Mongodb
 
Data load script:
 
LIB CONNECT TO 'MongodbXXXXXYYYYYY'; // I had to hide this
LOAD _id,
status,
 
[posts]:
SELECT [_id],
status,
FROM XXXX.YYYY; //had to hide this
 
Labels (2)
1 Solution

Accepted Solutions
Solvica
Contributor II
Contributor II

Hi, in our case it has been caused by having invalid date format in the database (something like 15.08.20023) - we had to fix these records and then it worked fine.

Pavel

View solution in original post

5 Replies
Albert_Candelario

Hello @Bernard_rosencrantz ,

Thanks for posting.

Have you tried to load a limited amount of rows of your BD and open the scrip in debug mode? If not, I would suggest giving it a shot:

Debug the data load script | Qlik Cloud Help

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer
Solvica
Contributor II
Contributor II

Hello @Bernard_rosencrantz ,

did you get it working? I am facing the same issue using PostgreSQL.

Thanks.

Pavel

prinzchristian
Partner - Contributor III
Partner - Contributor III

Wurde hier bereits eine Lösung gefunden - Habe das gleiche Verhalten über den PostgreSQL on Prem wie auch in der SaaS? 

prinzchristian_0-1693836160203.png

 

Vielen Dank! 🙂 

Solvica
Contributor II
Contributor II

Hi, in our case it has been caused by having invalid date format in the database (something like 15.08.20023) - we had to fix these records and then it worked fine.

Pavel

prinzchristian
Partner - Contributor III
Partner - Contributor III

Vielen Dank! 🙂 
Dann werde ich mich mal in die DB stürzen und die Sätze identifizieren.