Latest Contributions by AmnoyAm

There's not much information to work with.  That said, I would consider the following: 1.  Verify that your license manager has both Pro and Desktop licenses.  Each application has its own set of licenses.  Pro licenses cannot work for Desktop and vice versa.   2.  Verify you have Pro pointing to the correct license manager.  Check your other system that is working and make sure the hostname for the license manager is identical.   3.  Check communication.  Make sure you can ping the license manager from the Pro machine.  Ping the name you provided in Pro when trying to consume the concurrent use license.   4.  Check the firewall.  If there is communication between the two systems and other machines can use the licenses from the same license manager, there must be something blocking the ports used.  Start with the Windows firewall on the machine.  Disable it if it's enabled.  If it has to be on, check our documentation on how to configure the license manager through a firewall.   ... View more

Just noticed your response to Cody.  So you have a Single Use Desktop license.  You successfully authorize Desktop Single Use.  You can use ArcMap, ArcCatalog, etc.  This is the classic client application.  It also means you have a Pro Named User license to go along with it.  You will need to create an ArcGIS Online account if have not done so already.  Start with the following document:  https://pro.arcgis.com/en/pro-app/latest/get-started/set-up-an-arcgis-online-organization.htm. You will essentially do the following: -create an AGOL account. -activate your subscription -assign a Pro Named User licenses to your account. -use that account to log into and start Pro. ... View more

Instead of running in circles, start with what license type you have.  When you mentioned authorization file, what is the extension of the file? ... View more

Very little information to go with here but we will see if we can narrow down the issue based on how it should work.  When you start Pro, configured for Pro Named User license via Enterprise, it will display the portal login dialogue.  The dialogue itself verifies Pro is able to make an https connection to the portal.  The user provides an  Enterprise account and password.  It then makes a call to the portal.  The portal verifies the account and password is valid and determines if it was assigned a Pro NU license.  If it does not, it will throw an error back to Pro indicating the account was not assigned a Pro NU license and to log in with an account that does.  Because you did not get this error likely means there is no communication issue up to this point.  Assuming the account used to log in was assigned a Pro NU license.  It send the message back to Pro indicating the Pro NU license it was assigned and a license manager server where to get the license.   Pro proceed to make a call to the license manager server through TCP/IP to retrieve the license.  If it can reach the license manager and retrieve the assigned Pro license, Pro will start.  If it cannot retrieve the license, it will usually display an error.  In some cases, it may just close and stop.  I believe this is where issue lies.  Either Pro cannot find the license manager or there is there is a network issue to the license manager.  Let's take a look at each.   License Manager-  Go to the URL address for the poral admin. Ex.  https://hostname/arcgis/portaladmin.  Click on the license link.  Verify the License Manager info.  It it displaying the license manger as a hostname, FQDN, IP address, etc?  Verify you can at least ping that name from the Pro machine.   Now that you've determined what the license manager server is, Pro must be able to communicate to the machine through two ports, 27000 and another port.  You must specify these ports in the service.txt file on the license manager machine.  Refer to the following link if you need more information, https://desktop.arcgis.com/en/license-manager/latest/configure-the-arcgis-license-manager-to-work-through-a-firewall.htm.  Let's assume you've tied down the ports to 27000 and 27002 for example.  You must open these two ports through any firewall between the two machines.  From my experience, a block on one of these ports is usually the issue.   Hope that helps.  Let me know how it goes.   ... View more

@RichardDaniels A new version of Pro will include bug fixes, new features, etc.  Sometimes we upgrade the Flexnet Licensing Service to stay up-to-date and to address vulnerabilities.  When doing so, we also need to update the service on the license manager to the same version or higher.  Because newer Flexnet Licensing Service will always work with the same version or lower, you should always update the license manager when available.  That said, a new version of the licensing service is not updated for each release.  So yes, newer version of Pro may work with an older version of the license manager but not always.  In the case of Pro 3.2 and license manager 2023.0, we updated the licensing service for Pro but later found a major bug with the same version of the licensing service on the license manager.  As a workaround, we tested and verified the new licensing service worked with the prior version in the license manager.  This is the same version found in LM 2022.1.  This is why you're able to use either version of the license manager for Pro 3.2.  Again, this is not always the case.   ... View more

