just received a warning about a failed vss call during backup time today with the following content:
Failed to perform post-backup application-aware processing steps Details: Failed to call RPC function 'Vss.FinishSnapshot': Error code: 0x80004005. Failed to invoke func [FinishSnapshot]: Unbekannter Fehler. Could not run program [C:\WINDOWS\TEMP\{9c63168b-4aa0-46f9-8069-a58acd122666}] with arguments [-func BlobCall -out "C:\WINDOWS\TEMP\{13f0d008-af5a-4800-b4ce-93cf8b69e43c}" -blob "C:\WINDOWS\TEMP\{2aad1051-0426-4c93-a35b-e14313843132}" -glogin "domain\user" -gpwd xyz
If you take a look at the last part, the "xyz" from the gpwd argument should probably not be shown here?? I'm not sure about it but if it was a Hash or anything that can be used to authenticate this user, it should not be shown in this message. If this value was already 'anonymized', then there's no reason to stop smiling
Will be glad to investigate this one with QA, but we will need an entire log file for this job.
You can send it via PM to me or via support ticket(share ID with me).
Interesting case: error message string in our log files has password replaced with ***, however UI parses the error message "as is" into the session details.
Password string itself is encrypted, but we will make sure to hide it with *** in the UI as well.
Logged a bug.
