All previously defined folder mount points have disappeared and documents are not available via AccessPoint.
Environment:
The mounted folders are saved in the settings.ini file. If the information in the file changes in a way that the QlikView Server cannot interpret or read correctly when is starting, it will be recreated and the mounted folders will be gone.
Note: The following depicts theoretical possible scenarios only, and is not guaranteed to be the root cause in all cases:
The issue may occur more frequently if all QVS nodes are taken offline at the same time and for an environmental reason, the settings.ini of the first QVS node to come back online is corrupt. In that scenario the file will be recreated with matching information found in the iniData.pgo file stored in the Root directory. This is the mechanism used to update the other QVS's nodes' local settings.ini files. If it is unable to reach or interpret the iniData.pgo file, it may update/recreate that file according to the information found in the settings.ini. The next QVS nodes to come up will then look at the new information in the iniData.pgo and update their settings.ini with missing information.
Another scenario where the behaviour occurs intermittently could be related to this defect: Settings.ini changes not propagated from one QlikView node to another. This defect causes the settings.ini information to not be propagated, which the iniData.pgo relies on. It is resolved in 12.20 SR4 and later. But other causes can lead to the settings.ini not being synchronized (Antivirus scans, locked files, network issues, etc...)
It is worth mentioning that .pgo files can also become corrupt, and information there can potentially be cleared. Why a file gets corrupted, for e.g. .shared or .pgo?
Resolution:
- Review the mount folder locations in the QVS settings.ini (under C:\ProgramData\QlikTech\QlikViewServer) file to determine if there was a bad write to the file.
- Check that the root folder which holding the iniData.pgo is accessible at all times, and that this file has not been recreated or become corrupt.
- Monitor what process/services/servers are accessing these file(s).
- The information in the iniData.pgo file can be read when enabling a .xml copy. This may be used for troubleshooting purposes. Reading PGO contents and CAL assignments / PGO to XML
More information on iniData.pgo file found under What information is stored in the QlikView PGO files? and under What Information is stored in the QlikView IniData.pgo?
