Forums

Jerome, I think that we are actually a lot further now, and I think that you are close to finding it. First, we've now eliminated all other causes except the terminal server.  The thread that I brought up last night was one of many.  In my case, I'd probably message the person in the thread and ask how they fixed it.  

Furthermore, you will see all sorts of articles and posts on google with various fixes for your exact same problem.  

One of the articles that really helped me was right here when the author discusses causes of terminal service login problems:  

www.virtualizationadmin.com/.../troubleshooting-terminal-service-connection-errors.html

This would explain why an administrator could login but a user couldn't.  It also explains why some users can login while other users can't.  

Finally, just google the terms, "dynamics terminal services user profile troubleshooting" and check out all of the user profile fixes -- that same one: log on interactively strikes me as a probable cause.  

That should be enough to get there.  Ideally, there would be a good windows person who can now compare that user profile on the TSE server to the working profiles and look for the missing permission.  That's what I would do.  

Hope that helps and let me know if you find an answer.  As I said, you are a lot closer.  

Hello Jérôme!

The last time i got this issue i had to remove the user from the AX Users, delete the user account from de AD and recreate a new AD account and import it into AX again!

Hello  fsilva-jr,

I will try your solution.

Do you know the reason ?

Best Regards

Please dont forget to delete the user profile folder before to login with the new user account.

I think it was caused because of a crash in the user profile... could not find the main reason yet

hope it work for you!

Hello!

Was your problem solved?!

Hello,

Was in holidays :)

Didn't do nothing since... :)

Delete the AD User and recreate.

Denis

lol...  I fell down laughing when I read the answer to this one.  This just goes to show the dangers of internet troubleshooting without looking at a system.  Ultimately, without looking at the system, we sometimes make the wrong assumptions.  Everyone assumed that the user profile had already been examined for any differences in settings.  This is because you had stated that you deleted the user profile.  But you had not deleted the ax user profile.  You had deleted the cached version of the user profile on the system.    In person, this would have been caught in 2 minutes.  On the internet, interpretations can get messy.   

So, an FYI for anyone, to solve this:

To start with a problem like this, you should first examine the core Dynamics AX User Profile. Open up your Dynamics AX Client.  Go to System Administration --> Common --> Users.  Hit the checkbox for the user in question and select Profiles.  Check the user in question and select Options from the top ribon menu. Examine the account for differences.  That's almost always the first step of troubleshooting when a user has a permissions related issue or something funny happening just for that user.  Then, afterwards, all of the other steps would have come into play had the situation been more complicated.  I'm attaching a screenshot of the fix..  [note: may have to be logged in to see the screenshot]

Sorry but like I said, I don't know anything about AX for now.

But why that setting is linked to the fact that the user cannot use the application onto 1 server whereas everything works on the others.