License server administrator 2021

[DarylHochhalter]

We have Enterprise 7.0 federated portal with SAML logins with a redirected URL running on Windows Server 2019. I log into ArcGIS Pro with my domain acct. which is setup as an admin in Portal. Since upgrading the License server administrator I have to log into the Server machine and manually re-read licenses each morning before I can open Pro. Any helpful ideas appreciated.

I have noticed this in the debug log for License Server Admin:

1:30:38 (ARCGIS) Wrong hostid on SERVER line for license file:

1:30:38 (ARCGIS) C:\Program Files\ArcGIS\LicenseManager\bin\service.txt

1:30:38 (ARCGIS) SERVER line says VM_UUID=E0C007B4-AE71-489E-ABE9-C6350F48EE93, hostid is VM_UUID=E0C007B4-AE71-489E-ABE9-C6350F48EE93

1:30:38 (ARCGIS) Invalid hostid on SERVER line

1:30:38 (ARCGIS) Disabling 1 license from feature ACT(0E33 13F7 49BF 4183 )

1:30:38 (ARCGIS) Disabling 3 licenses from feature desktopAdvN(0686 4471 3FA4 0688 )

1:30:38 (ARCGIS) Disabling 3 licenses from feature publisherN(0825 F8CA 41CD 73B4 )

[DarylHochhalter]

I can add this bit of info, in our case we are using a redirected URL for our portal and server web adaptors. The enterprise installation (portal,server,etc) exist on the same virtual machine as the License server.

[BuffaloCoWI]

Almost two years later and I had the same problem. Everything worked fine until the license file expired for named users authenticating through our Portal. I went to My Esri and created new license files. Since our ArcGIS Enterprise servers are on VMs, I assumed the Cloud Instance ID would be more appropriate than a MAC address, which is supposed to correspond to a physical NIC. Obviously not.

It worked fine at first, but the next day, and each day thereafter, users would try to start ArcGIS Pro in the morning and get an error. The temporary solution was opening License Server Administrator on the server and re-reading the licenses.

Eventually I found this solution, generated new licenses with the MAC address instead, and now it works properly. The licensing tools on My ESRI should have a warning against using the Cloud Instance ID.