QV User manager 11 - list works, but remove doesn't

[#1]

Hi,

I've installed QV User manager 11 on our customer's test machine and it works fine. I can trigger a batch file to list the current licenses in use and I can run a batch to remove unused cals.

Now we've migrated the same to production and the removal of cals won't work. Listing does. Strange.

The csv output file contains this error message:

System.NullReferenceException: Object reference not set to an instance of an object.

   at PIX.CalInfo.WriteXml(XmlWriter w)

   at Wrappers.QVSWrapper.CallFunction(String methodName, String iStartElement, String iStartAttribute, IXmlSerializable arguments, IXmlSerializable outpar, String& message, Byte[][] attachments)

   at Wrappers.QVSWrapper.SetCalInfo(CalInfo i_CalInfo)

   at QMSBackendCore.Communication.QlikViewServer.SetCalInfo(QlikViewServerResource qvsResource, CalInfo calInfo)

   at QMSBackendCore.Service.ServiceImpl.SaveCALConfiguration(CALConfiguration calConfiguration)

On the same machine an implementation of the EDX stuff is running and working, so the basic functionality should be there. We also checked the following:

• Functional user executing the task in MMC is member of ‘QV Management Api’ group
• Executing the batch file from command line under Windows with the user results in the same - listing works
• QV services on the server are running under functional user
• SSL certificate: name and location from the config file matches the installed certificate
• Functional user has access rights to the cert.
• Event view shows error when writing the XML structure:
  • System.NullReferenceException: Object reference not set to an instance of an object.

   at PIX.CalInfo.WriteXml(XmlWriter w)

   at Wrappers.QVSWrapper.CallFunction(String methodName, String iStartElement, String iStartAttribute, IXmlSerializable arguments, IXmlSerializable outpar, String& message, Byte[][] attachments)

   at Wrappers.QVSWrapper.SetCalInfo(CalInfo i_CalInfo)

   at QMSBackendCore.Communication.QlikViewServer.SetCalInfo(QlikViewServerResource qvsResource, CalInfo calInfo)

   at QMSBackendCore.Service.ServiceImpl.SaveCALConfiguration(CALConfiguration calConfiguration)

• Restarted MMC service, without effect
• Log of the Management service logs the exception, without further information

Anybody an idea how to solve this?

Thanks a lot in advance,

Jens

[#2]

Anyone familiar with this?

[simenkg]

I have no experience removing cals using batch jobs, but a common annoyance when deleting CALs the normal way is that you can have CALs allocated to .qvw-files that are already deleted. I imagine that the CALs then exists in an internal list, but perhaps deleting the CAL needs to refer to some index in a list that should hold file paths. If this index no longer exists then a Null Reference seems logical enough.

So my suggestion is that you find out if some files have been deleted from AccessPoint on the production environment where CALs where allocated. If so create empty .qvw's with the same file name and use QMC to remove the allocated licenses before deleting the file again.

[Anonymous]

This rings a bell regarding dot net versions.

[#5]

Ok, I haven't been in the project from the beginning. Will need to check with a colleague who is on vacation this week.

Thanks.

[#6]

I checked the dotnet installations (runtime envs) on both machines, both are 4.0.30319. Or do you mean something else?

Thanks.

[Bill_Britt]

Have you create the correct groups on the local machine and put the users that are going to run the .bat files in the groups?

Bill

[#8]

Yes, we checked that.

[#9]

I'm not sure how to find out if there were documents deleted that might still have license allocations. Is there a way?

Would it help to delete the PGO files to clear a probable issue? How?

Thanks.

[#10 · Accepted solution]

Finally solved this issue and in case anyone is running into the same trap, here's the solution that might help in similar cases:

From older "tries" of configuring the system, files called "BorrowedCalData.pgo" existed. They harmed the successful execution of the user manager. When deleted, the removal of licenses worked properly.

Jens