Running the following config:
I created an Office 2016 appstack (had to uninstall KB4487044 for provisioning). Did not start Office apps after installation.
Used the following config XML for Office installation:
<Configuration ID="e39519ba-e14b-400c-8b48-92b0ada03bdd">
<Add OfficeClientEdition="64" Channel="PerpetualVL2019" ForceUpgrade="TRUE">
<Product ID="ProPlus2019Volume">
<Language ID="nl-nl" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="OneNote" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="1" />
<Property Name="PinIconsToTaskbar" Value="FALSE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="FALSE" />
<Display Level="Full" AcceptEULA="TRUE" />
</Configuration>
When starting one of the Office apps, the following error is shown (in Dutch). Rough translation is: "An error has occurred, Excel not working properly..." Needs to be closed. Do you want to recover/repair?"
If i then choose "Nu herstellen" (Recover/Repair), all Office applications start working without issues.
Does anyone have any idea how to fix this?
Looking at file cv_startup_postsvc.log the following is logged, including an ospprearm error:
Anyone have any clue?
019-03-12 10:59:26.638 svoffice Windows 10 Enterprise LTSC 2019 6.3.17763 64-bit
2019-03-12 10:59:26.640 svoffice Logon start
2019-03-12 10:59:26.640 svoffice Waited 0,009 seconds for log file lock
2019-03-12 10:59:26.648 svoffice Built on 2018-11-30 at 07:19:41 UTC
2019-03-12 10:59:26.651 svoffice AppCloaking is off
2019-03-12 10:59:26.659 svoffice {0000538b-0000-0000-0000-100000000000} App volume
2019-03-12 10:59:26.663 svoffice {899b078c-0000-0000-0000-602200000000} Writable volume (system)
2019-03-12 10:59:26.665 svoffice PostProvision log start
2019-03-12 10:50:08.022 svoffice Windows 10 Enterprise LTSC 2019 6.3.17763 64-bit
2019-03-12 10:50:08.061 svoffice Built on 2018-11-30 at 07:19:41 UTC
2019-03-12 10:50:08.061 svoffice PostProvision start
2019-03-12 10:50:08.065 svoffice AppCloaking is off
2019-03-12 10:50:08.098 svoffice {4e05e36a-0000-0000-0000-100000000000} App volume
2019-03-12 10:50:09.093 svoffice No MSOffice products on the system volume
2019-03-12 10:50:09.136 svoffice Wrote C:\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\OfficeTokens\tokens.spp.dat
2019-03-12 10:50:09.139 svoffice Find licenses
2019-03-12 10:50:09.267 svoffice Found 22 licenses
2019-03-12 10:50:09.268 svoffice Found 1 product on the AppStack:
2019-03-12 10:50:09.274 svoffice ProPlus2019Volume 2016-64 2019-03-12 09:43:32 UTC 16.0.10341.20010
2019-03-12 10:50:09.275 svoffice Access 2016-64 2019-03-12 09:43:40 UTC
2019-03-12 10:50:09.276 svoffice Excel 2016-64 2019-03-12 09:43:39 UTC
2019-03-12 10:50:09.276 svoffice Lync 2016-64 2019-03-12 09:43:39 UTC
2019-03-12 10:50:09.276 svoffice Outlook 2016-64 2019-03-12 09:43:38 UTC
2019-03-12 10:50:09.276 svoffice PowerPoint 2016-64 2019-03-12 09:43:38 UTC
2019-03-12 10:50:09.276 svoffice Publisher 2016-64 2019-03-12 09:43:38 UTC
2019-03-12 10:50:09.276 svoffice Word 2016-64 2019-03-12 09:43:37 UTC
2019-03-12 10:50:09.852 svoffice C:\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\SVROOT\Program Files\Microsoft Office\Office16\ospprearm.exe result: There was an error when trying to rearm Office. You can try passing the SKU ID as a parameter. Passing the SKU ID is necessary if you are relying on an activation to permit an additional rearm.
Error: 0xc004d304
On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xc004d304' to display the error text.
2019-03-12 10:50:09.854 svoffice PostProvision end
2019-03-12 10:59:26.666 svoffice PostProvision log end
2019-03-12 10:59:26.699 svoffice Invalid Office 365 product ID ProPlus2019Volume
2019-03-12 10:59:26.724 svoffice System.SystemException: Application aborting
2019-03-12 10:59:26.724 svoffice bij svoffice.AbortApp()
2019-03-12 10:59:26.724 svoffice bij svoffice.ParseXMLFile(String sFileXML, XML_PARSED& xmlParsed)
2019-03-12 10:59:26.724 svoffice bij svoffice.cmd_logon(String[] args)
2019-03-12 10:59:26.724 svoffice bij svoffice.Main(String[] args)
2019-03-12 10:59:31.512 svoffice ShellStart start
2019-03-12 10:59:31.513 svoffice Waited 0,011 seconds for log file lock
2019-03-12 10:59:31.537 svoffice Invalid Office 365 product ID ProPlus2019Volume
2019-03-12 10:59:31.565 svoffice System.SystemException: Application aborting
2019-03-12 10:59:31.565 svoffice bij svoffice.AbortApp()
2019-03-12 10:59:31.565 svoffice bij svoffice.ParseXMLFile(String sFileXML, XML_PARSED& xmlParsed)
2019-03-12 10:59:31.565 svoffice bij svoffice.cmd_shellstart(String[] args)
2019-03-12 10:59:31.565 svoffice bij svoffice.Main(String[] args)
Error 0xc004d304 translates to: "The security processor reported that the entry key was not found in the trusted data store"
No idea what that means, why this is happening and how to fix this... It makes our AppStack useless!
KB 2146035: VMware Knowledge Base
Office 2019
Office 2019 is currently not supported with App Volumes
Hi, thanks for the info.
I know this isn't supported, but a have to try. It's almost a year ago i posted this and Office 2019 is still not supported! Our organisation has already moved to Office 2019 so i have no option, i have to get this to function. Besides that, i do find it a bit shocking that it's still not supported. From what i have heard from MS tech support the changes from 2016 to 2019 aren't that big.
Yes I totally agree, I would very much like it to be supported on AppVolumes as well as our organization is finalizing steps to move to 2019 these days.