-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Veeam Module crashing #93
Comments
Maybe it's a blank password so it tries to split on it but cant? |
That was indeed an issue in the past :D fixed that a few weeks ago by replacing whitespaces with a some text, so that shouldn't be it... |
It looks like you set that text after the split (line 164). From the error it's stating that |
That should be the convention back to the original whitespace. Currently whitespaces in the password are already converted to "WHITESPACE_ERROR" in the powershell output and now after splitting account and password converted back to the original " ". I saw that error once when powershell returned some kind of error message where the whole syntax is not applicable (account could something arbitrary than). That was my idea why it crashed. I should probably do something like: |
Adding error handling for unexpected powershell output, see issue #93
Closing it until someone opens up an issue with a specific crash report. This should be now get handled better and not crash. |
Describe the bug
Veeam Modul randomly crashes
To Reproduce
Uknown
Screenshots
NetExec info
Additional context
My best guess is that powershell returns an output string which the module can't properly interprete. I will add a general error handling to the powershell output.
The text was updated successfully, but these errors were encountered: