Errors in Event Viewer

%3CLINGO-SUB%20id%3D%22lingo-sub-3284603%22%20slang%3D%22en-US%22%3EErrors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3284603%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20updating%20to%20the%20latest%20beta%20version%2015209.20000%2C%20the%20following%20errors%20appear%20in%20Event%20Viewer%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFailed%20to%20parse%20element%3A%20VersionOverrides%3CBR%20%2F%3EId%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3CBR%20%2F%3EP1%3A%20Apps%20for%20Office%3CBR%20%2F%3EP2%3A%2016.0.15209.20000%3CBR%20%2F%3EP3%3A%200x8004323E%3CBR%20%2F%3EP4%3A%20New%20Document%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3286054%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3286054%22%20slang%3D%22en-US%22%3EWe%20are%20seeing%20this%20issue%20as%20well.%20This%20is%20popping%20up%20when%20opening%20a%20new%20document.%20Working%20on%20a%20resolution.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3286360%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3286360%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1364042%22%20target%3D%22_blank%22%3E%40TonyAps124%3C%2FA%3E%26nbsp%3BYup.%20Even%20the%20ID%20is%20the%20same.%20The%20eventid%20300%20seems%20to%20be%20a%20catchall%20for%20office.%20But%20in%20the%20alert%20there%20is%2C%20what%20appears%20to%20be%2C%20a%20random%20string%20of%20characters.%20That%20is%20the%20ID%20that%20is%20the%20one%20that%20is%20the%20same%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3286497%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3286497%22%20slang%3D%22en-US%22%3ESame%20for%20version%2016.0.14931.20118%3CBR%20%2F%3EFailed%20to%20parse%20element%3A%20VersionOverrides%3CBR%20%2F%3EId%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3CBR%20%2F%3EP1%3A%20Apps%20for%20Office%3CBR%20%2F%3EP2%3A%2016.0.14931.20118%3CBR%20%2F%3EP3%3A%200x8004323E%3CBR%20%2F%3EP4%3A%20New%20Document%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3287745%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3287745%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20-%20we're%20getting%20the%20same%20thing%20on%20two%20different%20Dell%20Optiplex%20PCs%20!!!%26nbsp%3B%20Both%20of%20them%20are%20Win%2010%20Pro%2064-bit%20v%2021H2.%26nbsp%3B%20The%20Optiplex%207010%20Mini-Tower%20is%20build%26nbsp%3B19044.1645%2C%20and%20the%20Optiplex%203020%20Mini-Tower%20is%20build%2019044.1586.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EWe%20have%20MS%20365%20Family%2C%20which%20permits%20use%20by%20up%20to%20six%20users%2C%20and%20it%20is%20installed%20on%20both%20PCs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Optiplex%207010%20says%20this%20in%20Event%20Viewer%3A%3C%2FP%3E%3CP%3EFailed%20to%20parse%20element%3A%20VersionOverrides%3CBR%20%2F%3EId%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3CBR%20%2F%3EP1%3A%20Apps%20for%20Office%3CBR%20%2F%3EP2%3A%2016.0.15028.20178%3CBR%20%2F%3EP3%3A%200x8004323E%3CBR%20%2F%3EP4%3A%20New%20Document%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Optiplex%203020%20says%20this%20in%20Event%20Viewer%3A%3C%2FP%3E%3CP%3EFailed%20to%20parse%20element%3A%20VersionOverrides%3CBR%20%2F%3EId%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3CBR%20%2F%3EP1%3A%20Apps%20for%20Office%3CBR%20%2F%3EP2%3A%2016.0.15028.20178%3CBR%20%2F%3EP3%3A%200x8004323E%3CBR%20%2F%3EP4%3A%20New%20Document%3CBR%20%2F%3E%3CBR%20%2F%3EI%20suppose%20our%20%22P2%22%20is%20slightly%20different%20from%20PurSpyk's%2C%20but%20obviously%20not%20important.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Optiplex%207010%20is%20OK%20-%2016%20GB%20RAM%20and%20an%20an%20i5.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Optiplex%203020%20is%20maybe%20underpowered%20-%208GB%20RAM%20and%20an%20Intel%20Pentium%20CPU%20G3220%20%40%203.00GHz.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20what%20should%20we%20do%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3288943%22%20slang%3D%22de-DE%22%3ESubject%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3288943%22%20slang%3D%22de-DE%22%3EI'm%20getting%20the%20same%20error%20and%20Excel%20is%20getting%20closed%2C%20when%20I%20try%20to%20save%20a%20file.%3CBR%20%2F%3E%3CBR%20%2F%3EFailed%20to%20parse%20element%3A%20VersionOverridesId%3CBR%20%2F%3E%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3CBR%20%2F%3EP1%3A%20Apps%20for%20OfficeP2%3CBR%20%2F%3E%3A%2016.0.15028.20152P3%3CBR%20%2F%3E%3A%200x8004323E%3CBR%20%2F%3E%20P4%3A%20New%20Document%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3289469%22%20slang%3D%22de-DE%22%3ESubject%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3289469%22%20slang%3D%22de-DE%22%3ESame%20here%20too%2C%20twice%20a%20day%20office%20365%20thows%20this%20error%20in%20windows%20event%20viewer%20without%20starting%20office365.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3289955%22%20slang%3D%22ja-JP%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3289955%22%20slang%3D%22ja-JP%22%3EMicrosoft%20365%20Personal%20also%20gets%20the%20same%20error%20several%20times%20a%20day.%20%3CBR%20%2F%3E%3CBR%20%2F%3EFailed%20to%20parse%20element%3A%20VersionOverrides%3CBR%20%2F%3E%20Id%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3CBR%20%2F%3EP1%3A%20Apps%20for%20Office%3CBR%20%2F%3EP2%3A%2016.0.15028.20204P3%3CBR%20%2F%3E%3A%200x8004323E%3CBR%20%2F%3E%20P4%3A%20New%20Document%3CBR%20%2F%3E%3CBR%20%2F%3E%20Log%20Name%20Microsoft%20Office%20Alerts%3CBR%20%2F%3E%20Source%20Microsoft%20Office%2016%20Alerts%3CBR%20%2F%3E%20Event%20ID%20300%3CBR%20%2F%3E%20Level%20Error%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3289876%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3289876%22%20slang%3D%22en-US%22%3EHave%20the%20same%20issue%20on%20some%20entities%20of%20XenDesktop%20on%20Windows%20Server%202019.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3292258%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3292258%22%20slang%3D%22en-US%22%3E%3CP%3EI%20continue%20to%20get%20these%20errors%20on%20our%20two%20different%20PCs%2C%20as%20I%20noted%20above%20at%2004-17-2022%2009%3A23%20AM.%20And%20this%20is%20after%20running%20updates%20on%20MS%20365%20Office.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3292298%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3292298%22%20slang%3D%22en-US%22%3EJust%20installed%2C%2016.0.15028.20228%20(ODT%20Current%20Channel)%3CBR%20%2F%3EErrors%20seems%20to%20be%20gone.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3292838%22%20slang%3D%22de-DE%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3292838%22%20slang%3D%22de-DE%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1364284%22%20target%3D%22_blank%22%3E%40WiKo1969%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20it%20is%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3297409%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3297409%22%20slang%3D%22en-US%22%3EYes%20..%20still%20broke%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3300093%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3300093%22%20slang%3D%22en-US%22%3E%3CP%3EMe%20too%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301245%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301245%22%20slang%3D%22en-US%22%3E%3CP%3Enow%20on%2015128.20178.%20(current%20channel)%26nbsp%3B%20%26nbsp%3B-%20log%20errors%20still%20occur.%20reported%20through%20builtin%20feedback%20function%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301258%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301258%22%20slang%3D%22en-US%22%3Ebuild%2015225.20000%20still%20has%20the%20issue.%20I%20have%20even%20reported%20this%20through%20the%20feedback%20option%20in%20Office.%20You%20really%20have%20to%20wonder%20if%20feedback%20ever%20gets%20read.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3303634%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3303634%22%20slang%3D%22en-US%22%3EI'm%20hitting%20the%20same%20issue%20on%20my%20personal%20PC%20(Windows%2010%20Pro%2010.0.19044%20Build%2019044%20%2B%20O365%20version%202204%20Build%2015128.20178%20Click-to-Run).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3313486%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3313486%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F922654%22%20target%3D%22_blank%22%3E%40PurSpyk%3C%2FA%3E%26nbsp%3BIt%20is%20being%20actively%20investigated.%20A%20bug%20was%20officially%20filed%20on%205%2F3.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3315763%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3315763%22%20slang%3D%22en-US%22%3EThank%20You%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3318568%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3318568%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F922654%22%20target%3D%22_blank%22%3E%40PurSpyk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20interesting%20is%20that%20the%20StoreId%3D(null).%20Why%20would%20this%20be%20null%3F%20What%20happens%20in%20my%20instance%20is%20I%20went%20to%20use%20the%20share%20button%20on%20a%20document%20that%20contains%20a%20sensitivity%20label%20applied%20to%20it.%20Once%20I%20do%20that%2C%20it%20crashes%20my%20entire%20Office%20365%20Word%20or%20Excel%20document.%20Hopefully%20this%20isn't%20an%20issue%20with%20IRM%20and%20Office%20365%20applications%20but%20not%20sure.%20I'm%20running%20on%20Windows%2011%2010.0.22610%20Build%2022610%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3326126%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3326126%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F908941%22%20target%3D%22_blank%22%3E%40BrReich-MSFT%3C%2FA%3E%26nbsp%3Band%20for%20all%20of%20those%20working%20in%20Citrix%2FWindows%20Server%202019%20environments%20and%20having%20issues%20with%20O365%20activation%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgcc02.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.ferroquesystems.com%252Fresource%252Fissue-citrix-app-office-365-activation-issue-on-windows-server-2019%252F%26amp%3Bdata%3D05%257C01%257Cscott_vanteyens%2540ios.doi.gov%257C089e1bd34a104ed4f09208da2eadad23%257C0693b5ba4b184d7b9341f32f400a5494%257C0%257C0%257C637873620719795733%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C3000%257C%257C%257C%26amp%3Bsdata%3DQTYhL6Tjay3WpNmP0QW9gunjxH7DRt%252F2bAtK2CIAtBg%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.ferroquesystems.com%2Fresource%2Fissue-citrix-app-office-365-activation-issue-on-windows-server-2019%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3286330%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3286330%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1363846%22%20target%3D%22_blank%22%3E%40XyVr_io%3C%2FA%3E%26nbsp%3Bexactly%20the%20same%20random%20errors%20300%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3290081%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3290081%22%20slang%3D%22en-US%22%3EFailed%20to%20parse%20element%3A%20VersionOverrides%3CBR%20%2F%3EId%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3CBR%20%2F%3EP1%3A%20Apps%20for%20Office%3CBR%20%2F%3EP2%3A%2016.0.15028.20152%3CBR%20%2F%3EP3%3A%200x8004323E%3CBR%20%2F%3EP4%3A%20New%20Document%3CBR%20%2F%3E%3CBR%20%2F%3EError%20seems%20to%20occur%20when%20validating%20the%20Office365%20license%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3345140%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3345140%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20checked%20my%20event%20viewer%20and%20have%20had%20this%20error%20109%20times%20since%204%2F13%2F2022.%3C%2FP%3E%3CP%3ELog%20Name%3A%20OAlerts%20Source%3A%20Microsoft%20Office%2016%20Alerts%20Date%3A%204%2F13%2F2022%206%3A47%3A33%20PM%20Event%20ID%3A%20300%20Task%20Category%3A%20None%20Level%3A%20Error%20Keywords%3A%26nbsp%3B%20Description%3A%20Failed%20to%20parse%20element%3A%20VersionOverrides%3C%2FP%3E%3CP%3EId%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%3C%2FP%3E%3CP%3EP1%3A%20Apps%20for%20Office%3C%2FP%3E%3CP%3EP2%3A%2016.0.15028.20152%3C%2FP%3E%3CP%3EP3%3A%200x8004323E%3C%2FP%3E%3CP%3EP4%3A%20New%20Document%3C%2FP%3E%3CP%3EEvent%20Xml%3A%20300%200%202%200%200%200x80000000000000%204741%20OAlerts%20(localpcname)%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3EFailed%20to%20parse%20element%3A%20VersionOverrides%20Id%3Dd949f36b-4eb7-4269-8eae-db0a399b7ca2%2C%20DisplayName%3DTranscribe%2C%20Provider%3DMicrosoft%20Office%20Services%2C%20StoreType%3DSdxRdx%2C%20StoreId%3D(null)%20Apps%20for%20Office%2016.0.15028.20152%200x8004323E%20New%20Document%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3390997%22%20slang%3D%22de-DE%22%3ESubject%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3390997%22%20slang%3D%22de-DE%22%3EThe%20error%20seems%20to%20be%20gone%2C%20but%20now%20there%20is%20eventid%207000%20clfcl5.365%2C%20the%20file%20could%20not%20be%20found.%3CBR%20%2F%3E%20maybe%20this%20is%20related%20to%20MSoffice.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3411001%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3411001%22%20slang%3D%22en-US%22%3ENow%2C%20almost%20six%20weeks%20later%2C%20I%20have%20not%20seen%20the%20event%20in%20some%20time%2C%20at%20least%20on%20one%20of%20my%20two%20Dell%20Optiplexes%20with%20MS%20Family..%3CBR%20%2F%3EWhat%20did%20MS%20fix%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3411171%22%20slang%3D%22en-US%22%3ERe%3A%20Errors%20in%20Event%20Viewer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3411171%22%20slang%3D%22en-US%22%3E%3CP%3EI%20also%20face%20the%20same%20random%20errors%20300%3CA%20href%3D%22https%3A%2F%2Fhumorquotes.net%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E.%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Since updating to the latest beta version 15209.20000, the following errors appear in Event Viewer:

 

Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15209.20000
P3: 0x8004323E
P4: New Document

 

