But, a company has had to update GP user passwords, even though the servers in HA are on the same network.
Why, and what can be done to prevent having to change GP passwords?
Thanks!
John
But, a company has had to update GP user passwords, even though the servers in HA are on the same network.
Why, and what can be done to prevent having to change GP passwords?
Thanks!
John
Hello John,
When you mention High Availability, are you referring to AlwaysOn Groups that can be setup with SQL Server?
If so, you're correct in that I know I've heard the passwords don't work during a failover with AlwaysOn Groups when on different subnets, as you mentioned, I've seen varying success with AlwaysOn Groups, usually due to Dynamics GP encrypting its passwords whereas, if a GP login password is reset in SQL Server, it doesn't encrypt it, thus users are prompted to change their password the next time they attempt to login or you need to login as 'sa' and reset the user's password in the User Setup window.
The following page > mbs.microsoft.com/.../MDGP_SQL2012SupportedFeatures > has two documents that discuss Dynamics GP and the AlwaysOn feature in SQL Server, I'd recommend looking at these documents if you haven't already.
I'd also mention that usually with these type of cases we have our SQL Support engineers look at it, as they're more the expert with the AlwaysOn functionality and setup, but maybe others on this forum will have information as to what they had to do to get it to work for them.
Let us know if you have any questions.
Thank you,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,235 Most Valuable Professional
nmaenpaa 101,156