I've issue license initialization in ArcGIS Pro 2.7. I can run python script manually via command line and batch file but encountered with following run time error with scheduled task in Windows server 2019. File "C:\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 14, in import arcgisscripting File "C:\arcgis\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\arcgisscripting\__init__.py", line 128, in from ._arcgisscripting import * RuntimeError: The Product License has not been initialized. Any ideas or solutions? Thanks in advance, Chintamani

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro Runtime Error: the product license has not been initialized

chintakandel

I've issue license initialization in ArcGIS Pro 2.7. I can run python script manually via command line and batch file but encountered with following run time error with scheduled task in Windows server 2019.

File "C:\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 14, in <module>
import arcgisscripting
File "C:\arcgis\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\arcgisscripting\__init__.py", line 128, in <module>
from ._arcgisscripting import *
RuntimeError: The Product License has not been initialized.

Any ideas or solutions?

Thanks in advance,

Chintamani

Najděte více příspěvků označených jako

Desktop

Accepted answers

Robert LeClair

What type of ArcGIS Pro license are you using? Named User, Concurrent or Single Use? I found one case with this messaging where the customer changed the ArcGIS Pro license from Named User to Single Use license - this corrected the error message. The error could have been thrown if the account running the script has never opened ArcGIS Pro, thus no roaming profile exists. The analyst and customer tested the workflow using a Single Use license and it worked properly. Hope this helps!

All comments

jordan.carmona@piercecountywa.gov_piercecowa

This did not keep it alive.

jordan.carmona@piercecountywa.gov_piercecowa

I'm testing this now; will report back in 14 days.

MasaoMatsuokaDev

Checking the option "Authorize ArcGIS Pro to work offline without Internet connection" in ArcGIS Pro Licensing worked for me.

Bryan_krg

I'm not sure if this is how the licensing works but it seems you can check if a license file is present for the user signed into ArcGIS Pro.
If you look in hidden the folder C:\Users\<your username>\AppData\Local\ESRI_Licensing there is a file called lss.dat. If this file is present then you will be licensed for arcpy. If it's not there you will not be. The log file in logs tells you when you have created the lss.dat file and what you did to create it.

As mentioned above by Shovon there a few criteria that you could meet to create this file. Unfortunately, if your user is running a scheduled task and isn't logged in the options to be signed in or have ArcGIS Pro open are out, which leaves the bottom two. Unfortunately, as erinheinrich mentioned concurrent use license doesn't work as expected either so that leaves 'Authorising ArcGIS Pro to work offline without an internet connection'

This will tie up one of your licenses purely for automated tasks which does seem a little crazy. If ESRI could create a python module to allow us get license in the script similar to the functions to checkout extensions it would be greatly appreciated. For example:

if arcpy.CheckProduct("ArcInfo") != "Available":
   try:
      arcpy.SignInToPortal("https://webadaptorhost.domain.com/webadaptorname", 'username', 'password')
      arcpy.CheckOutProduct("ArcInfo")
   else:
     # raise a custom exception
     raise LicenseError

# Do your arcpy scripting things....

jschuckert

