Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Not applicable

Error PGO: Failed to open

Hi,

We are having QVS clustering and maintaing root and mounted folder in common shared server.

we are getting an error in event log "Error PGO: Failed to open \\xvavvvv002\Root\IniData.pgo. Error: 11. Time: 268435456 ms" very frequently.

Have anyone found this error and what may be reason for this error.

Thanks in advance.

19 Replies

Error PGO: Failed to open

On the first glance this error indicated that the QlikView Server is unable to reach the share.

In detail the "Time" parameter states the amount of time in Milliseconds the operation(s) took before aborting for the error related to the error code. If this number is high (like in this case) and the error code is either 11 or 12, we can draw the conclusion that QVS made as many retries as it could fit within the fixed timeout of 30 seconds.

Please verify that you are not experiencing network issues during the time when the problem occurs, but be aware that this could have a number of causes. Submit a Support ticket through the right channels if necessary, just make sure you include all necessary details like QVS version details, log files and also let us know what network storage solution you are using (NAS, SAN, whether they are windows based or not, etc).

/Sonja

QT Support

Sonja Bauernfeind
Senior Technical Support Engineer and Knowledge Centered Support Gremlin


To help users find verified answers, please don't forget to mark a correct resolution or answer to your problem or question as correct.
Not applicable

Error PGO: Failed to open

Hi Arunesh,

We are having the same issue. Can you please share your experience and your solution.

We opened a ticket and we don't get any staright answer ...

Thanks

Priya

Not applicable

Error PGO: Failed to open

Hi Priya,

We have contacted the Qlitech for this issue and they are going to give some new patch in order to fix the issue.

Let us wait for that patch.

Aruenesh

Not applicable

Error PGO: Failed to open

All,  this was a bug in earlier versions of 9 and 10, the issue is fixed in SR3 of version 10 that was released today. Not sure if we have a SR out fixing the issue in version 9, please let me know if you need a fix for it in version 9 as well and I will see if I can find a patch for you on Monday.

Regards Katarina

Not applicable

Error PGO: Failed to open

Hi Katarina,

Thanks for reply.. We are having another issue  QVS Server restarts sporadically because .meta file cannot be found.Any idea if this is a bug and has a fix...

Thanks

Priya

Not applicable

Re: Error PGO: Failed to open

Unfortunately not, if the upgrade to SR3 doesn't solve the .meta issue as well, please report it to qlikview support at support@qlik.com<mailto:support@qlik.com> and attach the qlikview server event log file, this will help the support to find the problem you have.

Kind Regards

Katarina

Not applicable

Error PGO: Failed to open

We installed SR3 last weekend and we are still seeing a variation of this error in the Event log.  In our case, it is usually IniData.pgo or CalData.pgo, though occasionally ServerCounters.pgo is also cited.  This problem is not fixed in SR3 for us.

We are running QV10 SR3 on two dedicated test servers running Windows 2003 Server on VMWare ESX.

Interestingly, this problem, and several other problems where .qvw.log files can't be written to, and .Meta files are reported as "missing" when they are in fact, present, does not occur when we disable the second QVS service, so that the cluster has only a single QVS service running.

Not applicable

Error PGO: Failed to open

Could you please report this to QlikView support at support@qlik.com or via the customer portal if you have access to it!

Kind regards

Katarina

Not applicable

Error PGO: Failed to open

We have the same problem, same event in the windows log (Application log/eventID 131).

We are using QlikView v9 SR7, which is the latest, with IIS and the files are on a share.

At the same time we have had access problems to the qvw-file. But we cannot be sure it has to do with this issue.

Restart seemed at first to solve the problem.

But since not everyone got access problems during the time the event showed, it cannot be a certainty.

I will report this to Qlikview support.

Community Browser