Skip to main content

Notifications

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 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:

*This post is locked for comments

  • Suggested answer
    RE: [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."

    Thx

  • RE: [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."

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

  • Verified answer
    Sean Watson Profile Picture
    Sean Watson 30 on at
    [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."

    "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.

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

News and Announcements

Announcing Category Subscriptions!

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Verified Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,359 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,370 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans