Question

License counter not functional after license update

WebLink

Updated December 2, 2016

asked on December 1, 2016 • Show version history

Greetings,

I have a performance counter setup to record Public Portal license usage and it was working properly until I updated the Weblink license. Weblink license was upgraded from 50 Public Public portal user to Unlimited x2 processor. The license is a test license so I am not sure if that will make a difference. Seems like after the license change any counter regarding licenses is not reported and just shows 0, so even Full Licenses just reports 0. Sessions on the other hand are reporting properly. Has anyone experienced this before, and if so were you able to resolve it?

Any ideas or thoughts is greatly appreciated. Thank you!

-BLP

License&Session Counter.JPG (80.77 KB)

| Download

Log of license count stopping.JPG (92.29 KB)

| Download

0 0

Answer

SELECTED ANSWER

replied on December 1, 2016

Hi Bich,

I'm not clear on what your screenshots are supposed to show. The first one looks like it's from an ad hoc perfmon trace that's running in real time. The second looks like a saved trace from 11/18 to 11/19.

In any case, can you confirm that making an ad hoc perfmon trace using the Public Portal Licenses counter works correctly with the updated license you have in place? If not, then please open a support case and we can investigate the matter further.

A generic test I performed of a server with unlimited public portal while using perfmon to track the public portal license usage worked fine.

Regards

0 0

replied on December 2, 2016

The first screenshot, shows the ad hoc with Public Portal Licenses and it's constantly 0. The second screenshot shot just shows how it flat lined to 0 after the license update. I will open a support case. Thanks!

0 0

Replies

You are not allowed to reply in this post.

You are not allowed to follow up in this post.

Question

Question

License counter not functional after license update

Answer

Replies

Sign in to reply to this post.