topic Why would arcgis server be constantly be sending requests to an ip address that doesn't exist (169.254.169.254)? in ArcGIS Server with JavaScript API Questions

Why would arcgis server be constantly be sending requests to an ip address that doesn't exist (169.254.169.254)?

ThomasFurcron — Mon, 09 Oct 2017 14:17:02 GMT

Our IT manger has recently asked me this, has anyone else experienced this? It is constantly sending requests to this ip address 169.254.169.254.

Re: Why would arcgis server be constantly be sending requests to an ip address that doesn't exist (169.254.169.254)?

MattStull — Mon, 18 Dec 2017 16:28:52 GMT

I'm having this same issue but with ArcGIS Desktop. ArcMap and ArcCatalog won't open. When I try to open them, the splash screen appears and then it doesn't go away and the mouse cursor just has that spinning wheel. Sometimes ArcMap or ArcCatalog will open but only after a long wait. Are you having that happen as well? Did you find a solution?

Re: Why would arcgis server be constantly be sending requests to an ip address that doesn't exist (169.254.169.254)?

MattStull — Mon, 18 Dec 2017 16:29:23 GMT

My IT staff said it was making the calls to 169.254.169.254 IP address.

Re: Why would arcgis server be constantly be sending requests to an ip address that doesn't exist (169.254.169.254)?

ThomasFurcron — Mon, 05 Feb 2018 13:51:22 GMT

Matt,

We were not having issues with ArcGIS Desktop, just server hosting our ArcGIS server and ArcGIS License Manager.

We did not find a complete fix, but I was told by ESRI support it was a know issue related to the ArcGIS License Manager. We upgraded the License Manager to a more recent release and the calls to the specific ip address were cut in half but have not gone away completely. So if your license manager is on the same machine as your arcgis desktop version that you are trying to open it may be related.

Tom

Re: Why would arcgis server be constantly be sending requests to an ip address that doesn't exist (169.254.169.254)?

MattStull — Mon, 05 Feb 2018 17:48:20 GMT

I got this issue fixed back in December! Thanks for the feedback Tom. Here are the notes I made to myself on how I fixed it: