Is there any way that a 'named user' Pro license that is being consumed by a service account has to be released so that the same account can "check out" this license on another machine? I know there is no real check in/out for named users. But I'm running into an issue where I want to have the same account running the same script on different machines but it will only complete on the first machine. I can schedule it to run on either machine over night and it runs fine. As soon as I want to run it on both machines, it will fail on the second one.
I've wrapped my import into try/except to make sure that's really where it's failing:
<SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
<SPAN class="keyword token">import</SPAN> arcpy
<SPAN class="keyword token">except</SPAN> Exception<SPAN class="punctuation token">:</SPAN>
<SPAN class="keyword token">with</SPAN> open<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">'C:\temp\arcpyIssue.log'</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">'w'</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="keyword token">as</SPAN> failurelog<SPAN class="punctuation token">:</SPAN>
failurelog<SPAN class="punctuation token">.</SPAN>write<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"Unable to get arcpy license"</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="line-numbers-rows"><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN></SPAN>and that appears to indicate the arcpy import is the issue? Any thoughts? Shouldn't I be able to run as many instances of Pro or Pro licensed Python under the same account as I want? I seem to have no issues having instances of Pro open on multiple machines using my own account.