We are also troubleshooting this issue.
We looked at the server logs during these disconnects and found the following line.
Windows System Info: Failed to translate name DOMAIN\USERNAME - "The parameter is incorrect.
Where "DOMAIN" and "USERNAME" are our domain and the username of the person that created the bookmark.
In our case, the USERNAME is no longer an employee of the company.
Hexediting the .shared file shows that username in several places, we are going to replace that username with another one (with the same number of characters) and see if that resolves our issue.
We found this same issue in QV 10 SR4. It is in fact caused by there being bookmarks in the .SHARED file referencing users that have been deleted from the active directory. There is no issue with deactivated users.
This issue causes the following problems:
- In the Ajax client, the document crashes and a message saying "Session lost" appears. This renders the entire QlikView document unusable.
- When using the IE plugin, the application works until one tries to add or edit bookmarks. The document crashes and this message appears: "Server communication lost, closing document!"
- When using the Enterprise Management Console, and trying to view the document in the User Documents section, the following message appears: "An existing connection was forcibly closed by the remote host". Thereafter, no settings can be made for the document, and a crash of the entire management console occurs if an attempt is made.
The are two fixes to this issue, none of which are optimal solutions:
- Delete the .SHARED file and lose all your bookmarks
- Edit the .SHARED file and delete any references to users no longer in the Active Directory.
As solution #1 is not a viable solution for us as our users have many bookmarks, we opted for solution #2.
To edit the .SHARED file we used the Shared File Viewer provided in the QlikView Power Tools package. With this tool, we found deleted users, unchecked them, and pressed Defrag to save the file without those users. The document worked again.
This is an issue that needs to be addressed by QlikTech as the required maintenance of removing users is tedious, and a missing user should not be a cause for a crash of the entire document.
I hope this helped anyone else experiencing this problem