locked
SharePoint Sites disappeared from IIS 8.5 RRS feed

  • Question

  • I've encountered a strange issue that I haven't being able to find the root cause, how the Root Site and MySite disappeared from the IIS but was present in Central Administration. 

    I've a single server farm having Windows Server 2012, 16GB Ram and 2 cores and IIS 8.5. 

    When I checked the IIS history, applicationHost.config file was modified in 2 minute interval and at 2:43 site was present but at 2:45 it was not present in the history.

    Server was running on low memory and it was reported in SharePoint health analyser. When I checked the event logs, multiple entries are found in the system logs before the application crash

    [2:44:39 PM] "An ISAPI reported an unhealthy condition to its worker process. Therefore, the worker process with process id of '6540' serving application pool 'SecurityTokenServiceApplicationPool' has requested a recycle."

    [2:44:39 PM] "An administrator has requested a recycle of all worker processes in application pool 'MySites (14.01.2015 13.05.58)'."

    Application Log:-

    [2:44:44 PM this warning message appeared 820 times] “There was an error during processing of the managed application service auto-start for application pool: 'SecurityTokenServiceApplicationPool'.  Some application services may not have been processed correctly.  Please check the configuration for application service auto-start for the application(s) assigned to this application pool.  The data field contains the error code.”

    [2:44:46 PM] 

    Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96

    Faulting module name: xlsrv.dll, version: 15.0.4945.1000, time stamp: 0x593f8e42

    Exception code: 0xc0000005

    Fault offset: 0x000000000000109d

    Faulting process id: 0xcc8

    Faulting application start time: 0x01d3cdda51e9a7be

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

    Faulting module path: C:\Program Files\Microsoft Office Servers\15.0\Bin\xlsrv.dll

    Report Id: 7d188b85-4245-11e8-81b3-000c29313cbc

    Faulting package full name:

    Faulting package-relative application ID:

    System Log:-

    [2:44:46PM] “A process serving application pool '42a757967f9a479caeec8af3eba5e49f' terminated unexpectedly. The process id was '3272'. The process exit code was '0xc0000005'.”

    [2:44:46PM] “Application popup: w3wp.exe - Application Error: The instruction at 0x43c3109d referenced memory at 0x00000000. The memory could not be read.”

    Task Scheduler shows

    [2:44:46 PM] Task Scheduler launched "{00000000-0000-0000-0000-000000000000}” instance of task "\Microsoft\Windows\MemoryDiagnostic\ProcessMemoryDiagnosticEvents” according to an event trigger.

    But with these error, I'm not able correlate the thing happened on the IIS end , how the sites gone missing and how the Virtual directory for MySite disappeared from file system.

    Although I've recovered the sites from backup but still need to create RCA and I've no clue how to proceed, where to look now. Any help would be appreciated. Thanks.

     


    Best Regards,
    Brij K
    http://bloggerbrij.blogspot.co.uk/

    Friday, April 20, 2018 11:44 AM

Answers

  • The proper way to recover from this is to stop the Microsoft SharePoint Foundation Web Application service instance and restart it. That will properly provision the IIS sites/vdirs/app pools.

    It certainly does look like a low memory condition caused a cascade of errors. It might be time to either look at bringing in a 2nd server for load balancing or scaling up your existing server.


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Proposed as answer by Sara Fan Monday, April 23, 2018 1:09 AM
    • Marked as answer by Brij K Tuesday, May 1, 2018 10:06 AM
    Friday, April 20, 2018 2:43 PM

All replies

  • The proper way to recover from this is to stop the Microsoft SharePoint Foundation Web Application service instance and restart it. That will properly provision the IIS sites/vdirs/app pools.

    It certainly does look like a low memory condition caused a cascade of errors. It might be time to either look at bringing in a 2nd server for load balancing or scaling up your existing server.


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Proposed as answer by Sara Fan Monday, April 23, 2018 1:09 AM
    • Marked as answer by Brij K Tuesday, May 1, 2018 10:06 AM
    Friday, April 20, 2018 2:43 PM
  • Hi Brij K,

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, April 23, 2018 1:09 AM
  • Hi Sara,

    Thanks Trevor for the proper resolution. But my problem is to find out how the Virtual directory for MySite disappeared from file system. Is it also related to the low memory problem. 

    Regards,

    Brij


    Best Regards,
    Brij K
    http://bloggerbrij.blogspot.co.uk/

    Tuesday, April 24, 2018 8:10 AM
  • Can't say for certain why it occurred. This would take time to review logs. Not something we're equipped to do via these forums.

    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Proposed as answer by Sara Fan Monday, April 30, 2018 9:42 AM
    Tuesday, April 24, 2018 2:16 PM