AnsweredAssumed Answered

ArcGIS Server 10.1 SP1 Web Adaptor.config error in Event Viewer

Question asked by Colli on Apr 28, 2015
Latest reply on May 26, 2015 by Colli

Good day all,

 

Yesterday we came into work to our production server site crashing. We restarted the server service, rebooted the server, no luck. There were all sorts of errors in both the server manager logs beginning at midnight when our server recycles:  Failed to initialize service xxxxx, Underlying DBMS error, Method failed HRESULT = 0x80004005 System/publishing tools.GPServer. Never got the thing fully up until last night after multiple reboots, waited a few hours, restarts etc.

 

DB server has no errors.

 

The event viewer application logs on the GIS/web server had a bit more info, but they occurred a few hours after the GIS logs indicated a major issue. We are seeing a tandem of errors that are occurring together within a few seconds of each other.

 

First we see:

An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/2/ROOT/arcgis

Process ID: 19320

Exception: System.IO.IOException

Message: The process cannot access the file 'D:\Sites\MapViewer\arcgis\WebAdaptor.config' because it is being used by another process.

 

Second is:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2

Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677

Exception code: 0xe0434f4d

Fault offset: 0x000000000000940d

Faulting process id: 0x4b78

Faulting application start time: 0x01d080fcddbcfaf8

Faulting application path: c:\windows\system32\inetsrv\w3wp.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: de1cc55d-ecf3-11e4-8c45-005056895439

 

Seems as though the web adaptor is misbehaving. Looking back, this has been happening for a few months now even though the server has been stable and very responsive.

 

I wanted to see if anyone has experienced this same problem or had any insight. Of course this is all happening while we are upgrading our beta to 10.3 which has gone fairly well with the exception of the... web adaptor! so needless to say, I'm pretty much done with web adaptor issues, albeit different ones. 

 

Perhaps this will just continue on our production 10.1 SP1 environment for the next month until we can upgrade and played no part in our crash. In either case I'd like to get a better understanding of the underlying cause.

 

Cheers,

Outcomes