I am facing since the 6th december 2022 a problem with applications using Store instruction on a Google Drive folder.
Everything worked fine until this date. Applications runned hourly without any problems and all my QVDs were generated correcly.
Since the 6th december at 08:00 PM CEST, my reload tend to fail on a random Store instruction. By random, I mean that it is not especially one QVD.
I have 2 types of error thatI am facing
Data has not been loaded. Please correct the error and try loading again. The following error occurred: Cannot open file: 'lib://Google drive connector/<idfolder>/accounts.qvd' (Connector error: Error completing job: Object reference not set to an instance of an object.) The error occurred here: Store accounts into [lib://Google drive connector/<idfolder>/accounts.qvd] (qvd)
Data has not been loaded. Please correct the error and try loading again. The following error occurred: Cannot open file: 'lib://Google drive connector/<idfolder>/projet .qvd' (Connector error: Exception in reading response chunk for upload: Status(StatusCode="Unknown", Detail="Error during upload: Object reference not set to an instance of an object.")) The error occurred here: Store projet into [Google drive connector/<idfolder>/projet .qvd] (qvd)
Do you guys have an idea about why do I have this errors? Are you facing the same problem since the 6th december too?
I'm getting the exact same error. I don't know what to think, sometimes my script completes the stores without any issue and sometimes the error appears on table A or table B. I didn't change anything from my script and it was working fine until December...
Qlik, do you know something about it?
Same here, since Dec 6th.
As I heard, google drive changed its authentication method. I think Qlik Connectors couldnt catch the change yet, unfortunately..
All of my dashboards rely on qvd import/export to google drive. Please fix this ASAP.
Thanks for highlighting this issue.
Our engineering team is investigating it on high priority.
When having a meaningful update we will update.
@achampire Mail I got from support:
"According to the R&D the root cause of this issue has been found and an according fix has been released.
Can you please test on your side and let me know if the result?"
I dont get error anymore, can you try it too?
@barsssk I got the same answer from a case that I created yesterday on that topic.
I activated my reload schedule this morning (it was deactivated by the 5th time on failed).
It seems good for the first reload. I will take a look today to confirm that.