none
Sharepoint 2016 - Stoppped working after windows update RRS feed

  • Question

  • Hi, 

    Any help with this would be really appreciated. As far as I can see, Sharepoint stopped working after a windows update. If I attach a debugger to the w3wp.exe I see the following error: 

    Unhandled exception at 0x00007FFF15B295FC (KernelBase.dll) in w3wp.exe: 0xC06D007E: Module not found (parameters: 0x000000036D7EE9C0).

    And 

    Exception thrown at 0x0000000000000000 in w3wp.exe: 0xC0000005: Access violation executing location 0x0000000000000000.

    If there is a handler for this exception, the program may be safely continued.

    When I look in the event log I see: 

    Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f33794
    Exception code: 0xc06d007e
    Fault offset: 0x00000000000095fc
    Faulting process id: 0xe4c
    Faulting application start time: 0x01d37281d06708f8
    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 0e519386-de75-11e7-80d6-00155d0047b3
    Faulting package full name: 
    Faulting package-relative application ID

    And 

    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: w3wp.exe
    P2: 8.5.9600.16384
    P3: 5215df96
    P4: KERNELBASE.dll
    P5: 6.3.9600.18666
    P6: 58f33794
    P7: c06d007e
    P8: 00000000000095fc
    P9: 
    P10: 

    Attached files:

    These files may be available here:


    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 0bbac721-de75-11e7-80d6-00155d0047b3
    Report Status: 0
    Hashed bucket: 

    When I try to run the configuration tool, I get the following errors: 

    The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.
    Could not read the XML Configuration file in the folder 16\CONFIG\PowerShell\Registration\.
    Could not find a part of the path 'C:\Windows\system32\16\CONFIG\PowerShell\Registration'.
    No xml configuration files loaded.
    Unable to register core product cmdlets.
    Could not read the Types files in the folder 16\CONFIG\PowerShell\types\.
    Could not find a part of the path 'C:\Windows\system32\16\CONFIG\PowerShell\types'.
    "No Types files Found."
    Could not read the Format file in the folder 16\CONFIG\PowerShell\format\.
    Could not find a part of the path 'C:\Windows\system32\16\CONFIG\PowerShell\format'.
    No Format files Found.

    Any ideas of why SharePoint would really be appreciated. I am just stuck. 

    Best regards, 

          Seamus 


    Monday, December 11, 2017 1:30 PM

Answers

  • Did you check if SharePoint updates are part of windows update? may be runt he config wizard on SharePoint servers

    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -Waqas Sarwar(MVP) Blog: http://krossfarm.com

    Monday, December 11, 2017 2:12 PM
    Moderator

All replies

  • Did you check if SharePoint updates are part of windows update? may be runt he config wizard on SharePoint servers

    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -Waqas Sarwar(MVP) Blog: http://krossfarm.com

    Monday, December 11, 2017 2:12 PM
    Moderator
  • Hi

    Can check if the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Location" points to the right place.

    More details refer to 

    https://www.dmcinfo.com/latest-thinking/blog/id/9357/sharepoint-2016-forgets-where-its-installed-after-update

    Monday, December 11, 2017 4:07 PM
  • Yes, one of the servers had an update and the other did not. Once it was installed on the second server, SharePoint is now working. Thanks for your help. 
    Wednesday, December 13, 2017 2:02 PM
  • This is happening way too often and our sites are down until I add the registry entry again.

    Is Microsoft aware of this bug and are they going to fix it?


    Matthew Barrett Concept Interactive Inc.

    Thursday, May 24, 2018 4:28 PM