POST
|
I have a specific order in which I conduct upgrades. I start with the Portal, move on to Portal WA, then upgrade the Server followed by Server WA, and finally, the Data Store. This order is important because during the upgrade process, the new WA needs to register with the appropriate Portal/Server component.
... View more
4 weeks ago
|
0
|
0
|
49
|
POST
|
Definitely sounds like there is an issue either with the Windows Share Permissions for \\\\NetworkSharedFolder\\ServerBackups\\portalserver or with the actual permissions on the folder itself. When you run the webgisdr utility manually, via the command line - you're probably using your own login. When the same utility is run via Windows Task Scheduler, it is using either a service account or 'something' else. Check what account it is using and adjust if necessary. For this distributed set up, I would use the same account to run the task as you're using to run the various Portal, ArcGIS Server, Data store services.
... View more
4 weeks ago
|
0
|
3
|
288
|
POST
|
Hi there, we did something almost the same: 1. We created a new project file with the corrected datasources. 2. Extracted the dataConnection properties. 3. Stepped through a folder structure that had all the project files, opened up each project and found all that were broken and replaced them with the corrected datasource from step 2. Note: A. We had V3 (version 3) of the layer definition file compared to V2 in your code. B. Very surprised that the initial change where the featureDataSet was removed from the EGDB, that it didn't break anything in the project files.
... View more
4 weeks ago
|
1
|
0
|
52
|
POST
|
Can you access the local web server (assuming you're using a web adaptor and local IIS)? Can you also access portal on port 7443?
... View more
03-15-2024
05:49 AM
|
0
|
1
|
523
|
POST
|
For built-in 'local' Portal accounts, it is normal for usernames to use the form 'username' - though one can use any form, so long as it is consistent. Usernames that use the form username@org.email usually come from an IDP provider. Am not sure if your first example is typical though it could be due to the way the claims are mapped between what ArcGIS Enterprise needs and what the IDP provides. As for users needing to type 'username@org.email in; it shouldn't be necessary as it is likely they've already signed in already via a browser.
... View more
03-14-2024
08:15 AM
|
0
|
1
|
194
|
POST
|
Hello, @Yogesh_Chavan for step 4, delete the ArcGIS Server site on Server A. This is through the ArcGIS Server Administrator Directory where there is an option to 'deleteSite'; this removes the config-store information but doesn't go as far as completely reinstalling the software. All I am suggesting is to switch Server A with B; so that it is B that has Server A join it. We're trying to isolate the cause of the joining site issue.
... View more
02-13-2024
07:44 AM
|
0
|
1
|
213
|
POST
|
Can I suggest the following, let's reverse the server configuration: 1. Unfederate Server A. 2. Install Web Adaptor onto Server B. Call the web context as 'server' instead of the default 'arcgis'. 3. Federate Server B to the Portal. Test and Confirm that all is working as expected. 4. Delete the server site from Server A. Uninstall the Web Adaptor on Server A. 5. Reinstall the Web Adaptor and call it 'server' instead of 'arcgis'. 6. On Server A, 'join server site' to Server B. 7. Federate to Portal using the address of Server B. Question: have you considered using a load balancer in front of Server A and Server B?
... View more
02-12-2024
03:45 AM
|
0
|
3
|
267
|
POST
|
Server A - ArcGIS Server with Web Adaptor. Server B - ArcGIS Server Server C - Portal for ArcGIS Some clarification questions: 1. When you're joining Server B to Server A (prior to federating) - is the config-store for Server A in a shared location, accessible to both Server A and B? 2. Is there a Web Adaptor on Server B? 3. When federating with Portal, what are you using as the URLs for both the ArcGIS Server and the ArcGIS Administration URL? 4. Can Server B resolve and 'see' Server C (via hostname or FQDN)?
... View more
02-08-2024
08:49 AM
|
1
|
1
|
329
|
POST
|
Just adding to what Scott said - the DNS record type is partly dependent on what you've been given. The A and CNAME records are the two common ways to map a host name (“name”) to one or more IP addresses. There are important differences between these two records. An A record points a DNS name to a specific IP. If you want FQDN maps.mingworld.net to point to your server or load balancer with the following external IP of 99.12.12.187 you’ll configure: maps.mingworld.net. A 99.12.12.187 A CNAME record points a name to another name instead of to an IP. The CNAME source represents an alias and is common with most of the Public Cloud Providers where your deployed server is accessible through this alias rather than a fixed IP as your provider most likely will recycle their pool of IPs. For example: mingworld.uksouth.cloudapp.com would be configured as a CNAME thus: maps.mingworld.net. CNAME mingworld.uksouth.cloudapp.com. In each case, typing in maps.mingworld.net will resolve (and redirect) to either the IP or the CNAME seamlessly. As for A records being a bit more efficient; that it is probably because there is a less involved process of resolving access to the resource. A CNAME ultimately, also needed to resolve to an IP (and then MAC address etc.)
... View more
02-08-2024
12:47 AM
|
2
|
0
|
193
|
POST
|
Looks fine from the screenshots you have shared. I have run not run a 11.1 CF Template for Linux in AWS yet. Last time, I used AWS CF Template was to deploy a 10.9.1 (Linux) into AWS. Might be worth trying an earlier version first (you can always upgrade it to 11.1)
... View more
11-15-2023
03:07 AM
|
0
|
0
|
458
|
POST
|
When you took an AMI and relaunched a new instance, assume that it took on new Internal IPs? If so, I would uninstall both your web adaptors and check that you can still access portal and server on ports 7443 and 6443 respectively. If so, then reinstall the webadaptors -- using the new internal IP of the VM to register them. You can use their FQDNs but internal IP is fine, so long as they don't change.
... View more
11-15-2023
02:59 AM
|
0
|
0
|
259
|
POST
|
From my experience, just re-running the workflow again (maybe use a new resource group) usually is worth doing. Specifically, the PFX file you've created: is this for a new Domain Name and has this been setup within your Azure DNS zone or is it some internal domain name?
... View more
11-15-2023
02:51 AM
|
0
|
0
|
288
|
BLOG
|
Love it. I see that they it is available as a PDF but I think if we can print them onto the standard Poker card size that would be great. I know, that with a pair of scissors and glue; one can do it yourself but who doesn't love opening up a new pack of cards? Reminds me of my Magic: The Gathering days....
... View more
12-10-2018
03:12 AM
|
1
|
0
|
332
|
POST
|
I got this to work with AWS RDS for PostgreSQL. Used Cloudformation to create RDS PostgreSQL Instance, (engine 9.4.5). Used PGADMIN tool to ensure that the newly created DB was working as intended. Followed the instructions on Create a geodatabase on Amazon Relational Database Service for PostgreSQL—ArcGIS for Server (10.4) | ArcGIS for Server Step 5 -- for some reason, the newly created SDE user could not own the schema (SDE) so I went to the login role for SDE and edited the privileges to include 'create database' and it all worked. I did not create a new user but just used the SDE user to load data. I know not good but this was an initial test to ensure that all the parts worked. Did not register the DB with ArcGIS Server. Just used desktop to directly connect to the RDS. Successfully imported 10GBs of featureclasses. Haven't tried to apply RDS snapshots etc; however -- performance is quite impressive. Good luck. Ming
... View more
07-28-2016
06:08 AM
|
1
|
1
|
2693
|
Title | Kudos | Posted |
---|---|---|
1 | 4 weeks ago | |
1 | 02-08-2024 08:49 AM | |
2 | 02-08-2024 12:47 AM | |
1 | 07-28-2016 06:08 AM | |
1 | 12-10-2018 03:12 AM |