@feralcatcolonist if you are say using a service account which is what runs all your automation but is rarely logged in with, does this truly keep the ArcGIS Pro login tokens active (or renewed)? A recent ESRI Tech support case we flushed out that their (ESRI's) recommended batch file to launch Pro only works from Task Scheduler if "Run only when user is logged on" is checked. If you use the alternative "Run whether user is logged on or not", it still runs error free however does not make the token refresh calls thus keeping the login active for another 14 days.

Robert LeClair

Hi @VithushanLogan - unfortunately this question is outside of my knowledge base - @JeffBigos - are you aware of how to accomplish this workflow?

VithushanLogan

Hi @Robert_LeClair, I was working on the automation project using ArcGIS Pro and Lambda. The simple idea of the workflow lambda triggers the Ec2 instance to run some Python scripts related to the Arcpy module. In this process when lambda triggers the Python script in the Ec2 instance, throws some errors (Error in JSON format)

RuntimeError: The Product License has not been initialized.', 'StandardErrorUrl': '', 'CloudWatchOutputConfig': {'CloudWatchLogGroupName': '', 'CloudWatchOutputEnabled': False},

Can I know how to resolve it?

erinheinrich

Option 4 does not work for me, I have use single use licence, concurrent just not working as expected.

Shovon

Please follow the instructions

Python in ArcGIS Pro—ArcGIS Pro | Documentation

Authorize Python outside the application
If you run Python scripts that use ArcGIS Pro functionality outside of the ArcGIS Pro application, such as a Python IDE, from a command prompt, or running scripts through scheduled tasks, one of the following conditions must be met:

1.Sign me in automatically is checked when signing in to ArcGIS Pro.
2.ArcGIS Pro is currently open.
3.ArcGIS Pro has been authorized to work offline.
4.ArcGIS Pro is configured with a Concurrent Use license and at least one license is available on the ArcGIS License Manager.

feralcatcolonist

I've used this process in the past to trick ArcGIS Pro into thinking that I've manually logged in to keep resetting the counter that requires a manual sign-in process.

import os
import time

#Assign the location on the machine, usually here
ArcGIS_Pro_filepath = r"C:\Program Files\ArcGIS\Pro\bin\ArcGISPro.exe"
#Use os.startfile(), this will launch ArcPro
os.startfile(ArcGIS_Pro_filepath)
#Use time.sleep() to wait 60 seconds, enough time for ArcPro to open properly
time.sleep(60)
#Use os.system() to forcefully quit named process, ArcGISPro.exe
#https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/taskkill
os.system("taskkill /f /im ArcGISPro.exe")
#You can use the following output to determine if the command was successful
#SUCCESS: The process "ArcGISPro.exe with PID 4408 has been terminated

https://gist.github.com/FeralCatColonist/9cae407c7200fa6a45f922c019e397c3

Jen_Zumbado-Hannibal

This worked great! Thanks.

JoseSanchez

Hello everyone,

I had the same error message in our development server, and for me the solution was simple. I just opened ArcGIS Pro on the server and it behaved like I was opening it for the first time, it asked to connect to AGOL to validate the license. Then I tested again the script and the line "import arcpy" did not return any error message.

Thanks

ZachBodenner

I'm also having some trouble with this exact issue. I can run python scripts just fine, but not automate them with system scheduler. Currently we operate mostly out of Enterprise (ie. no spare licenses in AGOL) using a license manager with concurrent licenses. However, this was a recent change - the user I'm attempting to run the scripts with does have a roaming Pro file. I've tried to set the license to approve for offline use, but nothing doing. Anyone with a similar setup have success?

Anonymous User

I find the following helpful:

Single use license
Use the task scheduler in Pro
Setup everything from installing Pro to creating a project to adding the script to the project toolbox and scheduling the task as a user who is an administrator on the machine.
A local admin user can work well but only if you don't need to get to network resources with your script.
A domain user who is part of the machine administrator group is the best. It has full rights on the machine and can interact with network resources.
Once your task is set to run from the script tool in your project via the Pro task scheduler, don't monkey with it in the Windows task scheduler (WTS) except:
You can set it to run whether or not logged in.
You can run with highest privileges but don't do it just to do it. Do it only if it the script won't work without it.

Overall, running scripts against Pro conda is about half as stable as python 2.7 unless you get the recipe nailed. This has always been an issue with Pro and I am sure ESRI would rather sell us Notebook Server advanced which is very cool but $$$$$.

erinheinrich

I have a concurrent licence and this was the "simple" solution that worked for me, informed by everyone's responses above:

1) login to ArcPro with my MyESRI credentials, which are linked to my organisation.

2) Borrow licence, that is check "Authorize ArcGIS Pro to work offline"

Viola, simple as that, no more error... until licence expired and I then just re-borrowed 🙂

RobertStevens

This procedure did nothing.

I ssh to the client windows 10 box, try to run python with arcpy
and still get the same message after having spent 30 mins of my time
going throught the involved procedure of converting to a single
user license.

Cristian_Galindo

Hallo Darina,

To be hones the error was solved by the IT guy that manage the corporate Firewall. I can tell you that a rule was created to allow communication with www.arcgis.com.

You can check a detailed document for your whitelist here: https://downloads.esri.com/resources/enterprisegis/AGOL_Domain_Requirements.pdf

DarinaTchountcheva

Cristian,

Can you provide more details on what Firewall rules?

I am having the same problem, and I suspect that the Firewall might be the issue, but not sure how to figure it out.

Thank you!

LauraTateosian

Thank you to everyone who replied. I got it working. For the purposes of this description, I will say the user that runs the process is "batch_runner". Here's what I did:

1) Log in to the server machine as batch_runner. (This was a bottleneck for a while, but had nothing to do with ArcGIS) and download a single user license file executable.

2) Run the single user license file and when prompted, oog in to ArcGIS Pro as a named user with my own account credentials.

3) Switch ArcGIS Pro to a single user license (in that log in session)

a) Select "Configure your licensing options".

b) Change the License Type to "Single Use License".

c) Click Authorize and follow the steps in the Software Authorization Wizard. Click Ok.

d) Restart ArcGIS Pro.

4) Et voila! It worked. 🙂

I believe this created a profile under batch_runner, because after this, it could run the arcpy processes.

I am still trying to find out what I'll need to renew the license which will expire in July. But at least it's working for the moment. Thank you for all the responses and helpful information!

Cristian_Galindo

I had an issue with the company Firewall rules 😞

Cristian_Galindo

I am suffering from the same behavior:

File ".\Arcpy\PublishService.py", line 9, in <module>
    import arcpy
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\__init__.py", line 88, in <module>
    from arcpy.geoprocessing import gp
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\__init__.py", line 14, in <module>
    from ._base import *
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 14, in <module>
    import arcgisscripting
  File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\arcgisscripting\__init__.py", line 128, in <module>
    from ._arcgisscripting import *
RuntimeError: The Product License has not been initialized.

the characteristics of my environment:

ArcGIS pro 2.9.3

ArcGIS Pro Named User License

The processes were running with out issue, but since yesterday it start with this issue, as it can be seen in the code above, the error is triggered when the script reach the import arcpy command.

An special consideration: I have a set of 5-6 scripts that runs over 4 geodatabases, all of them are orchestrated to be run sequentially by a service (the service runs under the same credentials as the ArcGIS Pro application was configured and executed - you know...the profile cookie mentioned above), but not all the scripts fail, and the failing ones are not always the same.

I even have a script made in PowerShell that uses the ArcGIS.Core.Hosting.dll, it is failing too when the initialization is called.

LauraTateosian

Hi Chintakandel,

I can run as administrator. Can you tell me which system tools are involved?

LauraTateosian

Hi, Thank you for posting this information. I tried to follow this procedure, but perhaps when you said "Task Manager", you meant "Task Scheduler"? The Task Manager doesn't have an Action option, but the Scheduler does. It looks like this solution will not work for me, as I'm not triggering the script through a scheduled task.

chintakandel

I think you have to run Task Manager as administrator or service account to access system tools. You may require to run ArcGIS Pro as admin.

LauraTateosian

Though related, my target functionality is a bit different from what is posted here. I'm not triggering the run from a Task Manager. It's triggered by PHP code. I can't figure out what the equivalent of setting the task manager's privileges would be.

LauraTateosian

Thanks, our IT is setting up such an account. I hope it works. I'll post again either way.

chintakandel

We’re using service account as admin account. Ignore service account if you are using admin account for your computer.

LauraTateosian

Hi RickMomsen1,

I'm facing a similar issue and your setup sounds similar to ours. It's a server machine that needs to trigger some Python scripts.

But I'm not sure what you mean by "service account". Does that require a special kind of license?

Anonymous User

Our configuration is different than any other helpful threads - here is our config and solution.

Config: We have a dedicated scripting server (WS 2016); default Pro 2.9.1 install; custom cloned environment in "C:\Python3x\...\our_clone"; scripts on local and network drives; tasks run as a domain\service account that we cannot use as machine login; concurrent license

Solution:

Task Manager:
- General: Run as <domain\service acct>; Whether logged in or not; Highest Privileges (may not be necessary)
- Action:
  - Program: C:\Python3x\...\our_clone\python.exe
  - Argument: \\path\\to\\script.py (or c:\path\to\script.py)