26 Replies
We are seeing this issue as well. This is popping up when opening a new document. Working on a resolution.

@XyVr_io exactly the same random errors 300

@TonyAps124 Yup. Even the ID is the same. The eventid 300 seems to be a catchall for office. But in the alert there is, what appears to be, a random string of characters. That is the ID that is the one that is the same as well.

Same for version 16.0.14931.20118
Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.14931.20118
P3: 0x8004323E
P4: New Document

Hey - we're getting the same thing on two different Dell Optiplex PCs !!!  Both of them are Win 10 Pro 64-bit v 21H2.  The Optiplex 7010 Mini-Tower is build 19044.1645, and the Optiplex 3020 Mini-Tower is build 19044.1586.

We have MS 365 Family, which permits use by up to six users, and it is installed on both PCs.

 

The Optiplex 7010 says this in Event Viewer:

Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15028.20178
P3: 0x8004323E
P4: New Document

 

The Optiplex 3020 says this in Event Viewer:

Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15028.20178
P3: 0x8004323E
P4: New Document

I suppose our "P2" is slightly different from PurSpyk's, but obviously not important. 

 

The Optiplex 7010 is OK - 16 GB RAM and an an i5. 

The Optiplex 3020 is maybe underpowered - 8GB RAM and an Intel Pentium CPU G3220 @ 3.00GHz.

 

So what should we do?

I'm getting the same error and Excel is getting closed, when I try to save a file.

Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15028.20152
P3: 0x8004323E
P4: New Document
Same here too, twice a day office 365 thows this error in windows event viewer without starting office365.
Have the same issue on some entities of XenDesktop on Windows Server 2019.
Microsoft 365 Personalも日に何度か同じエラーがでます。

Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15028.20204
P3: 0x8004323E
P4: New Document

ログの名前 Microsoft Office Alerts
ソース Microsoft Office 16 Alerts
イベントID 300
レベル エラー
Failed to parse element: VersionOverrides
Id=d949f36b-4eb7-4269-8eae-db0a399b7ca2, DisplayName=Transcribe, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15028.20152
P3: 0x8004323E
P4: New Document

Error seems to occur when validating the Office365 license

I continue to get these errors on our two different PCs, as I noted above at 04-17-2022 09:23 AM. And this is after running updates on MS 365 Office.

Just installed, 16.0.15028.20228 (ODT Current Channel)
Errors seems to be gone.

@WiKo1969 

No it is not.

Yes .. still broke

Me too 

now on 15128.20178. (current channel)   - log errors still occur. reported through builtin feedback function

build 15225.20000 still has the issue. I have even reported this through the feedback option in Office. You really have to wonder if feedback ever gets read.
I'm hitting the same issue on my personal PC (Windows 10 Pro 10.0.19044 Build 19044 + O365 version 2204 Build 15128.20178 Click-to-Run).

@PurSpyk It is being actively investigated. A bug was officially filed on 5/3.