Hey folks, any advice you can give me on this?
My server is OK, no operational issues (that I can tell) with the solution.
Despite things appearing to work smoothly, I’m a little concerned. I have been seeing this message in besrelay.log a couple times per day since May 20.
licenseUpdater (5440) - LicenseUpdater error: License server error: Could not find license with serial #152189133
Ran the Server Admin Tool, no indication of any license change.
We’re not up for renewal for at least 3 more months and we’re not over allocated on the number of deployed clients vs the number of licenses we paid for.
What would cause this message? I know that BigFix logging can often write messages that appear more serious than they are, but since this is a newish and recurring message I feel like it needs a little research. I did check the forums and other sources, there were only two hits with the same message and there were no replies with advice or a resolution.
Have you checked that the Internet connection is not intermittent?
What you can do as test is try a manual update of the license from BigFix Console and see if the error is shown on the log.
Thanks! I ran through the manual update process and didn’t get any new error about the license.
We aren’t air-gapped - not that you asked but when you mentioned intermittent connectivity I thought it was important to bring up air gap too.
There are no issues with the network connectivity that I can tell, but this server is hosted at a colo and it is virtual, and I know it is on a shared physical host with lots of other virtual devices. It is possible that another device could interfere with this one.
I’ll investigate the network resources first and then open a PMR if there are no network resource issues and the log entry keeps appearing.
Right, AirGapped deployments will throw these errors when they go out and try to gather updates for your license. That is to be expected. So you logged into the TEM License Key Center, went to your license, downloaded it, and imported it via the Activate Masthead button in the BESAdmin tool, correct?
Actually no I didn’t complete the process. So I went back into the Key Center and it was totally weird.
There are two entries for my company name. One was blank, one had an account ID.
The one that was blank had 5 SKUs with the expected available quantity and 0 available quantity burned, which makes sense because there is no serial number associated, but doesn’t make sense because there are more SKUs here. The expiration date for support on those is 14 November of this year.
The entry with an account ID has one associated serial number. When I select that serial number it has only 3 associated SKUs with only one Lifecycle Management RVU burned. 0 CDs for Patch and 0 CDs for Security and Compliance are burned. As if our server has only a license for 1 processor and 0 clients. The expiration date on these is September of this year.
So I selected an allocated quantity for the RVUs on Lifecycle and the CD for Patch and Security and Compliance.
Hit the update serial number button.
Got an error.
Shrugged and went back and hit the button again and was able to generate a LicenseAuthorization.crt file.
Before I do anything with that .crt file, I want to call out that these problems all started on May 20th and the start date on our serial number is May 20th, but why that is I don’t know. The license was converted from trial last September and we haven’t had any changes to our licensing by request or otherwise through our reseller…as far as I know. This all seems rather odd.
Before I open a PMR which is hard for me because I’m not authorized by the IBM system to do that (which is another thread entirely), should I be getting with our account rep first to ask what is happening?