Publishing a Service Error - ServerHealthCheckTask

DejanPopovic4 · ‎12-17-2018

I'm having a problem sharing a service via ArcMap and generally accessing REST services.

Configuration:

ArcGIS for Server Version 10.5.1 runs as Windows Service (port: 6080)
WebAdaptor Version 10.5.1 runs on Tomcat as war File (forwards from port 6080 to port 6443).
Windows 10 Pro

I receive following error in Tomcat when Web Adaptor is running:

NOTE: (Fehler in Admin-Anforderung für Abruf von Computern Connection refused - from German: Error in Admin Request at call from Computer Connection refused)

17-Dec-2018 09:35:01.044 WARNUNG [Timer-0] com.esri.arcgis.server.wa.cluster.UpdateServerCacheTask.updateServerList Exception in connecting to http://localhost:6080/arcgis/admin Fehler in Admin-Anforderung für Abruf von Computern Connection refused: connect
17-Dec-2018 09:35:02.060 WARNUNG [Timer-0] com.esri.arcgis.server.wa.cluster.UpdateServerCacheTask.updateServerConfig Exception in connecting to http://computername.domain.LOCAL:6080/arcgis/admin Fehler in Admin-Anforderung für Abruf von Computern Connection refused: connect
17-Dec-2018 09:35:03.075 WARNUNG [Timer-0] com.esri.arcgis.server.wa.cluster.UpdateServerCacheTask.updateServerConfig Exception in connecting to https://computername.domain.LOCAL:6443/arcgis/admin Fehler in Admin-Anforderung für Abruf von Computern Connection refused: connect
17-Dec-2018 09:35:09.545 INFORMATION [Timer-4] com.esri.arcgis.server.wa.cluster.ServerHealthCheckTask.updateServerStatus Checking Healthcheck status for hostname : computername.domain.LOCAL
17-Dec-2018 09:35:10.564 INFORMATION [Timer-4] com.esri.arcgis.server.wa.cluster.ServerHealthCheckTask.updateServerStatus Healthcheck status for hostname : computername.domain.LOCAL false
17-Dec-2018 09:35:19.549 INFORMATION [Timer-4] com.esri.arcgis.server.wa.cluster.ServerHealthCheckTask.updateServerStatus Checking Healthcheck status for hostname : computername.domain.LOCAL
17-Dec-2018 09:35:20.565 INFORMATION [Timer-4] com.esri.arcgis.server.wa.cluster.ServerHealthCheckTask.updateServerStatus Healthcheck status for hostname : computername.domain.LOCAL false

I followed the steps to install AGS (ArcGIS for Server) and webadaptor again (Install ArcGIS Server on one machine—Installation Guides (10.5) | ArcGIS Enterprise ).

As a results, webadaptor is running, but shows the following error when trying to register

Error: Could not access any GIS Server machines. Please contact your system administrator

I followed the steps in the answer and it doesn't help.

Although I don't have agsusers and agsadmin group but I have enabled settings for local users and admin (account from which AGS and webadaptor were installed)from following thread.

Error: Access Denied or The connection could not be made

The services in AGS are not responding when webadaptor is running. When I restart PC, AGS is running, and all Publishing Service, however when I try to share service using AcMap, it says that is not being started.

I followed following thread to find try to solve:

User does not have permissions to access 'system/publishingtools.gpserver

I tried both connecting to AGS via:

http://localhost:6080/arcgis

and

https://computername.domain.LOCAL:6443/arcgis or https://localhost:6443/arcgis/
to publish service and it always responds that Publishing Service is not running.

Ports: 6080,6443 are opened for AGS at Windows Firewall and I use only admin account for log in at AGS.

Summary:

AGS and webadaptor, once the PC is restarted work fine, however once I try to publish service everything crashes.

Any help is highly welcome!

Dejan

JonathanQuinn · ‎12-17-2018

On the WA machine, can you reach https://computername.domain.LOCAL:6443/arcgis/rest/info/healthCheck? That's a health check URL and you can verify whether the WA can reach that endpoint.

