Latest Contributions by JonathanQuinn

First, when configuring the Web Adaptor, reach the web adaptor registration page via the URL you want to use as the "public URL". For example, if my machine is wa.domain.com, reach the web adaptor registration page via https://wa.domain.com/portal. You may have multiple hostnames on the machine, but as long as you use the intended URL to reach the registration page, that will be written to Portal's config files. Second, make sure that you use the correct hostname within the portal URL parameter. It should set the hostname within the portal nodes section in the webadaptor.config file. ... View more

I was able to reproduce the "unable to generate token" error. Feel free to contact technical support and present them your architecture/steps to repro if you want to log an official bug, but we've logged an internal issue. I read through the thread you posted, but I'm not sure why we are writing to the hostname.properties file during a restart. I didn't think we wrote anything to it, I was under the impression you, as a user, would define the entries in that file and Server would honor it, (for example, multi-NIC or multiple hostnames on the machine). Server overwriting those changes defeats the purpose of the file. ... View more

How many resources the components and services will use, (aside from disk space), is going to be dependent on the load on the machines. You can publish 10000 hosted services, but if you only have a handful of users, then you won't see an issue. If you have 10 hosted services and significant load on the services, then that's another story. In my opinion, best practice is to make sure you have enough resources on all machines running the components, which applies to whether you put all components on one machine or all on separate machines or any combination of that. Our cloud builders for AWS and Azure set up two machine sites with Portal, Server, and Data Store on each. Does that mean it's a best practice? Maybe, maybe not, but individual system architects typically end up deciding what their own best practices are, because they have either positive or negative experiences one way or another. ... View more

Thanks for the diagram, I was able to reproduce the behavior in-house. I'm thinking it has to do with the machine having an alias. I can't reproduce it if the admin URL is set to the machine name, (https://ags1.domain.com:6443/arcgis, for example). If possible, try to update the admin URL via the URL you referenced and see if you can run the DR tool. ... View more

If you have orphaned items, deleting files on disk outside of going through the Sharing API won't remove them from the index, which is why they continue to be returned via searches and within the Portal site. Deleting an item through the Sharing API will remove the item from the index. You could try to reindex after deleting them, but you run a chance of a discrepancy between the database counts and the index counts. ... View more

The important error is the "not a database cluster directory" error. What are the contents of the latest dbxxxx folder? Do they match the contents of the db folder on the primary machine? What's likely happening is that the standby is detecting that the database is not running so it thinks it's coming back from a failure and gets a new DB snapshot. The standby can't start the DB again, (due to the not a database cluster directory error), and then again, it thinks it's coming back from a failure because the database isn't running. That's likely the loop it's stuck in. Figuring out what the PG doesn't like about the db directory is the first step by looking at the contents. ... View more

So the actual hostname of your hosting server is ags1, but it has an alias of myalias1, and it seems like the alias is used throughout the deployment. Can you check what the Server lists for it's machine name under the Admin API > machines? ... View more

If Google Sign In is a SAML/ADFS provider, you could try to set up Portal to use it: https://enterprise.arcgis.com/en/portal/latest/administer/windows/configuring-a-saml-compliant-identity-provider-with-your-portal.htm Google isn't listed, but it could work, no guarantees though. ... View more

In my opinion, you can install the software on any machine that has enough resources. Typically, you'll have a dedicated database tier for your SQL Server, Oracle, PG etc type databases, but for the ArcGIS Data Store, you can install it on the same machine as any of the other components. Again, the only thing to keep track of are resources on the machine, (RAM, CPU). ... View more

You'll be able to update the admin URL of a federation after you actually federate. Not sure if aliases/traffic resolution is the problem here but just wanted to point that out. Can you provide a network diagram so we can understand your architecture? What URL are you using for the PORTAL_ADMIN_URL? ... View more

Check the Event Viewer. When you see "database startup timed out" type errors, that means that the database isn't starting correctly and the only place the cause is logged is in the Event Viewer. You'll see a bunch of errors in there, but there will be one that tells you why the database can't start. ... View more

So if you were able to log onto the machine and access the shared content directory, there shouldn't be a problem with Portal doing the same thing. I assume you're still seeing the "Cannot read from directory path" error? I'm not sure why the content would have grown so large. You should identify what files were created during that time, search for the itemID within Portal, and identify who created the items. No, re-federating isn't a solution and will cause more problems. How long does it take for https://portal.domain.com:7443/arcgis/sharing/rest/portals/self to return a response? ... View more

On the primary machine in an HA configuration, the dbXXXX folder is created during a restore. On standby, it's created when the machine is coming back from a failure. Other than that, it shouldn't be getting created on primary. The only situation I'm aware of that will continually create dbXXXX folders on standby is the presence of the promote.dat file within the db directory on the primary machine. Can you see if that file is there and if it is, delete it? It'll create one more dbXXXX folder on standby but should be stable after that. Can you check the logs and see if there are any indications as to why it's creating the db snapshots on the machines? ... View more

The web adaptor is doing very basic load balancing. It knows of the two (or more) machines in your site and is doing simple round-robin load balancing to each Server. It has no knowledge of capacity, load, or weighted load balancing nor can it determine that a request should go to a specific machine based on the requested service. What version are you using? In previous versions, clusters were recommended, so a two machine site could have two separate clusters with different services on each. The web adaptor would still send requests to both machines and internally, the Server site can determine where that service resides and that machine will serve the request. That's the only situation where there is internal load balancing/traffic redirection for specific services, though. Anyway, I've never tried that and I doubt that's something that has been tested internally. I'd proceed with caution. Are you seeing performance issues, or are just wondering about increasing throughput? ... View more

The URL you use to reach the web adaptor registration page, (https://webadaptor.domain.com/portal/webadaptor/portal) is the URL that's set for the Web Adaptor URL. If you have a machine with a hostname and alias, ex wa.internal.com and webadaptor.acme.com, you should reach the web adaptor registration page via webadaptor.acme.com, not wa.internal.com. The web page brought up after the install likely defaults to the internal name. ... View more