nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Log in to the server machine - why?

Sfortunatamente

I have just installed Insights for ArcGIS in a single machine environment but I am having problems with accessing the data once Workbook is being created - a login window appears and asks me for log in to the server machine - the window uses local network machine name rather than fully qualified domain name.:

Why?

My Portal uses built-in user store. We plan to integrate it with our AD. Will it solve the problem?

Thanks

Najděte více příspěvků označených jako

Accepted answers

NathanSmith8

Hi Bartlomiej Gajc‌,

Are you still encountering this issue in Insights?

To answer your questions in the above post:

1) Do NOT unfederate. You are correct, this will be very harmful to your ArcGIS Enterprise.

2) That's correct, federation requires two URL's - Service URL and Admin URL - Based on your description, you configured these properly per our doc here. (See Step 5)

All comments

JakeSkinner

Hi Bartlomiej,

Is ArcGIS Server federated with Portal for ArcGIS?

Sfortunatamente

Yes, it is.

JakeSkinner

Did you use the Fully Qualified Domain Name when you federated ArcGIS Server with Portal?

Sfortunatamente

The thing is that I was following the comments on the federating wizard window but after the process is completed I can see local network address of the federated server. It is being successfully validated but still being displayed on the list using local machine name..

So you propose to unfederate and fedarate the GIS server again? Is it harmfull for the services running on GIS server now?

Sfortunatamente

Adding ArcGIS Server to Portal requires two different links to ArcGIS site, right? Service URL - I have put FQDN there, and Administration URL - the local network machine name.

Screenshot_55.png

NathanSmith8

Hi Bartlomiej Gajc‌,

Are you still encountering this issue in Insights?

To answer your questions in the above post:

1) Do NOT unfederate. You are correct, this will be very harmful to your ArcGIS Enterprise.

2) That's correct, federation requires two URL's - Service URL and Admin URL - Based on your description, you configured these properly per our doc here. (See Step 5)

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.