Latest Contributions by JonathanQuinn

The point of the load balancer in Portal HA is to balance the requests between the two portal machines but also monitor the health of the machines.  If one machine goes down, the load balancer should be smart enough, (using the built in health check for Portal), to only send traffic to the health machine.  The secondary portal machines is there for redundancy.  While both machines are active in the configuration, (the load balancer will send traffic to both machines and both machines will serve out content), a database on the primary machine is accessed by both portal machines.  The data is replicated to the standby so in the event that the primary goes down, the standby can assume the role of primary and promote it's own database to be the primary database.  Portal is not CPU bound like Server is, so you're not necessarily creating an HA portal for scalability but rather redundancy/availability. ... View more

Roberto Messora‌ did you set the Web Context URL, following the use a reverse proxy with Portal documentation that pfoppe‌ mentioned?  That should tell the Portal that there's a different front-end than the web adaptor.  It only redirects to the web adaptor because that's what it knows to be the entry point to the portal. ... View more

You're at the Rest API, not the Admin API: https://<server>.<domain>.com:6443/arcgis/admin/services/SampleWorldCities.MapServer?f=pjson The bolded section is the URL to the Admin API.  Log in with administrative credentials to make changes. I would start with looking at the overview of scripting administration of your Server, and the specific examples of editing service properties and checking a folder for stopped services for pieces of code you can use. ... View more

You're using 10.5, correct?  You can run a full backup for Portal which will clear out the walarchive files.  It's a best practice to be backing up your Portal anyway.  This can be done using the DR tool, (recommended for full ArcGIS Enterprise deployments) or through Portaladmin. ... View more

So it seems like GIS Server 1 and GIS Server 2 are part of the same site?  Is administrative access enabled through the web adaptor?  If so, use the same Services URL and Admin URL for federation.  That will federate the site, (both Server machines), with the Portal and provide a redundant URLs in case either Server isn't reachable. ... View more

Here's another link for reference: Tutorial: Set up a base ArcGIS Enterprise deployment—Portal for ArcGIS (10.5) | ArcGIS Enterprise  ... View more

You can look into writing a python script to get the "minInstancesPerNode" and "maxInstancesPerNode" properties from the Admin API: https://<server>.<domain>.com:6443/arcgis/admin/services/SampleWorldCities.MapServer?f=pjson ... View more

Just to add to this, if you're publishing a map service from data that is not registered, it's going to copy the data into the arcgisinput folder.  If you're publishing a map service with feature access using data that's not registered, it'll copy data into the ArcGIS Data Store and create a traditional map service that spins up an ArcSOC.exe process.  If you're publishing a feature service directly to Portal, the data still goes into the ArcGIS Data Store, but you're publishing a "hosted feature service" that won't spin up an ArcSOC.exe process. Since you're publishing a map service, the data won't be copied into the ArcGIS Data Store.  Once you publish a service that requires a relational database to store the data, (any feature service), it'll copy the data into the ArcGIS Data Store. ... View more

If you publish a map service from ArcMap and copy data to the Server, the data will live in the arcgisinput folder, ex C:\arcgisserver\directories\arcgissystem\arcgisinput\<service>\extracted\v101.  I'm not sure if that's the same with Pro, but that's a place you can look. Pretty sure it'll be the same location. ... View more

Do you have an active/active configuration or are they part of the same site?  Considering you're using the web adaptor, I assume they're in the same site.  If so, there's no need to federate both machines that participate in the site, you simply federate the site.  Both machines will recognize they're federated.  If you've set up your servers so they're redundant, then you'll want to federate using a URL that can be aware of the health of the machines for example: Services URL:  https://gismachine1/arcgiswebadaptor - this URL is for users to reach the Services in web applications.  Admin access can be disabled. Admin URL https://gismachine1/adminwebadaptor - this URL can be used as the admin URL for federation.  It's registered with the ability to reach Manager and the Admin API through the web adaptor. The admin URL can also be a third party load balancer if you want to go that route. ... View more

This isn't addressing your specific problem, but possibly another way to achieve what you're looking to do is to query the JSON of the service from the Admin API, store it in a variable, publish the new service, and then overwrite the JSON with what you've stored.  If the only thing you're changing is some layers or other properties in the MXD, that may work for you. ... View more

Right, but this is in your environment, where you didn't see the problem to begin with? On Rawan's machine, perhaps the local account did not have read access to the directory, or perhaps the Users group was also not granted read access to the directory, (which I think by default, local accounts are added to).  The Administrators group may have already had at least read access to the directory.  Either way, we can only speculate, as there isn't enough information to determine exactly why that fixed the problem. ... View more

I wonder if the Admin group had more privileges on the directory storing the data.  Once the user was part of the admin group, the account would then inherit those privileges.   ... View more

It appears as though you're providing the URL to a server you've already federated.  The URLs must be unique.  For example, if you federate a server that uses https://myserver.domain.com/server as the Services URL and https://myserver.domain.com:6443/arcgis as the Admin URL, that would point to a single site.  Each site should have unique URLs that will be used to federate.  If you're 100% sure that the Server isn't federated, but the Portal thinks it is, then that's another problem. ... View more

Yes, you can have more than one federated Server in Portal, but you can only have one hosting server. What http/https requests do you see failing when opening Survey123? ... View more