CA in middle of upgrade job, sysadm pwd wrong in env. how to fix?
So I'm in the middle of our 9.1 Initial upgrade and a step died because the target sysadm password is wrong in the environment. Apparently the 'test connection' only tests the User account? I editied it and fixed it, but it hasn't taken affect, the job is still failing? I thought saving the env would replace it in the current job, but that doesn't seem to be the case? Do I need to create a new job to recognize it? Any advice on what I should do?
Thanks.