|
POST
|
If a remote worker is not on our local network and not using a VPN, when they try to use ArcGIS Pro they get the Enterprise sign in page and after signing in they get an error message saying the License Manager could not be reached. It was once explained to me that is because ArcGIS Pro attempts to make a separate connection to the License Manager and it is looking for the PortNumber@FQDN of License Manager that is provided by Enterprise. That makes sense because as soon as I use a VPN to connect to our network ArcGIS Pro gets the license and works, but if I disconnect the VPN I loose the license and get the warning that I have 60 minutes to save my work before ArcGIS Pro closes. Reconnect with the VPN and ArcGIS Pro is happy again. If there is a way to have Enterprise be the proxy to the License Manager for ArcGIS Pro I would appreciate knowing how to set that up. We are running Enterprise 10.8.1, License Manager 2020.1, and ArcGIS Pro 2.7. Tomorrow I will be upgrading everything to the latest version so we will be on Enterprise 10.9, License Manager 2021.0, and ArcGIS Pro 2.8. Will that make a difference?
... View more
07-28-2021
12:39 PM
|
0
|
1
|
4428
|
|
POST
|
They sign into Enterprise to license ArcGIS Pro. My understanding is ArcGIS Pro makes one connection to Enterprise to handle the authentication of the named user and check to see if they are allotted an ArcGIS Pro license. Then, if authentication is successful, ArcGIS Pro makes a separate connection to License Manager to get the license. I am trying to find out how to safely let remote workers use ArcGIS Pro licensed through Enterprise without requiring a VPN connection to our network. However, I do not want to expose my License Manager to the internet if that means anyone who finds the open port can use our licenses.
... View more
07-28-2021
09:59 AM
|
0
|
0
|
4431
|
|
POST
|
A little background first. I have an ArcGIS Enterprise 10.8.1 deployment that is accessible over the internet through a web adaptor. A problem that we have had for years is that our portal is accessible via the internet but whenever any of my users opens ArcGIS Pro off network they get an error that the ArcGIS License Manager (ALM) is not accessible, which is expected because the ports for ALM are blocked from the internet by the firewall. Is it safe to expose the ALM to the internet so remote workers have access to ArcGIS Pro without having to use a VPN? If I get my system admin to expose the ALM port to the internet, will anybody who finds the port be able to access our licenses managed through ALM? Does Esri have a way or documentation on how to proxy the ALM connection? Could ArcGIS Pro use a standard URL that is provided by a proxy to request a license. Then have the proxy connect to ALM get the license and have the proxy pass that back to ArcGIS Pro. I wish Esri would just add that functionality to ArcGIS Portal so that ArcGIS Pro, Drone2Map, etc. just make one call to ArcGIS Portal and ArcGIS Portal handles both authenticating the user and passing the license from ALM to ArcGIS Pro.
... View more
07-27-2021
01:02 PM
|
0
|
8
|
4461
|
|
POST
|
Will ArcGIS Pro licensing work with ArcGIS Enterprise like it does with ArcGIS Online? My users can access our ArcGIS Enterprise deployment with an internet connection but to use ArcGIS Pro they have to start a VPN session to connect to our network because the ArcGIS License Manager is not exposed to the internet. I would love to see ArcGIS Pro just talking to ArcGIS Enterprise and ArcGIS Enterprise acting as a proxy to ArcGIS License Manager for ArcGIS Pro.
... View more
07-22-2021
08:39 AM
|
0
|
3
|
5532
|
|
POST
|
Thank you! I went back to 2.8.0 and that fixed the issue.
... View more
06-28-2021
07:38 AM
|
2
|
2
|
6203
|
|
POST
|
After installing the patch for ArcGIS Pro 2.8.1, every time I launch an ArcGIS Pro project that has an existing Python Notebook the active Python environment changes back to arcgispro-py3. The only thing that changed was installing the 2.8.1 patch. I have tried reinstalling ArcGIS Pro and cloning to different locations, but as soon as I open that notebook the active environment changes back to arcgispro-py3. The notebook previously used a cloned environment with no issues.
... View more
06-25-2021
03:08 PM
|
2
|
10
|
7532
|
|
POST
|
Glad to hear that the new domain is working. Is it the domain that will not delete or an attribute field that is using the old domain? If you are trying to delete the domain, have you tried the Domain Usage tool to see if there are any feature classes still trying to use the old domain?
... View more
06-08-2021
11:52 AM
|
0
|
1
|
14302
|
|
POST
|
I know this topic has come up several times ever since Vector Tiles were release and that there is a enhancement request regarding the issue (ENH-000098440), but I cannot get labels for road features to draw consistently at all scale levels. Same settings between scale levels for the labels besides font sizes and minimum repeat valves, but some levels the labels work fine, some levels only some of the label classes draw, and several levels show no labels. I have read the guidelines at https://pro.arcgis.com/en/pro-app/latest/help/mapping/map-authoring/labeling-in-vector-tiles.htm but I am still having issues. The issue of all road labels missing at scales 9,028 through 282 is the most confusing issue. Are there any other guidelines for labeling vector tiles from Esri?
... View more
05-27-2021
03:55 PM
|
0
|
0
|
1070
|
|
POST
|
The response that I received from Esri was the production version of the new Map Viewer will be available as part of ArcGIS Enterprise (AGE) 10.9.1. AGE 10.9 is shipping with and locked to the December 2020 version of the Map Viewer Beta and AGE 10.8.1 has the March 2021 version of the Map Viewer Beta available as a separate install. Here is a link to the post about the production version of the new Map Viewer being available at AGE 10.9.1: https://community.esri.com/t5/arcgis-enterprise-questions/did-the-new-map-viewer-and-dashboard-apps-make-it-into-arcgis/m-p/1055212#M30106
... View more
05-11-2021
07:31 AM
|
0
|
0
|
1466
|
|
POST
|
Esri just answered the question about the Map Viewer Beta in a blog post: https://www.esri.com/arcgis-blog/products/arcgis-enterprise/announcements/map-viewer-beta-in-arcgis-enterprise-10-9/ ArcGIS Enterprise 10.8.1 has the Map Viewer Beta March 2021 edition and ArcGIS Enterprise 10.9 has the Map Viewer Beta December 2020 edition and will not be updated. So the final version of the new Map Viewer found in ArcGIS Online is not available for any version of ArcGIS Enterprise at this time.
... View more
05-07-2021
06:45 AM
|
0
|
1
|
1696
|
|
IDEA
|
I think it would be useful to have ArcGIS Pro query a connection, be it portal connection or geodatabase connection, to determine the connection's version and only present options and functionality up to the level that the connection supports. I would like to have some kind of backwards compatibility built into ArcGIS Pro if it is going to keep being release ahead of a compatible version of ArcGIS Enterprise. Often ArcGIS Pro has a new release that targets a unrelease version of 10.x or geodatabase. If you try to use that new version with a 10.x or geodatabase release that is below the expected version there are often issues because ArcGIS Pro is trying to do something that ArcGIS Enterprise or the geodatabase does not support. A great example of this has been the releases of ArcGIS Pro 2.7 in December 2020 and ArcGIS Enterprise 10.9 in May 2021. So from December 2020 to May 2021 there was no compatible version of ArcGIS Enterprise that you could use with ArcGIS Pro 2.7. I tried using ArcGIS Pro 2.7 with ArcGIS Enterprise 10.8.1 but ran into a few issues that only resolved by going back to ArcGIS Pro 2.6.
... View more
05-06-2021
01:38 PM
|
0
|
0
|
1053
|
|
POST
|
Personally, I would try rolling back to ArcGIS Pro 2.6 on just one computer and test to see if the domain editing and view publishing issues go away. If that resolves the issue then just have that one computer be the publishing/geodatabase maintaining computer. I think all the other computer can stay at ArcGIS Pro 2.7 for consuming and editing feature services. If you do roll back all the computers to 2.6, any projects that were saved using 2.7 will show a warning stating any 2.7 based functionality will be stripped from the project when saved using 2.6. So if you did not use any new 2.7 functionality in the project nothing should be lost. Here is a link to the ArcGIS Pro compatibility matrix that shows what ArcGIS Enterprise/Geodatabase version each version of ArcGIS Pro is designed to work with I now have this page bookmarked: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/client-geodatabase-compatibility.htm Since Esri keeps releasing new versions of ArcGIS Pro before the compatible version of ArcGIS Enterprise is released, I wish ArcGIS Pro would have better backwards compatibility.
... View more
05-06-2021
01:19 PM
|
0
|
0
|
2578
|
|
POST
|
As long as the "Lock Schema" is turned off on all 50+ feature services, I would think you should be able to edit the domain successfully. That is assuming that there is not some ArcGIS Pro 2.7 bug preventing the changes. I think also you should be able to manually be able to edit the domain values without using the Table to Domain tool.
... View more
05-06-2021
10:08 AM
|
0
|
0
|
14778
|
|
POST
|
You may want to try using ArcGIS Pro 2.6 to make these changes. Technically ArcGIS Pro 2.7 is at the 10.9 version when it comes to geodatabases and is expecting to connect to ArcGIS Enterprise 10.9. I just ran into an issue with trying to publish a new feature service from 2.7 to ArcGIS Enterprise 10.8.1. After several days of troubleshooting and digging through log files I found the issue was due to a new attribute rule that was created using 2.7. Apparently when 2.7 created that attribute rule it changed version level of the feature class in the SQL Server enterprise geodatabase and ArcGIS Enterprise 10.8.1 refused to connect to the feature class. Removing the attribute rule in 2.7, going back to ArcGIS Pro 2.6, recreating the attribute rule, and then publishing fixed the problem.
... View more
05-06-2021
10:03 AM
|
0
|
1
|
7981
|
|
POST
|
Back in the fall I had to update domains for a branch versioned feature service. At the time we were running ArcGIS Enterprise 10.8.1, SQL Server, and ArcGIS Pro 2.5. I was not manually updating the domain values but using the Table to Domain geoprocessing tool instead. I had to restart the service and close/reopen ArcGIS Pro to see the changes. To see the domain changes without restarting anything I had to go into the service properties and uncheck the "Lock Schema" option. The only other thing that I can think of is even though you are changing the domain value in the domain list you will still need to update any features that are referencing any domain values that were changed. I know I have forgotten to do that in the past. The second process you referred is showing no domain after switching to a new domain because the a config file for the feature service is still looking for the old domain which the feature class is no longer using. You would have overwrite the service to have the service know to use the new domain. You should be able to update your current domain list without have to overwrite anything.
... View more
05-06-2021
09:23 AM
|
4
|
6
|
14817
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Tuesday | |
| 1 | 04-15-2026 06:52 AM | |
| 1 | 04-15-2026 12:13 PM | |
| 1 | 04-13-2026 09:30 AM | |
| 1 | 03-24-2026 01:01 PM |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|