Latest Contributions by AmnoyAm

On the user's machine, start Pro and go to the Licensing tab.  What licensing type is being used to start Pro,  Concurrent Use, Single Use or Named User.  If Named User,  it should list the authorizing portal towards the bottom of the window.  If AGOL, it should point to www.arcgis.com.  If so, go to the Portals tab and verify the account used to log into Pro.   Now go to AGOL, www.arcgis.com and log in with one of the admin account.  Determine if that account used is a member in the org.  If is possible the user has a personal account belonging to another org.  You can have the user go to www.arcgis.com on a browser and log in with the same account.  Verify the organization ID.  This may explain why you cannot see it in your own organization.   ... View more

If you did a per user install of ArcGIS Pro, it installed to the local profile and does not install the flexnet licensing service that is necessary to authorize Single Use license.   If you did a per machine install, it should install the service.  However, I've seen a case or two every once in a blue moon where the licensing service did not get installed.   Either way, go to the Pro installation directory, per machine install is at C:\Program Files\ArcGIS\Pro\Resources\ArcGIS Licensing Service.  Run ArcGISLS.msi to install the licensing service.   Once installed and running, go back to the Configure Licensing dialogue.  There will be an option to authorize, deauthorize, etc.   ... View more

Named User via AGOL or ArcGIS Enterprise the preferred option moving forward.  For machines that is completely off the network, the Single Use option is still available.   ... View more

@GrantSmith122 I assume you're referring to the following section from the documentation I mentioned above: SERVER this_host ANY 27004 VENDOR ARCGIS PORT=5152 USE_SERVER This is just an example. Here, we have the lmgrd.exe vendor daemon or process using port 27004 and the arcgis.exe vendor daemon using port 5152. Again these are examples. For the lmgrd.exe daemon, we prefer you use ports 27000-27009 because they are specifically reserved this purpose. The arcgis.exe can be any port that hasn't been used. If you're not sure, talk to your network or system admin. Otherwise, feel free to use any port from 27000-27009. Hope that helps. .   ... View more

Keep in mind these are information provided to ArcGIS Pro from the portal's response.  It's telling Pro to go to that hostname for the license manger and use this port.  That is all that is necessary here.  Pro will then make a call to the license manager server by the name you provided, whether its the hostname, FQDN, etc.  Make sure this name is accessible from the Pro machine.  Also as part of the license manager configuration, you had to specify an open port for the arcgis.exe vendor daemon.  Pro will communicate to the license manager using ports 27000 for lmgrd.exe and the "open port" you configured.  These ports must be open between the Pro machine and license manager server.  Portal is no longer needed at this point.   Perhaps an overkill but hope that clarifies any confusion.   ... View more

Sounds like the Pro machine is having a problem connecting to the license manager through the specified ports.  Refer to the following document on how to configure the ArcGIS License Manager with a firewall.  You need to open ports 27000 and a predefined port for the ArcGIS vendor daemon.  Both ports must be open.  If both ports are already open, check the license manager name in the Enterprise portal.  Verify its using a hostname that is recognized by the client machines.  Below is the link to the firewall document to get started: https://desktop.arcgis.com/en/license-manager/latest/configure-the-arcgis-license-manager-to-work-through-a-firewall.htm   ... View more

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