Select to view content in your preferred language

Error: ArcGIS License Manager must be upgraded to support this ArcGIS Pro version

853
6
03-21-2024 05:27 PM
Labels (1)
anbinh
by
Frequent Contributor

Hi Community,

 

We just have upgraded our License Manager to the latest version at 2023.0. We have ArcGIS Pro 2.9.5 to connect with this License Manager. According to the Esri documentation Supported software products—License Manager Guide | Documentation (arcgis.com), it should not have compatibility issue. 

 

However, the user encountered an issue saying "The ArcGIS License Manager must be upgraded to support this version of ArcGIS Pro. Please contact your organisation's License Administrator to ensure that the ArcGIS License Manager version is up to date."

 

Am I missing any setting here? Is there anything I can do to resolve this issue?

 

Regards,

AB

0 Kudos
6 Replies
MichaelVolz
Esteemed Contributor

Can users upgrade their own machines or is that locked down?

Are you sure the user did not try to install a newer version of Pro that needs a higher version License Manager?

0 Kudos
anbinh
by
Frequent Contributor

Hi Michael,

 

The license manager is already at the highest version. 

 

The ArcGIS Pro on the user side is currently locked to 2.9, so we cannot upgrade the ArcGIS Pro to the latest version. 

 

If as the documentation says, License Manager 2023.0 should still be able to support Pro 2.9. Just that the error message contradicts with the theoretical compatibility here.

0 Kudos
GISFunctionalGroup
Occasional Contributor

Hi there,

 

Did you get the solution for the issue. We are facing the same issue after upgrading the LM to 2024 version in the server machine. Users are locked with 2.9version in their machines.

Any suggestions /solutions are highly appreciated

Regards

GIS Functional Group

0 Kudos
anbinh
by
Frequent Contributor

Hi,

 

I can't remember exactly what solved the issue. In my case, the real trouble-maker was the flexnet licensing service running on the same server with conflicting ports. Hence, we needed to lock the port and suggested client to move flexnet licesing to another server. (It does not seem that flexnet port can be locked, so we had to lock ArcGIS licensing port.)

 

Thanks,

Anbin

GISFunctionalGroup
Occasional Contributor

Thanks for the feedback. Meanwhile we resolved the issue by assigning the fixed port number for ArcGIS licensing port on license server. 

0 Kudos