Share
ReportHello:
Soon, we will be moving our GP 2013 R2 databases to a new SQL instance. Doing so will force a change of all GP users' passwords.
I'm testing GP in a test environment, while pointing to the soon to be new SQL instance. As usual, we ran through the steps outlined in KB article #878449.
Just now, m logged in as "sa", I changed someone's GP password to "OldSQL123". The box for changing that user's password at "next login" is checked in GP's User Setup window.
So, I logged into GP as that user in the test environment, with this "OldSQL123" password. In the window that prompted me to change the password, I entered "P@ssword123".
I got the message "Password change failed for an unknown reason", and I was asked to contact an administrator.
The following are our company's SQL password requirements:
the password must meet the Microsoft SQL Server Strong Password requirements:
• Does not contain all or part of the user's account name
• Is more than eight characters in length
• Contains characters from at least three of the following categories:
o English uppercase characters (A through Z)
o English lowercase characters (a through z)
o Base 10 digits (0 through 9)
o Nonalphabetic characters (for example: !, $, #, %)
Can you all think of any GP or SQL aspect that would prevent me from logging in as this user with this new password? Both of the passwords that I'm testing with meet the above requirements, unless I'm mistaken.
Thanks! Much appreciated!
John
*This post is locked for comments
All responses (
Answers (
4
