Hi Portal folks,
does anyone use ArcGIS Pro With Portal yet?
I have trouble setting up the License Manager on the Portal server, so that Portal can manage the Pro Licenses.
When starting Pro, it Connects to Portal, but "hangs" several minutes, claiming it could connect to Portal but not get a valid license.
In Portal, I can see that my user have used Pro.
So I suspect that Portal is not able to communicate with License Manager on the same server.
lmgrd is running on the Portal server, and License Manager is showing free Pro Licenses.
I am not able to find any log entries showing relevant activities, or any documentation on how this is working, especially regarding necessary firewall openings.
Could it be that communication Pro - Portal - License Manager requires some special firewall openings?
Mr. Paulsen, Lars Petter
Solved! Go to Solution.
When ArcGIS Pro opens, it first communicates with Portal to retrieve licensing information. This is done over the Web Adaptor url. It then needs to communicate directly with the License Manager to check-out the licenses. This is done by default over port 27000.
FYI, please review this thread for additional info: Re: Authorizing Portal to Administer Pro Licenses Confusion
Hope this helps,
Another thing that you may try is the following:
I know this may not answer the question but it's a troubleshooting step at the least.
Hope this helps.
thanks for this tip. I tried it, and do get the correct reply, so now reaching the port is not the problem.
I got a tip from support suggesting that a CA-signed certificate could cause problems, should possibly switch to self-sign to test that.
I know that if you have a self-signed certificate ArcGIS Pro will not connect to Portal as it cannot trust the certificate.
You could however, be running into a certificate mismatch issue. You could use Fiddler to confirm this to be true.
Do you use a DNS alias for Portal? If so when you registered the web adaptor did you use the machine name or the DNS alias. If you used the machine name then you'll want to complete the following steps and test further.
(1) Log into the Portal Admin endpoint (https://servername.domain.com/webadaptor/portaladmin
(2) Click on System --> Web Adaptors --> machine name
(3) In the address bar go to the end of the URL and add /edit
(4) On the next page under Web Adaptor URL update this value to reflect the DNS alias
(5) Click Edit Web Adaptor
Once this is complete every Portal URL request will reference the DNS alias instead of the internal machine name.
Hope this helps.