If you did not get a response yet, just call them. https://www.esri.com/en-us/contact#c=us&t=5   ... View more

The option file can be used to reserve or exclude users from a particular license.  It does not switch license level as you described.  Whatever is set in the ArcGIS Administrator is what ArcMap/ArcCatalog is going to use unless there is an environment variable setting.  ArcMap/ArcCatalog will check to see if there is an environment variable set before checking the ArcGIS Administrator.  Refer to the document below on how to change a license level through the system's environment variable.  This is especially useful for ArcGIS Desktop in a terminal server such as Citrix.   https://desktop.arcgis.com/en/license-manager/10.4/using-the-license-manager-with-wts-critix.htm   ... View more

I assume your machine is in the same network as the Enterprise Portal and the license manager configured with the portal. Also I assume you're logging into the portal with the same account used to take the Pro NU licenses offline. There's a few things the may have occurred to prenvent Pro from returning the offline licenses. It's possible the status of the Pro licenses may be out of sync with the Enterprise Portal and/or the accompanying license manager. There is another possibility that portal was configured to point to the license manager using a FQDN where the hostname is inaccessible to the Pro machine. Either way, manual reset might be the only option here. I suggest you contact Esri Technical Support and have an analyst troubleshoot and walk you through the process if indeed a manual reset is necessary. ... View more

Assuming you're using a Named User license, have your portal administrator go to Organization>Licenses>View license activity.  Look for the log-in account.  It will show which Pro machine is using the account.  The admin can release the license for one of the existing systems so you can log in.   ... View more

Whether the license manager is used for Concurrent Use license or Named User license with ArcGIS Enterprise, it's a good idea to upgrade the license manager to the latest version.  Later version of ArcGIS Pro may require a later version of the license manager.  The latest license manager will always work with earlier version of Pro.   ... View more

In your situation, Pro makes two separate calls when starting.  Upon startup, it communicates to the portal through https.  You're know when you you get the login prompt to your portal.  Once you log in with a valid Pro licensed user, the portal will verify the user and determine what license(s) are assigned to the user.  It also determine where to get the license from.  Pro then makes another call to the designated license manager using the TCP/IP protocol.  This is likely where the failure occurs.  If you refer back to the article mentioned above by Scott_Tansley, https://desktop.arcgis.com/en/license-manager/latest/configure-the-arcgis-license-manager-to-work-through-a-firewall.htm.  It walks you through the process to open your specific ports through your firewall.  Keep in mind there may be more than one firewalls between Pro and the license manager depending on your location.  As for the ports, the license manager uses two ports, 27000 for the lmgrd.exe daemon and any open port for the arcgis.exe daemon.  You set this up in the service.txt file as described in the article.  Then open those two ports through the firewall.   When troubleshooting, just verify communication to the license manager through those two ports are possible.   ... View more

It sounds like you authorize an ArcGIS Pro license.  Go to the Support Operations folder in the ArcGIS Administrator.  Click on the Deauthorize... button to start the Software Authorization wizard.  Just click next the rest of the way.   You will eventually get to the Deauthorization Options dialogue where it will list all the licenses you have authorized on the machine.  It will likely list feature names with "Pro" in them.  These are Pro licenses.  Cancel the wizard and leave the licenses authorized on the machine.   Instead, download ArcGIS Pro if you can.  If you cannot, contact our Technical Support department.  An analyst can help you through the process.  After installing ArcGIS Pro, it should be ready for use since you've already authorized the license.   FYI:  you have installed ArcGIS Desktop (ArcMap, ArcCatalog, etc).  This is different from ArcGIS Pro, a completely separate application.   ... View more