A user in this scenario in according to development can adopt one of the following solution:
1. Verify that the STAT_LOGIN user has read access to the STAT_LOGIN table.
It's probably ok otherwise you'd be getting a first pass login failure, but let's just make sure.
2. Send us the password from the Stat_login table and the results of this sql:
select * from stat_store_vw and we'll tell you what to set the Stat password to.
OR
3. Send us a password you want to use, plus the contents of the above sql and we'll encrypt it for you
so they can insert it into stat_login and change the stat db to it.
OR
4. Just give us the results from the query and we'll encrypt STAT for you so you can insert it into the stat_login table.
Also for any future password issues refer to the System Admin Guide section for the correct protocol when changing the STAT password.
In this case the issue solved once verified the password from STAT_LOGIN table matched in uppercase.
Apparently the stat password was lower case in the DB and when it was altered to uppercase it resolved the issue.
