web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / [Resolved] "Your ...
Finance | Project Operations, Human Resources, ...
Answered

[Resolved] "Your attempt to log in to the server failed because an unknown error occurred when the user ID and password were being verified. Attempt to log in again."

(0) ShareShare
ReportReport
Posted on by Sean Watson 30

"Your attempt to log in to the server failed because an unknown error occurred when the user ID and password were being verified. Attempt to log in again."

Resolution:

In our scenario, we had the GP Server on one domain and the end user/client on another. Thanks to Derek Albaugh's comment about ODBC, I quickly launched the application and it failed the test with the following "The client and server cannot communicate, because they do not possess a common algorithm." - I immediately remembered that I had deployed a policy to only allow TLS 1.2 on the end user/client domain. Temporarily disabling the TLS restriction policy and cleaning out the rules in the registry on the client PC resolved our issue.

Categories:
Microsoft Dynamics GP

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Sean Watson Profile Picture
    Sean Watson 30 on at

    "Your attempt to log in to the server failed because an unknown error occurred when the user ID and password were being verified. Attempt to log in again."

    Resolution:

    In our scenario, we had the GP Server on one domain and the end user/client on another. ODBC failed the test with the following "The client and server cannot communicate, because they do not possess a common algorithm." - I immediately remembered that I had deployed a policy to only allow TLS 1.2 on the end user/client domain. Temporarily disabling the TLS restriction policy and cleaning out the rules in the registry on the client PC resolved our issue.

  • Derek Albaugh Profile Picture
    Derek Albaugh on at

    Thanks for the information Sean, I'm sure it'll help others that run into this.

  • Suggested answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at

    Thx

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 456 Super User 2025 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 429 Most Valuable Professional

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans