Skip to content

Conversation

@cert-cwatch
Copy link
Contributor

Hello Andrew, we have identified that a warning pop-up can occur while running SUM and SRUM repair scripts in Kape.

We encountered an issue where the SUM and SRUM repair scripts would pause Kape, waiting for user input.

image

In my understanding, the warning originates from Esentutl.

Repair does not run database recovery. If a database is in “Dirty Shutdown” state, it is strongly recommended that before proceeding with repairs, recovery is first run to properly complete database operations for the previous shutdown.
The /g option pauses the utility for user input before repair is performed if corruption is detected. This option overrides the /o option.
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh875504(v=ws.11)

To resolve this, we added the '/o' option, which appears to suppress the warning and allows the scripts to run smoothly.
We also compared the script output with and without this change: the headers in the CSV files remain identical.

@AndrewRathbun AndrewRathbun self-assigned this Jan 9, 2026
@AndrewRathbun AndrewRathbun added the enhancement New feature or request label Jan 9, 2026
@AndrewRathbun AndrewRathbun changed the title Remove warning pop-up Remove warning pop-up in SUM/SRUM Repair scripts Jan 9, 2026
Copy link
Owner

@AndrewRathbun AndrewRathbun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! Thank you!

@AndrewRathbun AndrewRathbun merged commit 30d9746 into AndrewRathbun:main Jan 9, 2026
1 check failed
@AndrewRathbun
Copy link
Owner

@cert-cwatch I can get the scripts re-signed sometime today FYI

@AndrewRathbun
Copy link
Owner

@cert-cwatch these scripts are now re-signed, as seen here: 9f2efc6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants