Archive | March 2014

Convert .pgo files to .xml

Qlikview Server files .pgo can give us valuable information. PGO (Persistent Group Object) files are created by Qlikview Server and stored or placed in our root folder. The files are locked while the Qlikivew Server is running. The different pgo files contain information about borrowed CALs, CALs in use, Server settings and ticket data.
These files can’t be accessed without first converting them to .xml files.

Creating a .xml copy of a .pgo file

1) Stop the Qlikview Server service from the.
2) Add PgoAsXmlAlso=1 right under [Settings 7] in the Setting.ini file located in %ProgramData%\QlikTech\QlikViewServer. The Setting.ini file should look like this:

[Settings 7]
PgoAsXmlAlso=1
DocumentDirectory= …
….
….

3) Restart the Qlikview Server service
4) Go to the root folder where the .pgo files are. You will then see the .xml files.

I hope you find this useful.

JV

Tracking lost licences

Keeping track of licences in a big environment can be a bit of a hassle.

In case you didn’t know, we can literally loose licences if we don’t make sure to follow all the necessary steps before deleting or updating a file name.

But, how do we know we are missing licences?

The answer to this question, it’s very simple and easy to spot.

If you delete or change a file name before removing any licences assigned to this file, then those licences will be lost and you won’t be able to use them in any other application.

For example, let’s suppose we have a file “Qlikview Document.qvw” with 1 document CAL assigned to it. If we now go ahead and delete this file (without removing the licence), the licence will be lost and the file will show up in QMC in capital letters.

Image

Whenever we see a file like this, we should know we need to take action.

The first thing would be to restore the file we just deleted. If someone else deleted the file, it’s probably that Read More…