Latest Contributions by DustinHobbs

‎04-12-2018

Hi Ross, While I cannot guarantee that a full re-install will not be required the following may assist in the recovery of the environment. Ideally, these edits should ONLY be made from the portaladmin endpoint, but if you cannot reach that endpoint this may help. Stop the Portal for ArcGIS Service. Navigate to C:\arcgisportal\content\items\portal directory Edit the portal-config.properties file Remove/delete the webcontext.url entry at the bottom of the file. Save the edits to the portal-config. properties file Start the Portal for ArcGIS Service. From here you should be able to access the portaladmin endpoint, which will allow you to reconfigure the WebContext URL. This should ONLY be used as a last effort to recover the Portal for ArcGIS environment. The aforementioned file should not be used to make edits to the Portal for ArcGIS environment. The portaladmin endpoint should be used instead. I hope this helps. If you have problems beyond this the recommendation would be to reach out to Esri Support Services for additional assistance.

‎01-10-2018

Greetings Ahmad, In the version 10.3.1 when someone updated the WebContextURL from PortalAdmin that value was saved to an internal database. If the wrong value was entered for the WebContextURL, essentially the referrer value for proxying request would also be wrong. This is the reason users would not be able to access Portal for ArcGIS endpoints. Also, because the value was saved to an internal database the only way to recover from this problem was to reinstall Portal for ArcGIS. This problem has been addressed in the more recent versions of Portal for ArcGIS.

‎10-07-2015

Hi Huke, I've seen this error message before. Unfortunately to resolve this error message required a clean install of Portal for ArcGIS.

‎10-07-2015

Hi Darko, Ideally, you wouldn't make any update to the WebContextURL within Portal. Majority of the issues when you have to update the WebContextURL is actually fixed by completing the workflow I previously mentioned. This is also why I recommended removing the WebContextURL and completing this workflow. From Portaladmin endpoint navigate to the following location: Click on System --> Web Adaptors --> Click on the Machine name Next in the Address Bar at the end of the URL enter /edit Update the Web Adaptor URL to point to your Reverse Proxy address. Typically this will be https://reverseproxy/webadaptor Click Edit Web Adaptor Now if you are getting an HTTP 404 tells me that we're failing to reach the resource. This is most likely because of the update with the WebContextURL. Now the problem is we can longer access any of the endpoints to make the changes required. If we could access the internal database for Portal for ArcGIS we maybe able to make an update to recover from the problem. Unfortunately, there is currently not a documented workflow to do such. Therefore, I'm afraid you may have to re-install Portal for ArcGIS.

‎10-06-2015

Hi Philip, Can you access any of the other endpoints? Home and Sharing? Have you tried to access the portal using the port number https://localhost:7443/arcgis/portaladmin If sharing doesn't load then this points to some problem accessing the Portal PostgreSQL Database

‎09-30-2015

Hi Håvard, I would recommend trying the following if you haven't already contacted Esri Support Services. Open an Administrative Command Prompt Change directories (cd) to the following location C:\Program Files\ArcGIS\Portal\tools\accountmanagement Run the CreateAdminAccount.bat. This will create a new admin account for Portal. Next I would connect to the Portal for ArcGIS Admin endpoint (portaladmin) Click on System Click on Indexer Click on Reindex Change the Mode to Full Click on the Reindex button. This will Reindex the internal database built within Portal for ArcGIS. If you do this and it continues to fail then I would definitely reach out to Esri Support Services. I hope this information helps.

‎09-30-2015

Hi Dan, This is actually something my colleagues and I just came across. What we found is the default URL Rewrite in ARR is set to redirect traffic to http:// To avoid the 302 Loop in our environment we had to update the URL Rewrite rule to redirect to https://. Once we did this the 302 Loop was avoided. The other thing that we found we could do to avoid this was to complete the following: (1) Log into the portaladmin (2) Click on System (3) Click on Web Adaptors (4) Click on oursite.domain.com hyperlink (5) In the address bar append /edit to the URL (6) Update the Web Adaptor URL so that it's using the DNS alias for the Portal site. Typically this is defaulted to the internal name of the server when the web adaptor was first configured. Essentially this will white-list the URL for Portal and will prevent the 302 Loop as well. I hope this information helps.

‎09-30-2015

Hi Dave, If you want to leverage Portal Authentication and Active Directory Users this would be possible. The biggest piece is where are the individuals authenticating. To do this I would complete the following: (1) Configure Portal for ArcGIS for AD Users. (2) Configure Portal for ArcIGS for AD Groups. (OPTIONAL). (3) Install and configure the ArcGIS Web Adaptor for Portal for ArcGIS. (4) Ensure that the authentication for the Portal Web Adaptor is set to Anonymous Authentication. This way when end users connect to the Portal for ArcGIS they will have to click the Sign-in. If the user has a built in account they'll simply need to provide their credentials. If the user has a domain account then they would need to enter their credentials. Typically domain credentials will be in the format of UPN or username@domain. Please note that the username and password are case sensitive. I hope this information helps.

‎08-27-2015

