none
sharepoint 2016 stopped working completely after microsoft project 2016 installation RRS feed

  • Question

  • We have installed Microsoft Project 2016 on a Sharepoint 2016 server. Everything was working fine after Microsoft Project's installation but a couple of hours later, Sharepoint, Sharepoint Central Admin, and the Sharepoint Timer Service stopped working completely. We cannot tell if the issue is related to the installation of Microsoft Project on the Sharepoint server. Below are some details for your reference:

    • When trying to start the Sharepoint Timer Service, the following error is displayed: "Error 1053: The service did not respond to the start or control request in a timely fashion". Increasing the timeout did not solve this error.
    • The event viewer shows multiple errors. One is: "The Module name SharePoint14Module path C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\isapi\owssvr.dll returned an error from registration.  The data is the error". Adding bitness64 to the applicationconfig file did not solve the issue. We have also made sure the ISAPI filters point to the 64 bit folders.
    • Second event viewer error:
    Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.18895, time stamp: 0x5a4b1cf7
    Exception code: 0xc06d007e
    Fault offset: 0x00000000000092fc
    Faulting process id: 0x3138
    Faulting application start time: 0x01d39be6e20be1f3
    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 1fe92965-07da-11e8-8112-005056ba3dd5
    Faulting package full name: 
    Faulting package-relative application ID: 

    • Third event viewer error: Note that directly before installing Microsoft Project, we checked if there are any sharepoint updates. We had the latest updates/database upgrades already installed. However, for some reason, Sharepoint started requesting database upgrades after the installation of Microsoft Project. Running Sharepoint configuration manager fails on step 2. Running the upgrade command through command prompt also fails.
    The SharePoint Health Analyzer detected a condition requiring your attention.  Databases running in compatibility range, upgrade recommended.
    The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range: 
    Secure_Store_Service_DB_b059f3dc416e4c29b7c727035aa8bb8c,
    User Profile Service Application_SocialDB_401199ed66e247d286c3d0442a52f8ce,
    Search_Service_Application_AnalyticsReportingStoreDB_d5782a8c69484a8cbd14956adcc28e96,
    Bdc_Service_DB_2e8b7efbccef445caf4d4250ba248d8a,
    SharePoint_Config,
    Search_Service_Application_CrawlStoreDB_a6a3b106f392484b994a96d3408cec29,
    AppMng_Service_DB_d27bacc8093248c6ad6f29998915c4b9,
    SharePoint_AdminContent_351592ba-f5e8-4cd4-99c9-53fe12f2af5d,
    WSS_Content,
    WSS_Content_PSA,
    Search_Service_Application_DB_49d824ebc7794cfa9655b8c071075b87,
    Managed Metadata Service_dd27a94b1fd842f98f0fc4736c95d0f4,
    User Profile Service Application_ProfileDB_eb8a335a032c4d13a72db72bcc46daac,
    WSS_Logging,
    Search_Service_Application_LinksStoreDB_55090136ee9246c89c0dc620ae719e38.
    
    To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases.  For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
    Any help is much appreciated.
    • Edited by geo_d Friday, February 2, 2018 6:19 AM
    Friday, February 2, 2018 6:04 AM

Answers

  • Hi Paul,

    Thank you for your help. There were no meaningful error messages neither in the event viewer nor in the ULS logs. We were finally able to solve the issue by running the SharePoint repair and then the sharepoint configuration wizard.

    Regards

    • Marked as answer by geo_d Monday, February 5, 2018 3:13 AM
    Monday, February 5, 2018 3:13 AM

All replies

  • Hello,

    To confirm you installed Project Server 2016 or Microsoft Project 2016 on that server?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    Saturday, February 3, 2018 3:41 PM
    Moderator
  • Project Server 2016 was already installed and fully functional. We have installed Microsoft Project 2016. After that, everything was working find until after a couple of hours.
    Sunday, February 4, 2018 4:43 AM
  • OK. It shouldn't cause any issues but typically client applications like Project , Excel etc. are not usually installed on servers. The install of Project 2016 desktop wouldn't cause updates to the SharePoint 2016 farm. Check the date of installed updates using appwiz.cpl on each of the servers in the farm - were any installed on the same date SP started requesting the DBs are updated? When running the upgrade PowerShell command, what error does it give you? What do you see in the upgrade logs?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS | MVP | Downloads

    Sunday, February 4, 2018 10:19 AM
    Moderator
  • Hi Paul,

    Thank you for your help. There were no meaningful error messages neither in the event viewer nor in the ULS logs. We were finally able to solve the issue by running the SharePoint repair and then the sharepoint configuration wizard.

    Regards

    • Marked as answer by geo_d Monday, February 5, 2018 3:13 AM
    Monday, February 5, 2018 3:13 AM