The description for Event ID 300 from source QlikViewServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
System: PGO - Failed to store latest data to file: An unknown error occurred while accessing ..\F$\qvrootdirectory\dashboards\ServerCounters.pgo.
System: PGO - Failed to store latest data to file: An unknown error occurred while accessing ..\F$\qvrootdirectory\dashboards\IniData.pgo.
Sean, you find better information in the actual QVS Event logs and you can see things in context to everything else that was going on at the time provided you are running the QVS logging level at High Verbosity in the QMC settings.
That being said, what this one is telling you is we had an issue being able to process an update to the file share, which could be many different things, you will have to do some further digging to try to sort out exactly what happened. Here is a Help link regarding the .pgo files and what each one does:
About the best I can offer without further log info. Oh, I would be cautious using Admin file shares, this can bite you, we do recommend creating specific shares, as that way you control the share permissions, Admin shares are controlled completely by the OS, you cannot change any settings etc... One thing that could be going on is maybe Anti-Virus scan or some other utility on that file server that took away our ability to get the exclusive lock on the file... It can occur if the environment is very busy though and you have more than one QVS node, if one of the QVS services in the cluster is very busy, it may hang on to a .pgo longer than normally expected causing the other nodes to have issues being able to write things out.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
Sean, you find better information in the actual QVS Event logs and you can see things in context to everything else that was going on at the time provided you are running the QVS logging level at High Verbosity in the QMC settings.
That being said, what this one is telling you is we had an issue being able to process an update to the file share, which could be many different things, you will have to do some further digging to try to sort out exactly what happened. Here is a Help link regarding the .pgo files and what each one does:
About the best I can offer without further log info. Oh, I would be cautious using Admin file shares, this can bite you, we do recommend creating specific shares, as that way you control the share permissions, Admin shares are controlled completely by the OS, you cannot change any settings etc... One thing that could be going on is maybe Anti-Virus scan or some other utility on that file server that took away our ability to get the exclusive lock on the file... It can occur if the environment is very busy though and you have more than one QVS node, if one of the QVS services in the cluster is very busy, it may hang on to a .pgo longer than normally expected causing the other nodes to have issues being able to write things out.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
.png "Former Employee"){kind=icon}
