Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

GP10 user problem on Terminal server only

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

I have a problem driving me crazy. We have gp10 installed on our client. They have a Win2003 Terminal server installed for users to access GP.

One of the users say USERA tries to login to GP on the terminal server, it gives an error saying

"An error was encountered, GP has to close" and GP shuts down. I started troubleshooting this and this is what I have done till now and the results:

1) Logged in to TS using USERA login and logged into GP using USERA login and of course it gave errors and closed

2) Logged into TS using another user login and logged into gp using another user and everything is fine.

3) Logged into GP using the USERA login (being on another user login in TS) and the error occurred.

4) Logged in TS using USERA and another user in gp and worked fine

5) Logged on GP SQL server and logged into gp using USERA ( which gives error on TS box ) and it works fine.

Where should i look for resolving this problem. Thanks

 

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP10 user problem on Terminal server only

    Hamza one more thing you can check is how the ODBC is set up on the Terminal Server vs the SQL Server.  If the servername is different (servername vs IP address vs localserver) then it is possible that USERA's password may have been encrypted differently and will not login on the TS.  In that case either modify the ODBC, or create the user on the machine from which they will log in.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP10 user problem on Terminal server only

    So why does dropping and recreating USERA in GP not work?  

    1. Does the recreated user have different GP Security Roles and Company Access than the other GP user you tested with?  

    2. On the User Setup window, do you have Enforce Password Policies checked in one case and not the other?  

    3. After deleting USERA in GP, I would double check in SQL Management Studio to ensure all instances of USERA gone.  Look under the Security node as well as under all GP database nodes and manually delete if necessary.  Then recreate the user in GP.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP10 user problem on Terminal server only

    it is not a permissions issue, same user logged in TS can log into GP with another user. Another user in TS with faulty user in GP also gives same error

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP10 user problem on Terminal server only

    Hamza,

    A quick test to see if it is a permissions issue would be to copy the permissions from the user that is working on the TS to this "USERA" that you are referring to.  If the problem goes away, then not only is the issue resolved, but you will know that it is a permissions issue.  

    Since you are not familiar with using SQL trace, then I would try this first.

    Regards,

    Aaron

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP10 user problem on Terminal server only

    Richard, How do i SQL trace log? How would that show me the folder? Please give some specific examples, i'm a newbie to this.

    Vilma, Dropping and recreating the user did not resolve the issue.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP10 user problem on Terminal server only

    Dropping and recreating the user in GP may be the quickest resolution.

  • Richard Whaley Profile Picture
    Richard Whaley 25,195 on at
    Re: GP10 user problem on Terminal server only

    GP creates a folder on the TS device to hold the settings of individual users.  Each GP user has a folder in this temp folder.  But they must also have network/workstation rights to add/edit/delete/create in that folder.

    Run a SQL trace log and see where it is crashing.  This will tell you the location of the folder.

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

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,391 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,445 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans