resetDatabase blames service shutdown errors on lack of privileges, which is often the case, but that's a pretty useless thing to do if it happens to occur while running with elevated privileges. For this issue, simply suppressing that part is sufficient if we're running with elevated privileges. So, if running without elevated privileges, this makes sense:
Why?
This failure is likely to be due to lack of permissions
What to do:
If you can, try running this command as an administrator.
But say nothing if running with elevated privileges and just let the error speak for itself.
resetDatabaseblames service shutdown errors on lack of privileges, which is often the case, but that's a pretty useless thing to do if it happens to occur while running with elevated privileges. For this issue, simply suppressing that part is sufficient if we're running with elevated privileges. So, if running without elevated privileges, this makes sense:But say nothing if running with elevated privileges and just let the error speak for itself.