Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello guys,
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?
Hello @Albert_Candelario
As promised, below my analysis during new code delivered by Qlik on our problem.
We have a 16% reload failed rates for my "big app" (I have 2) and 2% for my "small app"
Regarding error we have 12 "PATCH ERROR" and 7 "HTML ERROR".
Patch errors look like below:
Error completing job: Failed on attempt 6 to PATCH. (The remote server returned an error: (503) Service Unavailable.))
Error completing job: Failed on attempt 6 to PATCH. (The remote server returned an error: (429) Too Many Requests.))
HTML error are error which return an HTML code that warn us that our computer or network may be sending to many queries.
Probably a Google limitation right now to avoid any network problem.
It could be good to know what are the limitation to deal with it.
Regards,
Alexandre CHAMPIRÉ
Thanks @achampire.
The team is still working in this topic.
As mentioned, we will post new updated when having a meaningful one.
If any further doubt, do not hesitate to ask your already open support case with us.
Cheers,
Albert
i have hourly load not every time but now and then i see failure with this error, any suggestions?
Connector error: Error completing job: Failed on attempt 6 to PATCH. (The remote server returned an error: (429) Too Many Requests.
Hello @Channa,
Thanks for letting us know.
The team is still working on this within our technology partners.
If you do not have a case with our Technical Support team about it, I would suggest to raise one for checking at your particular scenario as for most of the partners and customers the issues has been highly mitigated or gone after the improvement delivered.
Cheers,
Albert
@Albert_Candelario Hi Albert,
I bump this thread again since the same problem seems to occur again regarding the Google Drive connector in Qlik Cloud.
Do you have any information regarding this and what is causing these random failures?
Yes this is happening again from last 2 or 3 days just simple message:
Connector error: CANCELLED
dosen't help much
We would appreciate if this was prioritized as many of our stakeholders are affected by the exports to Google Drive not working. I have also opened a support case and waiting for a response.
I still facing same error again any fix? from last 2 weeks
Same here and it is getting really frustrating! How should we move forward? Any update on this? @Albert_Candelario
We are facing serious problems since the 15th July 2024 with the Google Drive connector. Everything worked just fine until this date. Our reloads fails when reaching the STORE command. We have tested reducing the data, tweeking the file name, deleting and recreating the connection, but it won't help. We really need this to be fixed or at least get answers on what's causing this.
This is the error that we are getting from the log files:
Hi William
Do you currently have a case open?
If not, I would suggest opening one.