Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Shared file corruption??

We have a *.shared file which gives errors.

In the QEMC we cannot edit anything for the QlikView report belonging to the shared file ... this gives the error: An exisiting connection was forcibly closed by the remote host. This probably happens because the shared file is read and changed for these actions.

In the QMC we can edit the QlikView settings, but this doesn't show the Shared objects we are interested in.

Using the powertools also this Shared file gives problems, e.g. with the Shared Object viewer ...

I know that throwing away the shared file will solve the problem, but since our users have their daily used user objects in this file we want to try to save this from distruction. We want to try to understand what is wrong with the file.

The end-users don't feel any problem with the Shared file since their objects are saved correctly.

Anyone has any clue what could happen here??

thx!!

rgrds,

Anita

12 Replies
Bill_Britt
Former Employee
Former Employee

Do you have session recovery enable? This will cause what you are talking about. I would disable it and see if the issue goes away.

Allow Session Recovery

All of the users can be allowed to recover from their sessions when lost. To allow all of the users to recover from their lost sessions, tick this check box. To deny all of the users to recover from their lost sessions, untick this check box.

QV11-2013-01-15-07-35-47.png

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
maksim_senin
Partner - Creator III
Partner - Creator III

Bill, yes the setting has been enabled from the day one and there were no problems till some (unknown) moment. The only possible reason why that happen is upgrade from 11SR1 (can remember the build no.) - there were no problems, to 11SR2 (build 11440) - not sure this is the reason but we didn't changed anything else at the server side.

michaelfreitas
Creator
Creator

This error occurred to me.

The logs of events windows you could see shared errors and users was displayed the message network connection.

I understood that .shared corrupted is the effect, not the cause.

The windows FIREWALL was active, blocking sometime QlikView doors, knocking the session of the users and corrupting the shared files.