Hi Stephen, What I would recommend is log into the PortalAdmin and remove the updated WebContextURL. Next I would complete the following From Portaladmin endpoint navigate to the following location: Click on System --> Web Adaptors --> Click on the Machine name Next in the Address Bar at the end of the URL enter /edit Update the Web Adaptor URL to point to your Reverse Proxy address. Typically this will be https://reverseproxy/webadaptor Click Edit Web Adaptor Once that is complete you should be able to access all the Portal for ArcGIS endpoints (Home, PortalAdmin, Sharing). I hope this information helps.

‎07-06-2015

Hi Lars, I know that if you have a self-signed certificate ArcGIS Pro will not connect to Portal as it cannot trust the certificate. You could however, be running into a certificate mismatch issue. You could use Fiddler to confirm this to be true. Do you use a DNS alias for Portal? If so when you registered the web adaptor did you use the machine name or the DNS alias. If you used the machine name then you'll want to complete the following steps and test further. (1) Log into the Portal Admin endpoint (https://servername.domain.com/webadaptor/portaladmin (2) Click on System --> Web Adaptors --> machine name (3) In the address bar go to the end of the URL and add /edit (4) On the next page under Web Adaptor URL update this value to reflect the DNS alias Example: https://megaman.esri.com/portal (5) Click Edit Web Adaptor Once this is complete every Portal URL request will reference the DNS alias instead of the internal machine name. Hope this helps.

‎07-06-2015

Hi Lars, Another thing that you may try is the following: Open Internet Explorer on the system where Portal is Installed. Type the following http://servername.domain.com:27000 If it returns the image below then you know that it's not a problem reaching the port. If it returns a "Page cannot be displayed" error then you know the port is not accessible. I know this may not answer the question but it's a troubleshooting step at the least. Hope this helps.

‎06-30-2015

Greetings Rick, The Portal Security is actually not stored within a flat file. Instead it is held within a PostgreSQL database. It sounds as if you have automatic account creation enabled. Therefore, the end user account that is created is Portal data and not ArcGIS Server data. If you were to federate ArcGIS Server with Portal you'd have the following benefits: The server and the portal share the same user store (that of the portal). This results in a convenient single sign-on experience. Your existing ArcGIS Server services are automatically shared as portal items. Any subsequent items you publish to the server are automatically shared on the portal. You can optionally allow the server to host cached maps, feature services, and scene services (tile layers, feature layers, and scene layers) published by users of the portal. Additional information about federation can be found at the following link: Federating an ArcGIS Server site with your portal—Portal for ArcGIS (10.3 and 10.3.1) | ArcGIS for Server Lastly the link between Portal Groups and Active Directory Groups is also stored within the PostgreSQL database. You could think of it as a redirect. You created the group in Portal but it's actually being redirected to the Active Directory group. I hope this information helps.

‎06-29-2015

When was the Portal for ArcGIS Installation downloaded? When Portal 10.3 was originally released there was a bug with the installer that created this exact scenario. This has since been fixed. However, if you downloaded the installation on or around 12/17/14 you most likely downloaded the problem. I would recommended re-downloading the installation and running through the installation process again.

‎06-24-2015

Greetings Andy, As you've already stated technically Ubuntu is not one of the supported Operating Systems for an ArcGIS Server Linux install. Please see the link below: System requirements—Installation Guides (10.3 and 10.3.1) | ArcGIS for Server I do agree with Danny that most likely you are simply missing a package. The above link will also supply a list of packages as well for the supported versions. This will probably add some insight to the missing packages for your Ubuntu instance. I hope this information helps.

‎06-24-2015

Shafi, If you could please clarify your question? I understand that you are using the WAB Developer addition and have it deployed to your web server. I guess I'm confused on your concern with named users. With this type of configuration named users would not come into play unless the ArcGIS Server, where the map services are being consuming from, is federated with Portal for ArcGIS.

Online Status	Offline
Date Last Visited	‎11-07-2022 06:54 PM

My Ideas

Latest Contributions by DustinHobbs

Re: Portal 10.3 Configuration Settings

Re: Portal 10.3 Configuration Settings

Re: Portal 10.3 Configuration Settings

Re: Portal 10.3 Configuration Settings

Re: Portal 10.3 Configuration Settings

Re: Corrupt admin account / Portal installation?

Re: Access Portal for ArcGIS through IIS ARR rule?

Re: Configure Portal with Portal authentication and Active Directory

Re: Portal 10.3 Configuration Settings

Re: Portal governing Pro licenses not working.

Re: Portal governing Pro licenses not working.

Re: Where is Portal security data stored?

Re: No site after installation of ArcGIS Portal 10.3 on Redhat Linux 6.5

Re: ArcGIS Server 10.3 - Could not create object 'ConfigurationFactory'

Re: Arcgis Enterprise security

Re: Portal 10.3 Configuration Settings

Re: Corrupt admin account / Portal installation?

Re: Access Portal for ArcGIS through IIS ARR rule?

Re: Configure Portal with Portal authentication an...

Re: Where is Portal security data stored?