- <everything else default>
ArcPro
- Right-click application --> more --> run as different user
- (log in with service account credentials)
- In the sign-in window, click the configure license settings in the lower left.
  - 2nd time logging in opens Pro - go to Settings\Licensing
- Change license type to Concurrent and set your license manager
- Do NOT "Authorize Pro to work offline"

Our biggest problem was initializing the Arc license, which was due to the service account and Pro relationship. Several threads mention logging in as the Scheduled Task user, but that was not possible for us. I often Run As Admin, but had forgotten about the option to log into the application as the service account.

Other Attempts:

Setting Pro to work offline (I'm very glad this didn't fix our issue because Pro checks the license back in automatically after X period of time - wouldn't work well in our system of automation)
Task manager\Action: "C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\propy"
- command not recognized.
Task manager\Action: "C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\propy.bat"
- successfully recognizes cloned env, but still failed on import arcpy
- I vaguely recall this command resolving to Pro's env once, so there may be some activation required.
- as mentioned above, pointing the task directly to the clone's python.exe works and is very clear
Task Manager\Action "Start in" had no affect regardless what path I entered
using batch files with conda activation and python execution

Tom_Laue

I have not had a chance to implement this yet.

AlexisHandelman

Have you implemented these steps and have they worked? We are experiencing the same thing as you. We cannot figure out what is causing Pro to log out. We were trying to avoid converting to single-use license though.

Tom_Laue

I’ve been encountering similar issues. I have found that ArcGIS Pro (which we license through AGOL) automatically logs itself out of every 90 days. I have many Arcpy scripts running via Task Scheduler 24/7.

Also, periodically (usually once a day at a specific time) scripts will fail saying “RuntimeError: The Product License has not been initialized.” No idea what is causing this error as this script runs all day every 30 mins and never gets this error the rest of the day.

ESRI Tech Support sent me this suggestion which we have yet to implement…

-------------------------------------------

We’ve done a bit of digging into our documentation and might have a solution for you. The bad news is, it doesn’t look like there’s a good way to handle the Pro license refresh through Python. The good news is, there is a promising option for handling it in your environment directly. Please see below for a configuration step-by-step that should solve your logout issue:

Step 1: Environmental settings

Convert your Named license to a Single Use license for this instance of Pro (if you haven’t already). See https://pro.arcgis.com/en/pro-app/latest/get-started/convert-named-user-licenses-to-single-use.htm for more details on how to configure this. This should allow offline access for Pro.
Make sure “Sign me in automatically” remains checked when you log into Pro on this machine. Just in case.

Step 2: Caching local user (src: https://community.esri.com/t5/python-questions/arcpy-fails-to-import-when-not-logged-into-host-machine/td-p/553399)

Log into the server that will host the script using the username that will be running the script (i.e. the “owner” in task scheduler).
Once logged in, open ArcGIS Pro (this will create an esri profile cookie in your AppData folder, that ArcGIS will be able to use to recognize the user).
Make sure your license and configurations are set according to step 1 and close Pro.

Step 3: Just in case… (src: https://community.esri.com/t5/arcgis-pro-questions/running-a-scheduled-task-on-a-server-machine/m-p/94134)

If the issue persists after running through steps 1 and 2, it means that your Pro configuration requires the application to be open while running scripts against its library, for whatever reason. If this is the case, and only after completing steps 1 and 2, we recommend you include a task before the script in your task scheduler that will open ArcGIS Pro, to remove any weird library locks. This is an edge case but does appear to affect some users, so I wanted to include it in the outline.

NathanHeickLACSD

Yes, I had a similar issue and just wanted to add my experience to the list. I had a scheduled task that had been working for a while with no problems. All of a sudden, I stopped getting email messages from the script. The script wasn't capturing all exceptions in the code, just those in the main block of business logic. So, it was not catching this error, which was causing the Scheduled Task to fail with code 2147942401. Like you, I just opened ArcGIS Pro and signed into a named user account and the script started working.

Could you explain Robert what might have changed? I haven't logged into ArcGIS Pro on that machine in a while, but it was working a few months ago.

chintakandel

Hi Robert,

Thank you for your suggestion. Worked after running Pro with the account that is used to schedule task to run script.

Thanks,

Chintamani

Robert LeClair

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.