We are in the process of testing out GP 9 in preparation for our upgrade to 9 from 7.5 and are having login issues.
Our test environment consists of 2 citrix servers, both on Win 2k Server. One is a copy of our live environment running 7.5. The second is an image of the first, but with the upgrade to 9 completed.
We are using Citrix to run GP as we are in our live environment. Our test users have no issues logging into th 7.5 instance. For some, when they try logging into the 9 instance their login fails every time (basically it's a password failure). I have reset their password, tested logging in with this from my computer (logged into Citrix as me of courser) and it works fine. When the user tries the new password, it fails still. I have shadowed and tried logging in with my login and it fails. The only username I am able to log into their session with is SA. This would tend to point to some issue with the password encryption as SA is an unencrypted password (correct me if I am wrong). I have created a new windows user to launch the sessions and it works fine for any user.
I hope that explains the pickle we are in. We hope this was just a glitch in our test area, but if it isn't, it's a showstopper when we actually do the upgrade for real.
Any input would be appreciated
Thanks
Our test environment consists of 2 citrix servers, both on Win 2k Server. One is a copy of our live environment running 7.5. The second is an image of the first, but with the upgrade to 9 completed.
We are using Citrix to run GP as we are in our live environment. Our test users have no issues logging into th 7.5 instance. For some, when they try logging into the 9 instance their login fails every time (basically it's a password failure). I have reset their password, tested logging in with this from my computer (logged into Citrix as me of courser) and it works fine. When the user tries the new password, it fails still. I have shadowed and tried logging in with my login and it fails. The only username I am able to log into their session with is SA. This would tend to point to some issue with the password encryption as SA is an unencrypted password (correct me if I am wrong). I have created a new windows user to launch the sessions and it works fine for any user.
I hope that explains the pickle we are in. We hope this was just a glitch in our test area, but if it isn't, it's a showstopper when we actually do the upgrade for real.
Any input would be appreciated
Thanks