May 11, 2022 at 9:20 pm
This is "resolved". Our experience with Microsoft ended the same as the previous comment. Stager the job start times. We actually did this a few weeks ago and haven't seen the error since.
We just kept at least a 5 second buffer between them, that's all it took.
Cause: buffer that stores the decrypted password can become corrupt when multiple jobs start at once. The result is not being able to retrieve the pw or it reads a corrupt and therefore incorrect pw.
They also noted that they are working on a fix, not sure if that would be Windows or SQL.
January 24, 2023 at 1:45 am
Looks like this is finally getting fixed.
Viewing 3 posts - 31 through 32 (of 32 total)
You must be logged in to reply to this topic. Login to reply