Instead of upgrading your existing DS 6.9 SP6, you've built a new GSS 3.1 server. You've also decided to use a new database. However, you'd like to use your existing jobs from DS 6.9 SP6 with your GSS 3.1. So you've exported your jobs from DS 6.9 SP6 and have imported them into your GSS 3.1. You've noticed however that now the tasks that you've set a specified user for are failing because of an incorrect password or insufficient rights.
Anyone who is exporting jobs from DS 6.9 SP6 and importing them to GSS 3.1 or higher, up to GSS 3.1 MP3 at this time.
Logon failure: unknown username or password
A new encryption method has been added to GSS 3.1 for updated security. This encryption also applies to how passwords are encrypted in the database for all jobs where a specified user has been set. When importing your jobs from DS 6.9 SP6 into GSS 3.1 your passwords are not being encrypted properly using the new encryption method. There for they won't work in GSS 3.1.
The work around for this is to simply go into the task, where the specified user has been set, and retype the password. This will update the encryption in the database for that one task. It will then work.
Development has been made aware of the issue and is currently determining if a fix can be provided. Please subscribe to this tech article and you will be notified if a fix is made available.
Subscribing will provide email updates when this Article is updated. Login is required.