Hi All,
We upgraded to version 12.3.1 a few months ago, not sure if related, but have just started getting this message when trying to open AMS.
"licencing is unable to connect to licence server"
We have been using AMS since the upgrade but now cannot open it. Has anyone seen this issue?
Regards
Tony
Hi, Tony.
I've seen this behavior on 90% of the AMS 12.0 and 12.5 systems co-deployed with DeltaV here in New England. It doesn't seem to be tied to the DeltaV version, as I performed an AMS-only upgrade to 12.5 on a DeltaV 11.3.1 system, and the same issue was observed there a day or two after installation. I've found a number of different root causes that lead to similar error messages, but the remediation path can be different, depending on the logged errors.
First thing you can do is check your Windows Event Logs, looking for BssProgLog / BssProgLogU source events. Check the context of the message and look to see if the logs state that the AmsServiceUser account password has expired. If you're seeing that, all you have to do is open DeltaV User Manager, edit the AmsServiceUser account, and check the "Password never expires" box. If you're in a domain environment, you can do this from AD Users & Computers. If in a workgroup, you'll need to do this on every machine on which AMS is installed.
If you don't see those log entries, you might look towards manually running AmsRegall from the AMS\bin directory and rebooting your ServerPlus / ClientSC. That seems to be a temporary workaround. If you have Foundation/Guardian Support, I'd also recommend logging this with the GSC (make sure it gets assigned to the AO group).
Best of luck!
In reply to Ray Emerson:
Tony,
If you changed your computer during the upgrade you will need to get a new license key. I just had to do this during one of my upgrades, the AMS key is tied to your hard drive SN (if I remember correctly). There was no cost for this but I had to call in and give them the new info and they gave me my new AMS license key.
Tony, Ray pointed out some good suggestions. As he mentioned, there are different situation that causes this to happen. From my experience, this happen when the AMS services did not shutdown properly or someone or application stop one of AMS services to the AMS server plus.
I would first try to use the AMS "Terminate Server" and properly shutdown all of AMS stations. Before you restart AMS client, make sure you restart AMS Server Plus first by manually launching the AMS app from the start menu then now go to AMS Client station and manually launch the app as well.
What this will do is to get all the AMS services to startup properly and get all the connection to the client to the AMS Server Plus establish.
Regards,
Tinh
Thanks very much everyone for your replys. The problem we found was with the password expiry.
In reply to Tony_M:
In reply to Adrian_:
In reply to andisaiman:
In reply to David Flamenco:
In reply to Tinh Phan: