|
POST
|
Hello - I am preparing to upgrade our Monitor from 2023.3.1 to 2024.1. I did not upgrade to 2024.0.x for a variety of reasons - (e.g. did not want to install all of the agents across on all of our hosts, the datastore monitoring components were not ready yet, 2023.3.1 is still stable and providing me with the metrics we need, the web adaptor wasn't ready yet . . .) - but now that the additional capabilities at 2024.1 are released, and we are 11.4, it is now time to upgrade. My question is - I show an ECP for Monitor 2024.0 as available in our MyEsri, but not for 2024.1. Typically this means I can apply this ECP but am reaching out to find out if this in fact true. @DerekLaw do you know? Thanks, David
... View more
01-29-2025
01:02 PM
|
0
|
2
|
1192
|
|
POST
|
Hello - I am preparing to upgrade our existing 2023.3.1 Monitor to the newly released 2024.1 version and came across this post. I did not upgrade to 2024.0.x for a variety of reasons. My question is I don't understand how this post was created on 10/16/2024 but is referring to the 2024.1 release. How could that be when 2024.1 was just released? I'm sure the version in the post title is some 2024.0.x version? Thanks, David
... View more
01-29-2025
12:53 PM
|
0
|
1
|
1350
|
|
POST
|
Yeah I am experiencing the same thing as shown in my IIS logs. I need to resolve this because it's related to a bad query that keeps happening to a hosted Street layer and hammering my hosted site server logs with a SEVERE level entry. I can't figure out what would be using esri.com from a ArcGIS Pro Client. It is not Open Data. But the request keeps looking for a {FULL_NAME} attribute on the hosted Street layer when it should be requesting {full_name}: Hosted/Street/FeatureServer: Field name 'FULL_NAME' does not exist. Did you mean 'full_name'? In my case, the client and referrer are: Client: ArcGIS+Pro+3.2.0+(00000000000)+-+ArcGISPro Referrer: http://www.esri.com/D187C34C-A620-43CE-A4B1-C53D26AE92AF So if anyone has any ideas, that would be great.
... View more
01-17-2025
07:04 AM
|
0
|
0
|
830
|
|
POST
|
I was going to say, sounds like you have to treat this like a Portal - Online collaboration and not as a Portal to Portal collaboration
... View more
01-10-2025
12:59 PM
|
0
|
0
|
1795
|
|
POST
|
Hi @Brian_McLeer , no that is not what I am saying. Yes it makes a difference that these are all custom basemaps. If all tile or vector tile layers making up your basemaps are coming entirely from your own tile / vector tile layer sources, then I don't know what to tell you, other than there is a sharing issue with those source layers and that's where I would check, as I'm sure you already know.
... View more
12-23-2024
12:56 PM
|
0
|
1
|
1874
|
|
POST
|
No, you're right, you don't want to enable anonymous access to portal. All I can say is that even though all the basemap webmaps still show as shared with Everyone, you still may have to update the Living Atlas. What happens when you go into each one and re-save? Are you getting prompted to update sharing?
... View more
12-23-2024
11:43 AM
|
0
|
1
|
1890
|
|
POST
|
Yeah, I had some wankiness on this as well, but not until we performed our restarts as part of the Windows Updates and then restarts. We too always restart in a stagger, with our config server going first, then host site server 1, host site server 2, relational data store, object store, fed site server 1, fed site server 2, and then portal server. So being aware of the Dynamic Mapping host service not behaving, I wasn't sure how that was going to manifest on our system. For the host site, it's not a big deal as we only use the host site for hosted feature layers, vectortile layers, scene layers... For the Federated site, it does matter. That's the site, (for us) hosting referenced feature access services in shared instances. After our restarts, I could see the dynamic mapping host was running on federated server 1, but was not running on federated server 2. After I restarted federeated server 2, dynamic mapping host came back up and so was visible as running on both machines. Then I went in to site settings, decreased to 4, saved. Then increased back to 8 (per machine) saved again. Then for server manager for the federated site, I restarted the dynamic mapping host service. It came back up showing 16 available max instances. So that did it for us, but I will be checking it's status after next months windows updates / server restarts
... View more
12-20-2024
12:01 PM
|
1
|
0
|
4167
|
|
POST
|
Ok well I figured out a workaround by running things from the Portal server and utilizing shared directories on our Config server for the shared location and the backup location specified in the properties file. It's not really a workaround per se but prior to the last release or 2 it was alot easier to run things from a desktop with the proper directory shares in place. Our polices are pretty strict so we can't run things from 'C\Program Files\ . . .' but I can copy out the webgisdr directory to my user-defined shared location and then run my bat that calls the 'myfullsitebkup.properties' file. Hopefully it'll run in the Task Scheduler...
... View more
12-16-2024
01:43 PM
|
1
|
0
|
1698
|
|
POST
|
Some more info on this. I basically ended up having to uninstall datastore and then re-install it with only the object store as an available datastore type. Otherwise, when I tried to upgrade the tileCache datastore, the upgrade program saw this as a relational store update, even though the 'type to update' read 'tileCache'. Not sure why, but probably because I had previously made a relational store available on this machine, it then created a relational store as a standby machine to my current relational store that is installed on a separate machine. I then went into server admin and removed the 'standby' machine. Then I uninstalled data store entirely and wiped out the content in both the C:\Program Files\ArcGIS\DataStore directory and in my D:\arcgisdatastore content directory. When I reinstalled Data Store, I only allowed for the object store type.
... View more
12-16-2024
11:22 AM
|
0
|
3
|
1406
|
|
POST
|
Hello - After finishing a largely successful 11.3 to 11.4, I copied the the webgisdr folder from it's default location on the Portal Server at C:\Program Files\ArcGIS\Portal\tools\webgisdr to a shared location on my desktop, and set up the proper shares for my temp, bakups and backup folders so that I can run a weekly backup to a file share. I then set the JAVA_HOME system environment variable to the latest JRE, which I currently show as: C:\Program Files\Java\jre1.8.0_431 Apparently this is the latest version of the jre. For the webgisdr properties file at 11.3, the JAVA_HOME requirement states: # If running the WebGIS DR Tool from a machine without Portal for ArcGIS installed, # make sure to set the JAVA_HOME operating system environment variable to a # Java Runtime Environment 1.8 or later installation directory. which I always had downloaded from https://www.java.com/en/download/manual.jsp Now, at 11.4, the JAVA_HOME requirement states: # If running the WebGIS DR Tool from a machine without Portal for ArcGIS installed, # make sure to set the JAVA_HOME operating system environment variable to a # Java Runtime Environment 11 or later installation directory. Predictably, the webgisdr tool is now failing with the following: Exception in thread "main" java.lang.UnsupportedClassVersionError: com/esri/arcgis/portal/util/FileUtil has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 Currently, I have no idea where to get the JRE 11 - it is not available at the https://www.java.com/en/download/manual.jsp site. That site says the latest is update version is version 8. Are there any suggestions from anyone? This method has always worked for us up until now, and I'd prefer not to run the backup from Portal server, mainly because I like to keep that server as light as possible. Thanks, David @JakeSkinner @JoshuaBixby @Scott_Tansley
... View more
12-16-2024
06:43 AM
|
0
|
1
|
1721
|
|
POST
|
Yes I agree. I think for my 11.3 to 11.4 upgrade this weekend that it is safer (for on-premises, multi-machine deployments on Windows Server 2022 VMs) to go ahead and uninstall the web adaptor prior to upgrade and make sure through the admin pages that the web adaptors are unregistered. Because I am now deactivating AV scanning during upgrade and post upgrade, I just don't want to have the WAs in place at all, so that (as @JoëlHempenius3 says) any calls to ..../myalias.myorg.net/portal/... should go unresolved or otherwise not found. The post upgrade steps don't use the web adaptor anyway, and I still can't find any help documentation on why this change was made in the first place. @Scott_Tansley
... View more
12-11-2024
06:21 AM
|
0
|
0
|
3125
|
|
POST
|
.... and I now see that the full-text index capability is indeed part of the 1.4 Enterprise release . . . good deal
... View more
12-11-2024
05:39 AM
|
0
|
0
|
909
|
|
POST
|
Ok, so this is a new install and you are trying to create a new site based on this: https://enterprise.arcgis.com/en/portal/latest/install/windows/installing-portal-for-arcgis.htm ? and then trying to configure a new portal based on this: https://enterprise.arcgis.com/en/portal/latest/install/windows/create-a-single-machine-portal.htm ? If you can't create the new Portal, then I'd say there is something about either a DNS re-direct issue or maybe firewall, or maybe the required ports aren't open. I haven't had to install a new portal since 10.6, and then I used the Join Site method when we upgraded our windows machines from 2016 to 2022. Based on what you are showing in your last, it looks like your portal site is in place. Can you get to the Content page? https://dnsalias.ourorg.net:7443/arcgis/sharing/rest/
... View more
12-10-2024
10:30 AM
|
1
|
1
|
4108
|
|
POST
|
Thanks for the reply @tcaulum_WPPI - actually we're good. I forgot about the conversion mechanism where we are able to convert 1 concurrent Creator to up-to 3 named user types, although I have to double-check the levels. Yes you are correct, we can still use the concurrent use license manager at 11.4, it is just not required
... View more
12-09-2024
09:42 AM
|
0
|
1
|
6190
|
| Title | Kudos | Posted |
|---|---|---|
| 6 | yesterday | |
| 1 | a week ago | |
| 1 | 3 weeks ago | |
| 1 | 4 weeks ago | |
| 2 | 05-22-2026 01:02 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|