bad password is mistaken as validation problem
If you have bad login info when you attempt to validate, without Debug enabled, all you see is “found errors in FOO” which obscures the real issue.
2026-07-16 14:12:18.837 [info] [@libum-llc/symitar] [SymitarHTTPs] Validation response status: 200, data: {"TaskManager_PowerOnValidateAndInstall":{"exitCode":0,"message":"Error: Invalid User Number or Password.\n","status":"error","statistics":{"durationInMillis":200}},"message":"error"}
2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] TaskManager message: Error: Invalid User Number or Password.
2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] Validation failed for FOO
2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] Top-level error message: error
2026-07-16 14:12:18.839 [info] [validateSymitarPowerOn] found errors in FOO

Comments2
Jul 17
PinnedWe’ll include this in
v1.10release - apologies for the delay on that version we’ve had mixed priorities but have an internal goal of this Friday.Dylan Martinez
Aug 11
Sorry for the delay, this has been added.