Errors in Event Viewer

Contributor

Since the latest beta update the following is appearing in Event Viewer:

 

Failed to parse element: Requirements
Id=87b35109-b1d7-4cdf-9cbb-84c1d946d22b, DisplayName=CV Surveys Win32, Provider=Amplify Signals and Insights Team, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15511.20000
P3: 0x8004323E
P4: New Document

 

Not too sure what is triggering this error, or which Office app is reporting it. 

9 Replies

@PurSpyk 

 

I'm have that identical error on the July 2022 build of Windows 11.

 

I have a 32-bit version of Office installed (because I need that version for a specific custom Access database).  Any chance you're running 32-bit Office?

 

I also have iDrive automated backup software installed.  Launching a backup with that software seems to kill my Ethernet connection until I reboot.  Not sure if that's related.

 

Do either of those two variables overlap with your situation?

Hi

No I use the 64bit version and don't use idrive

I also have this problem. Seems random in its occurrence.

I am finding the same error (and have a known Fast Flux DNS threat in my environment).

Exploit Protection is killing a number of Office processes flagged for credentail stealing. I am not sure if they are related.

same error here. on an insider build of windows 11 but not using the office "coming soon". wondering if that might address it.

otherwise assuming its something that must be lived with until the fall update.

Latest beta build, 26 July 2022, still same error. How do we report issues that get noticed? Feeback hub is pointless, these forums are only users, feedback via Office seems to go unnoticed as well.
Same error for me:


Failed to parse element: Requirements
Id=87b35109-b1d7-4cdf-9cbb-84c1d946d22b, DisplayName=CV Surveys Win32, Provider=Amplify Signals and Insights Team, StoreType=SdxRdx, StoreId=(null)
P1: Apps for Office
P2: 16.0.15427.20182
P3: 0x8004323E
P4: New Document
Latest version of Office, new Windows Updates, still same error reported. How do we get this fixed, feedback does not seem to be taken seriously
This happened in April and was eventually fixed....no it returns