ASP.NET and IIS errors on MS Azure with ArcGIS Enterprise 10.5.1 image

741
2
Jump to solution
07-18-2017 09:26 AM
AlessandroValra
Occasional Contributor III

We are trying to configure an ArcGIS Enterprise 10.5.1 on a MS Azure virtual machine. The OS is Win server 2016 with IIS 10. ArcGIS Enterprise was pre-installed on the machine (using the image available at my.esri), and ArcGIS Server and Potal are running properly on ports 6080/6443 and 7443 respectively.

It is a "single-machine" installation (only one GIS server machine/site).

Actually, we are facing the problem that http://localhost is responding with error 500. The same happens after we installed WebAdaptor accessing http://localhost/server/webadaptor.

We have an error regarding ASP.NET (see "aspnetERROR1325) and another on IIS (please see the image below).

We would need to configure properly the WebAdaptor to:

  • federate our server to the portal
  • using port 80 to provide GIS services

Another thing is that we noticed that, differently than what we were used to in previous installations, the account of the ArcGIS server is SYSTEM, not local (again, this was pre-configured in the image, we actually didn't touch that).

Does anybody have a clue about what could be wrong with the setup?

Thanks in advance for any help.

0 Kudos
1 Solution

Accepted Solutions
AlessandroValra
Occasional Contributor III

thanks for the suggestion. It did not work. Anyway, I solved installing some pending OS updates and reinstalling IIS.

View solution in original post

2 Replies
RandallWilliams
Esri Regular Contributor

I'd try dropping a web.config in the wwwroot, or if there's one already there, add or update this element:

<configuration>

   <startup>

      <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.1" />

   </startup>

</configuration>

Essentially, make sure that the .net sku is pointing to the correct version.

see:

https://forums.asp.net/t/2109026.aspx?ASP+NET+application+initialization+is+failing+on+Server+2016+I...

AlessandroValra
Occasional Contributor III

thanks for the suggestion. It did not work. Anyway, I solved installing some pending OS updates and reinstalling IIS.