[SOLVED] Events ({3bb9fd2b-351e-4b9c-b1fc-ed0758805998}) with HRESULT HRESULT_FROM_WIN32(234)

Blew away the key, exact same error. Key did NOT come back after the update. Still errors though.

Thats a weird one eh?

2022-02-01 14:27:53, Error CSI 00000284 (F) Error HRESULT_FROM_WIN32(234) in eventsXml: <events><provider guid="{3663a992-84be-40ea-bba9-90c7ed544222}" message="$(string.eventProviderName)" messageFileName="%SystemRoot%\system32\efscore.dll" name="Microsoft-Windows-EFS" resourceFileName="%SystemRoot%\system32\efscore.dll" symbol="EFS_PUBLISHER"><channels xmlns="http://schemas.microsoft.com/win/2004/08/events">

<channel chid="Microsoft-Windows-EFS/Debug" isolation="Application" name="Microsoft-Windows-EFS/Debug" symbol="EFS_DEBUG" type="Debug"></channel>

<importChannel chid="Application" name="Application"></importChannel>

</channels></provider></events>
[gle=0x80004005]
2022-02-01 14:27:53, Info CSI 00000285@2022/2/1:22:27:53.760 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};(null);7151298us
2022-02-01 14:27:53, Info CSI 00000286 End executing advanced installer (sequence 0)
Completion status: HRESULT_FROM_WIN32(234)

2022-02-01 14:27:53, Info CSI 00000287 Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:781f50f4ba17d801f80200009808dc08} pathid: {l:16 b:49b550f4ba17d801f90200009808dc08} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_09e78f632173f4c5' pid: 898 starttime: 132882279715865003
2022-02-01 14:27:53, Error [0x01802b] CSI 00000288 (F) Failed execution of queue item Installer: Events ({3bb9fd2b-351e-4b9c-b1fc-ed0758805998}) with HRESULT HRESULT_FROM_WIN32(234). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
2022-02-01 14:27:53, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2022-02-01 14:27:53, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20220201222611.log to WER report.
2022-02-01 14:27:53, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20220201192042.log to WER report.
2022-02-01 14:27:53, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20220201110047.log to WER report.
2022-02-01 14:27:53, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20220201092935.log to WER report.
2022-02-01 14:27:54, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20220131233331.log to WER report.

~Matt
 
Just to add - there's not a single reference of 3bb9fd2b-351e-4b9c-b1fc-ed0758805998 in the registry anymore...anywhere lol.

~Matt
 
OK, well as that didn't work I would replace that key from your exported file. I will dig into this a bit more and see what else I can suggest.
 
I would like to explore your system for the file mentioned in your error.

Please run the following script.

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to check please.
 

Attachments

Hmm interesting - did this on a working 2016 server. Same versions, but it doesn't give a failed to trace error like the broken one.

~Matt
 

Attachments

Hey so, I may have a solution for this, possibly? From the vendor.

Here's the fix. Testing now, just don't want you to spend more time if this works. I'll know shortly though. The value there was 524288000, but it was a REG_SZ not REG_DWROD. Dunno if they just dump too much stuff in the event log or whatnot.

1. Go to run and execute regedit.exe

2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Application

3. Check if key “MaxSize” is present with data type REG_DWORD, if datatype is not REG_DWORD, remove the key and perform steps 4 and 5.

4. Create a new key “MaxSize” of registry data type REG_DWORD

5. Provide 524288000 as value to the key (decimal) the exit regedit to save settings.

6. Stop Rhapsody server and then reboot IBE server to take effect.
 
Last edited:
Vendor tried to change the size of the event log, in doing so changed it from REG_DWORD to REG_SZ. That messed everything up. Changing it back to a DWORD fixed it. Sorry to waste your time man, appreciate all the help!

Feel free to mark this closed!

~Matt
 
Thanks for the feedback. I've marked It solved.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top