topic Re: Unable to log in to ArcGIS Pro: A core license could not be found in ArcGIS Pro Questions

Unable to log in to ArcGIS Pro: A core license could not be found

MwalimuKaranja — Tue, 18 Jun 2019 23:57:11 GMT

After a year of being able to freely log in to ArcGIS Pro, I am suddenly unable to log in. At first, I started getting the following error:

The number of licenses assigned to users exceeds the number of licences available in your organization

However, the organization I was logged in to definitely had available licenses and my account was assigned one and I had not taken it offline. The funny thing is, when I log out of that user profile on my laptop then I log into another user profile - I am actually able to log into ArcGIS pro with no problem. However, I absolutely need to be able to log into ArcGIS Pro on my user profile. Based on some advice from my IT department, I uninstalled ArcGIS Pro and deleted all references to Pro from AppData and the registry as advised here.(on assumption that a corrupt user profile was the problem).

This led to a different error:

Invalid URL

and then after a few more tries I got the error in the attachment. I am still able to log in to Pro when I use someone else's Window Profile. However, whenever I try using my profile (with the same AGOL credentials), I get this error:

A core license could not be found. Select another licensing option or contact your administrator to update your licenses.

Might anyone have any insight on how I can sort this out?

Re: Unable to log in to ArcGIS Pro: A core license could not be found

ThomasColson — Wed, 19 Jun 2019 11:29:34 GMT

I get this frequently. Unfortunately the only solution we have found is to delete the users local profile on that computer. There is some non-ESRI related corruption going on there.

Re: Unable to log in to ArcGIS Pro: A core license could not be found

AmnoyAm — Wed, 19 Jun 2019 17:43:13 GMT

Mwalimu,

Try the following:

1. Open you Windows Explorer and go to C:\Users\<local profile>\AppData\Local\ESRI_Licensing. Rename ESRI_Licensing to ESRI_Licensing_old.

2. Go to the Registry and navigate to HKEY_CURRENT_USER\Software and rename ESRI hive to ESRI_old.

Upon starting Pro, these files will be created with a default setting, basically resembling a fresh install. If you still experience the issue, it may be a non-Esri corruption in your profile as Thomas pointed out.

Re: Unable to log in to ArcGIS Pro: A core license could not be found

AmnoyAm — Wed, 19 Jun 2019 17:49:52 GMT

Thomas,

There was a bug with Pro 2.3 that was recently found and fixed in Pro 2.4.

Reproduction case:

Authorize ArcGIS Pro with either single or concurrent-use licensing.
Sign into AGOL.
Switch authorization mode to named user from AGOL.
Restart Pro as prompted.
Sign into AGOL using the same account as step 2. The error message will now be displayed.

The number of licenses assigned to users exceeds the number of licences available in your organization

If you get in this state, follow the suggestion I provided above. It should get you back to the default state. Again this issue was found in Pro 2.3 and fixed in Pro 2.4 which should be available very soon.

Re: Unable to log in to ArcGIS Pro: A core license could not be found

MwalimuKaranja — Sat, 22 Jun 2019 19:28:17 GMT

Dear Amnoy, apologies for taking long to get back to you. Your suggestion turned out to be the very answer I needed. Thanks again.

Re: Unable to log in to ArcGIS Pro: A core license could not be found

DSIProvince_Nord — Fri, 06 Dec 2019 05:06:27 GMT

Hi,

I have a similar issue, after updating ArcGIS Enterprise from 10.6.1 to 10.7.1 and thus License manager to 2019.0, I cannot connect directly ArcGIS Pro 2.4 to my portal to get a named user license.

I have the same error "A core license could not be found....."

The workaround I found is to connect to my AGOL account, then once AGPro is open, to switch to my portal url.

I put my named users and AGPro license on the portal by downloading the JSON file from MyEsri. I don't have GIS Professionnal user types, only Creators with AGPro additionnal licenses.

Trying to rename localUser data and registry key didn't work in my case. And the issue happened also on a newly installed computer.

I also tried to disable / enable my user's AGPro license through portal.

Any idea ?

Re: Unable to log in to ArcGIS Pro: A core license could not be found

MikeCannon — Fri, 05 Jun 2020 14:32:22 GMT

Very helpful. Thanks!!!

Re: Unable to log in to ArcGIS Pro: A core license could not be found

AmnoyAm — Fri, 05 Jun 2020 16:45:48 GMT

DSI,

Your issue is different from the initial post. In your situation, it appears you were able to log into the Enterprise Portal with a Pro license assigned account. However, it was not able to find a core named user license on the license manager. Here's what I would do:

1. Go to Portaladmin. Verify it's pointing to the correct license manager using the hostname, FQDN or IP Address.

2. Go to that license manager and verify you have named user licenses on that license manager.

3. If there is a firewall between the license manager and client machine where Pro was was installed, you need to configure the license manager to work through the firewall. This is likely your issue. Refer to the following documentation on how to do so: Configure ArcGIS License Manager to work through a firewall—License Manager Guide | Documentation

You should be able to use the Enterprise named user license once the firewall configuration is in place.

FYI. What you're currently doing is using a Pro assigned license account from AGOL to authorize Pro. Afterward you're connecting to your Enterprise Portal for data access. You're still using AGOL as the licensing portal. Once you configure it correctly you can use your Enterprise Portal as your license portal in addition to data portal.

Let me know if you have additional question on this.

Re: Unable to log in to ArcGIS Pro: A core license could not be found

DSIProvince_Nord — Mon, 08 Jun 2020 21:40:19 GMT

Hi,

Thank you for your advices.

1- In portaladmin everything look fine, I get the right hostname and port 27000

2- In the license manager I properly set up the named users

3- Regarding the firewall, there are no restrictions in communications between my license server and my client machine

Note that the license manager is not located on the portal server machine (this should not be a problem). I am trying to get a license for ArcGIS Pro 2.4.3.

Anyway we will try to update the license manager to 2020.0 instead of actual 2019.0 and AGPro to 2.5.

My main goal is indeed not to use AGOL but Enterprise Portal as a license portal.

Regards

Re: Unable to log in to ArcGIS Pro: A core license could not be found

geo_agronomo — Mon, 26 Jul 2021 21:25:20 GMT

Hello,

I have a similar problem I'm trying to log into ArcGIS pro and I get the message the number of licenses assigned to users exceeds the number of licenses available in your organization. Please contact your administrator to configure your organization's licenses. However, the ESRI licensing folder / file does not appear on my computer.

When I check the AGOL page it indicates that my license for arcgis pro advanced has expired, however it should remain valid until November of this year.

Any suggestion?

Greetings

Re: Unable to log in to ArcGIS Pro: A core license could not be found

JayantaPoddar — Tue, 27 Jul 2021 03:09:45 GMT

I think there has been recent changes in Organizational Account (AGOL) of ArcGIS for Personal Use, where ArcGIS Pro licensed through "GIS Professional Advanced" User-type, rather than the Add-On license of ArcGIS Pro. User Types: ArcGIS Online

Recently, I found (in my ArcGIS Online Organizational Account), "GIS Professional Advanced" user-type. Initially I had "Creator" User-type alongwith ArcGIS Pro add-on license (which had expired somehow). Once I unassigned the add-on license (having negative balance), I saw the following message.

Then, I assigned "GIS Professional Advanced" user-type to my named user.

Re: Unable to log in to ArcGIS Pro: A core license could not be found

geo_agronomo — Tue, 27 Jul 2021 16:52:43 GMT

Thanks, through this method I managed to solve the bug.