Hi All,
I have had this a few times and typically with smaller upgrades I get around the problem by deleting the users and re-creating however I am dealing with a much larger upgrade with over 100 users so.. was hoping for a better way to go about this.
So for the test upgrade on the new server, after I restore the databases and say run the upgrade to the last step of GP18.3, i then run the SQL Login Capture script against the old sql server then run the results against the new sql server and it creates the logins fine, I then typically change the password for each one (which is equally as long..) then they login fine after i also run the grant script for good measure.
However after I do the live upgrade so just restoring a database this time and the logins SQL are of course already present, upon sucesful upgrade I then go to change the users password then when I login as that user I get the following:
Any ideas on the correct process or a nice quick way around this?