Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
BI41andAll
Contributor II
Contributor II

QlikView: cannot connect error

Anyone have experience with this error message when

  • opening an app in Access Point in any browser or even in QlikView desktop via qvp://
  • adding a new sheet object (table box)
  • closing the browser (chrome)
  • opening the same app in Access Point again
  • getting the 'cannot connect error' w/o the ability to get into the app again

The symptom can be fixed usually by going into QMC | 'Documents' tab | User Documents and removing server objects for the named user.  It only happens for this particular user.  If that does not get the user back in, then the shared file cleaning tool can be used.

Once back in, the user can get in and out and back in the same app as long as new sheet objects are not added by the user. Other users add the same (and even more complex) objects no problem.

Qlik SoftwareQlikView April 2019 SR2 v12.40.20200.0

I am stumped. Anyone experience the same thing?

Labels (2)
1 Solution

Accepted Solutions
BI41andAll
Contributor II
Contributor II
Author

Just to circle back. Qlik R&D did discover a bug and recommend an upgrade.  The issue went away after upgrading to May 2021.

View solution in original post

3 Replies
Lucas_Gatling
Support
Support

This might be a good issue to contact us at Qlik support about. Has this always happened with this one user or has it been an ongoing issue with the user for a while?

If the issue is solved please mark the answer with Accept as Solution.
marcus_sommer

Maybe this user hasn't a proper permission to create server objects. But it may be possible within a running session and by the next access it creates a conflict with the authentication between the server and/or the application and the shared-file and lastly the access will be denied.

Therefore I would check the authentication method and the authorization for this user and application and comparing it with the settings from other users/application which are working.

- Marcus 

BI41andAll
Contributor II
Contributor II
Author

Just to circle back. Qlik R&D did discover a bug and recommend an upgrade.  The issue went away after upgrading to May 2021.