Apr 13 2022
07:39 AM
- last edited on
Jun 17 2022
11:15 AM
by
TechCommunityAP
Apr 13 2022
07:39 AM
- last edited on
Jun 17 2022
11:15 AM
by
TechCommunityAP
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
Apr 14 2022 10:36 AM
Apr 14 2022 03:25 PM
@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.
Apr 15 2022 12:25 AM
Apr 17 2022 06:23 AM - edited Apr 17 2022 06:32 AM
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?
Apr 19 2022 12:31 AM
Apr 19 2022 10:13 AM
Apr 19 2022 11:08 PM
Apr 20 2022 01:25 AM
Apr 20 2022 04:03 AM
Apr 22 2022 05:59 AM - edited Apr 22 2022 05:59 AM
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.
Apr 22 2022 06:34 AM
May 03 2022 04:08 AM - edited May 03 2022 05:00 AM
now on 15128.20178. (current channel) - log errors still occur. reported through builtin feedback function
May 03 2022 04:25 AM
May 04 2022 09:24 AM
May 04 2022 12:10 PM
@PurSpyk It is being actively investigated. A bug was officially filed on 5/3.