"No Portal Is Configured" after successfully registering portal

RoyCone1 · ‎03-12-2020

Hey All,

I have One machine running windows 10 with ArcGIS Server 10.7.1

https://gis.axioma-in.com:6443/

I have successfully install and configured a portal on that machine

https://gis.axioma-in.com:7443/

After doing so:

I have installed web adaptor and successfully configured it to use the server

Web adaptor name: wa

https://gis.axioma-in.com/wa/rest/services

I have installed the 2nd web adaptor named wap and try configuring it to use the PORTAL

(See 1st image)

After successful completion of the operation I am getting the error:

"No portal is configured"

when browsing to

https://gis.axioma-in.com/wap/home

(See 2nd image)

Please please please help me ... what am I doing wrong ??

Thanks ahead and best wishes

Roy

ShaneMiles · ‎03-12-2020

Ben Turrell‌ Edmund Hall, any ideas?

EdmundHall · ‎03-12-2020

Hi Roy Cone‌, Shane Miles‌,

One thing to check would be what service accounts Server and Portal were installed with, and what was used to configure Portal.

If you're not sure this can be checked by opening Services within the Windows Administrative Tools within your start menu. If you're doing a base deployment as a basic proof of concept, it may be worth considering using an account with administrator privileges within the Server and Portal installation.

When configuring Portal, it would be a good idea to ensure that the browser used is run using the same account for the Portal install, and ensure that the account has sufficient privileges to access locations such as the Portal configuration location (default is usually in C:\arcgisportal or similar), as well as the Portal installation directory which contains another configuration file (default is usually <Portal for ArcGIS installation directory>\customizations\<version number>\framework\webapps\arcgis#home\js\arcgisonline\config.js)

When initially configuring Portal, the initial URL provided after the installation completes can be pasted into a different browser instance which is opened using a 'run as' option for the a user which has appropriate permissions as above.

It may be necessary to uninstall the Portal Web adaptor, Portal installation and delete the above directories and try again.

If this has been helpful or answered you question, please mark the response to help other GeoNet users!

RoyCone1 · ‎03-19-2020

One thing to check would be what service accounts Server and Portal were installed with, and what was used to configure Portal.
If you're not sure this can be checked by opening Services within the Windows Administrative Tools within your start menu.

Roy: Sorry I am not sure of what you meant - attached some screenshots from my services

If you're doing a base deployment as a basic proof of concept, it may be worth considering using an account with administrator privileges within the Server and Portal installation.

Roy: I am only using local Administrator.

When configuring Portal, it would be a good idea to ensure that the browser used is run using the same account for the Portal install, and ensure that the account has
sufficient privileges to access locations such as the Portal configuration location (default is usually in C:\arcgisportal or similar), as well as the Portal installation
directory which contains another configuration file (default is usually
<Portal for ArcGIS installation directory>\customizations\<version number>\framework\webapps\arcgis#home\js\arcgisonline\config.js)

Roy: Checked: full control.

When initially configuring Portal, the initial URL provided after the installation completes can be pasted into a different browser
instance which is opened using a 'run as' option for the a user which has appropriate permissions as above.

It may be necessary to uninstall the Portal Web adaptor, Portal installation and delete the above directories and try again.

Roy: I've tried it ... but no luck

RoyCone1 · ‎03-19-2020

I have missed the first line:

THANK YOU for your help Sir,

RoyCone1 · ‎03-19-2020

thank you sir for your help.

Since the registration succeeded, that means that the WA can reach the portal via the URL you used in the registration process, (https://gis.axioma-in.com:7443 for example). Internally, the WA will then use that URL to see what machines are part of the site, (https://portal.domain.com:7443/arcgis/portaladmin/machines),

I don't see any machine register

and use the machine name(s) listed to send traffic to the portal. Do those machine names appear correct? This seems like an all-in-one deployment,

Roy: Yes you are right it is "All-in-one"

(everything on one machine), so it's strange that the WA can't talk to the portal machines after registration. You'd typically see this if portal and the web adaptor are on separate machines and they can't communicate with each other, (firewall, for example).

Thanks again

Roy

JonathanQuinn · ‎03-19-2020

Yikes, the machines API definitely shouldn't be empty, and that's certainly the reason why the Web Adaptor is returning that error. If this is a new portal, I'd suggest reinstalling and re-creating the site. There's no supported way to update the Machines API directly, it should be handled within the software, but for some reason wasn't.

RoyCone1 · ‎03-19-2020

Thank you Mr. Jonathan.

Hummm I don't know what to do then, I have uninstalled and reinstalled the "portal" twice by now.... all and all with the same out come ...

I am doing everything by the book and not skipping any steps,

The dev team was already add maps and information to the server...

any help will be appreciated

Thanks in advance

Roy

RoyCone1 · ‎03-29-2020

I can see the machine in the manager ....

Please, any help will be appreciate

JonathanQuinn · ‎03-13-2020

Since the registration succeeded, that means that the WA can reach the portal via the URL you used in the registration process, (https://gis.axioma-in.com:7443 for example). Internally, the WA will then use that URL to see what machines are part of the site, (https://portal.domain.com:7443/arcgis/portaladmin/machines), and use the machine name(s) listed to send traffic to the portal. Do those machine names appear correct? This seems like an all-in-one deployment, (everything on one machine), so it's strange that the WA can't talk to the portal machines after registration. You'd typically see this if portal and the web adaptor are on separate machines and they can't communicate with each other, (firewall, for example).