locked
Word crashes, error with ntdll.dll, published via App-v and Office 2016 packaged with Deployment tool RRS feed

  • Question

  • Hi,

    I am working on it for days but not able yet to find a solution. I have packaged Office 2016 with The Office Deployment Tool (officedeploymenttool_6612-6353.exe). That was even hard but ok, was able to find a solution.

    Now when I publish Office 2016 to my VM, all applications works fine except Word. You can work with it, open existing files but as soon as I click the browse or save as function, Word crashes immediately and closes Word. This is the error:

    Faulting application name: WINWORD.EXE, version: 16.0.6741.2017, time stamp: 0x56e712e4
    Faulting module name: ntdll.dll, version: 6.3.9600.18202, time stamp: 0x569e72c5
    Exception code: 0xc0000374
    Fault offset: 0x000e6054
    Faulting process id: 0x954
    Faulting application start time: 0x01d18451b672ae01
    Faulting application path: C:\ProgramData\Microsoft\AppV\Client\Integration\EB51A3D4-B87F-4676-AD01-5D583ABE053C\Root\Office16\WINWORD.EXE
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 0acf244b-f045-11e5-80d0-00155d37ee00
    Faulting package full name: 
    Faulting package-relative application ID: 

    So it keeps complaining about the ntdll.dll. I don't see that dll file in the virtual package. It is there on the local file system.

    Suggested fixes like deleting a security update or renaming a registry fix are not relevant for me since it's an App-V package.

    Any help would really be apprecaited because I really can't find a solution at the moment.

    The VM is completely updated and also tried another fresh VM. Same problems.

    Thanks!


    Tuesday, March 22, 2016 3:53 PM

All replies

  • Try upgrading the App-V client to the latest HotFix.

    https://support.microsoft.com/en-us/kb/3139245


    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Tuesday, March 22, 2016 6:18 PM
  • Thanks for your reply, unfortunately that didn't help. I updated app-v on the vm and the App-v server itself. Restarted both servers and also removed and re-added the package.

    Any other ideas?

    Thanks.

    Wednesday, March 23, 2016 7:25 AM
  • Have you tried Procmon to trace the issue?

    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Wednesday, March 23, 2016 7:40 AM
  • I am a little further, when I publish the app to the user only instead to the whole vm, so without the -Global parameter but with the -UserSid parameter, it works perfectly. So maybe that helps a little.

    I just started procmon, set a filter on ntdll.dll and got these two screenshots. One from the faulting server so with the -Global parameter and one VM with the -UserSid parameter. Looks like there is not much difference:

    Faulting server procmon overview:
    http://prntscr.com/aiugn6

    Working server with procmon overview:
    http://prntscr.com/aiugql

    I will keep looking in the meantime but hopefully you can keep pointing me in the right direction :)

    Thanks so far


    Wednesday, March 23, 2016 8:59 AM
  • Looks like the ntdll.dll file is not looked up in the Windows\System32 folder but in an app-v folder. There it's not found but looks like that explorer.exe tries to create it there, but has no access. Check these screenshots:

    http://prntscr.com/aiuonm
    http://prntscr.com/aiux00

    So far I don't see that activity on the working server. I have set the same filters on both servers

    Wednesday, March 23, 2016 9:23 AM
  • NOTE:

    Office 2016 App-v package needs to be published globally.


    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Wednesday, March 23, 2016 11:03 AM
  • Well yes it works per user, but only for one user then, right?

    I still haven't find a solution to my problem. Can anyone help me?
    Thanks

    Wednesday, March 23, 2016 11:08 AM
  • Anyone?
    Thursday, March 24, 2016 2:32 PM
  • This problem still exists. Does anyone know a solution?
    Tuesday, March 29, 2016 7:19 AM
  • I am testing this in my lab. Will update you but not sooner.

    You can raise a ticket with Microsoft in mean time to find a solution.


    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Tuesday, March 29, 2016 9:01 AM
  • Great for doing that! Thanks. Waiting for your outcome :)
    Tuesday, March 29, 2016 9:08 AM