DejanPopovic4 · ‎12-18-2018

Yes, once I started machine (for example now), I entered healthCheck link it responds:

---------------------------------------------------------------

Server Health Check

Health Check successful, the site is ready

In Tomcat it responds:

18-Dec-2018 09:33:30.209 INFORMATION [Timer-5] com.esri.arcgis.server.wa.cluster.ServerHealthCheckTask.updateServerStatus Healthcheck status for hostname : computername.domain.LOCAL true

---------------------------------------------------------------

Now I try to publish a Service from ArcMap using connection arcgis on localhost 6443, in Service-Editor

when Analyze is clicked, no Error messages were shown, however when I click Publish, it pops up following error:

Error: The server is not ready for publishing. Please check if the Publishing Tools on the server ar...

In Tomcat I keep receiving:

18-Dec-2018 10:20:30.267 WARNUNG [Timer-4] com.esri.arcgis.server.wa.cluster.UpdateServerCacheTask.updateServerConfig Exception in connecting to https://computername.domain.LOCAL:6443/arcgis/admin Fehler in Admin-Anforderung für Abruf von Computern Permission denied: connect
18-Dec-2018 10:20:30.268 WARNUNG [Timer-4] com.esri.arcgis.server.wa.cluster.UpdateServerCacheTask.updateServerConfig Exception in connecting to http://computername.domain.LOCAL:6080/arcgis/admin Fehler in Admin-Anforderung für Abruf von Computern Permission denied: connect

Although I can access arcgis manager via Browser, all System services and Services (that were being published before) are not active anymore. When I try to restart,e.g Publishing Tool, the execution never ends (it's been 2 hours already)

(PS: sometimes it pops up following error: Error while starting AppServer. Required port '4000' already in use.)

What I have restarted ArcGIS Service and I cannot access arcgis manager nor healthCheck link anymore. With help of TCPView, I see the following:

with cmd, try to find Ports: 6080 and 6443 but I don't get any response

I am a bit confused, since I am not quite sure if it has something to do with webadaptor or admin right are missing somewhere. I also try without webadaptor to publish services (using port 6080) but it didn't worked.

DejanPopovic4 · ‎02-25-2019

We ended up contacting esri support DE. Thanks to their help, after few tries, we finally found what intercepts connection between ArcGIS Server and local machine.

Each time when our machine was connected with CISCO Any Connect Client the local domain name was anymore longer forwarding to local IP Adress, whether it was overwritten by IP Adress from CISCO Client connected Server, therefore comes the following ERROR message:

http://computername.domain.LOCAL:6080/arcgis/admin Fehler in Admin-Anforderung für Abruf von Computern Permission denied: connect

The problem was indicating that machine name was not actually recognized by ArcGIS Server because it was wrong IP adress behind. Hence all system and created services were shuted down, both with webadaptor or without while we were connected with CISCO AnyConnect.

NOTE: without VPN Cisco AnyConnect connection, everything on ArcGIS Server was working perfectly.

Moreover with tried explicitly to define our local IP adress in hosts File (Error: Could not access any GIS Server machines. Please contact your system administrator ), but somehow the hosts file was being listened.

We also tried adapting TCP/IP settings, but it also didn't work.

We contacted our Service Provider to check CISCO AnyConnect Split Tunneling settings. That was not the case also.

(temporary solution)

Finally with our suggestion and guidance from esri support, we were able to explicitly change the local machine name to our local IP adress:

ArcGIS Server Administrator Directory: Home > machines > rename

That means that webadaptor has to be configured again and certificate for new name (local ip adress) also.

I would also recommend to publish again all map services via new webadaptor configured link.

That means, that ArcGIS for Server worked while VPN Client connection were being established.

(longterm solution)

Generally it is not good that local machine IP adress during VPN Connection is being overwritten. Then all programs that request local domain name will not functioning.

We are at the moment looking into long term solution with help from our Network Admin, VPN Service Provider and probably we will involve also CISCO support, but this is definitely out of scope in this regarding issue.