locked
Microsoft Project has stopped working RRS feed

  • Question

  • Hi

    My Project 2016 has stopped working. I cannot start it.

    • I have repaired it via Uninstall > Change > Repair online
    • I have uninstalled entire Office Pro Plus as well as Project 2016, and then reinstalled. Same result.

    Event viewer log says:

    Faulting application name: WINPROJ.EXE, version: 16.0.9126.2098, time stamp: 0x5ab005a0
    Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5aac7dad
    Exception code: 0x010d5840
    Fault offset: 0x00000000001cd673
    Faulting process id: 0x738
    Faulting application start time: 0x01d3c13c878d09ad
    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\WINPROJ.EXE
    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
    Report Id: aa30d706-be2e-47e9-ac3a-e60997ddcb45
    Faulting package full name: 

    Only information I found on the internet were this link: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_project-mso_win10-mso_2016/ms-project-2016-fails-to-start-on-windows-10/23970075-9e28-4a20-82be-d57de81c404e

    I then Googled the string: Faulting module name: mso20win32client.dll, and found 2 files located at:

    1. C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX86\Microsoft Shared\OFFICE16\mso20win32client.dll
    2. C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\mso20win32client.dll

    However there were NO mso20win32client.dll on filepath from error message: C:\Program Files\Common Files\Microsoft Shared\Office16\

    I really have no clue if this is out of the ordinary, or why a 32-bit dll client is somehow related to my Win 10 Pro 64-bit installation, and all Office installations are 64-bit as well.

    Please help.


    • Edited by jensjakobsen Wednesday, March 21, 2018 6:11 PM Spelling error
    Wednesday, March 21, 2018 6:11 PM

Answers

  • I called MS support. I checked two of my clients endpoints. The one that is not working has the latest build (released two days ago) 9126.2098. My other client, who is still functional is on a build that is a month old. Therefore a new update broke it. He told me all I can do is roll back for now.

    I followed their roll back instructions, in my case I had 365.

    1. Open cmd as admin then: cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun

    2. enter

    3. Paste in officec2rclient.exe /update user updatetoversion=16.0.8431.2215 

    Note: the 16.0.8431.2215 is the build that is working for my other user. You can insert whatever you want there.

    • Edited by CentrexIT Thursday, March 22, 2018 10:00 PM
    • Proposed as answer by IPTJosh Friday, March 23, 2018 11:01 AM
    • Marked as answer by jensjakobsen Wednesday, March 28, 2018 10:41 PM
    Thursday, March 22, 2018 9:35 PM

All replies

  • My clients are reporting the same issue. All of them lost access to project at the same time. Is this a global issue with Project 365?

    Note in this instance the client is Win 7 Pro with 32 bit installations.

    • Edited by CentrexIT Wednesday, March 21, 2018 11:20 PM
    Wednesday, March 21, 2018 11:19 PM
  • Same issue only thing that worked to get it working again for me was to roll back to the previous version of office

    Thursday, March 22, 2018 4:29 PM
  • I really really really hope a forum moderator will answer this :(
    Thursday, March 22, 2018 6:36 PM
  • I called MS support. I checked two of my clients endpoints. The one that is not working has the latest build (released two days ago) 9126.2098. My other client, who is still functional is on a build that is a month old. Therefore a new update broke it. He told me all I can do is roll back for now.

    I followed their roll back instructions, in my case I had 365.

    1. Open cmd as admin then: cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun

    2. enter

    3. Paste in officec2rclient.exe /update user updatetoversion=16.0.8431.2215 

    Note: the 16.0.8431.2215 is the build that is working for my other user. You can insert whatever you want there.

    • Edited by CentrexIT Thursday, March 22, 2018 10:00 PM
    • Proposed as answer by IPTJosh Friday, March 23, 2018 11:01 AM
    • Marked as answer by jensjakobsen Wednesday, March 28, 2018 10:41 PM
    Thursday, March 22, 2018 9:35 PM
  • Glad you got it working.  Two points to note.

    1. The forum moderators typically know a lot about the functionality of MS Project, but not about the specifics of Click to Run or of why a certain build might not work.  We don't work for Microsoft...

    2. My version is 9126.2098 (32-bit), running on Windows 10, and is working fine, so this isn't a global problem.  Though this is no consolation to you, it might narrow the issue down to Windows 7


    Ben Howard [MVP] | web | blog | book | downloads | P2O

    Thursday, March 22, 2018 10:08 PM
  • We have 16.0.9126.2098 running on Win 10 and have the problem on multiple machines. The rollback to 16.0.8431.2215 gets us running again.
    Friday, March 23, 2018 11:04 AM
  • Log Name:      Application
    Source:        Application Error
    Date:          3/23/2018 7:17:17 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    Faulting application name: WINPROJ.EXE, version: 16.0.9126.2072, time stamp: 0x5aa71b2d
    Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5aa6e4e7
    Exception code: 0x010d5840
    Fault offset: 0x00152808
    Faulting process id: 0x3050
    Faulting application start time: 0x01d3c2b1a5114938
    Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\WINPROJ.EXE
    Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll
    Report Id: 13e39603-3010-478f-97cf-bb3965c01e5e
    Faulting package full name: 
    Faulting package-relative application ID: 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2018-03-23T14:17:17.828647400Z" />
        <EventRecordID>17872</EventRecordID>
        <Channel>Application</Channel>
        <Computer>RD082016.Unicep.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WINPROJ.EXE</Data>
        <Data>16.0.9126.2072</Data>
        <Data>5aa71b2d</Data>
        <Data>mso20win32client.dll</Data>
        <Data>0.0.0.0</Data>
        <Data>5aa6e4e7</Data>
        <Data>010d5840</Data>
        <Data>00152808</Data>
        <Data>3050</Data>
        <Data>01d3c2b1a5114938</Data>
        <Data>C:\Program Files (x86)\Microsoft Office\root\Office16\WINPROJ.EXE</Data>
        <Data>C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll</Data>
        <Data>13e39603-3010-478f-97cf-bb3965c01e5e</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Same error as everyone else. Trying the rollback now, but I wanted to put this up for more visibility. This wiped out our entire project management and engineering teams. Does MS just not test anything anymore?

    • Proposed as answer by Fahim Solkar Monday, March 26, 2018 9:23 PM
    • Unproposed as answer by Fahim Solkar Monday, March 26, 2018 9:29 PM
    Friday, March 23, 2018 2:34 PM
  •  Please share the output of Microsoft Office Configuration Analyzer Tool 2.2 and share it and also the winver output to know Windows build version details. 

    Monday, March 26, 2018 9:28 PM
  • THANKS IPTJosh, it worked for me!

    I'm running a Win 10 Pro 64bit and a Office Pro Plus 64bit as well. And Project 2016 clicktorun 64bit.

    Thanks again!

    Wednesday, March 28, 2018 10:41 PM