We have a client with 27 users, all of whom access GP 10.0.320 via a single Terminal Server machine. The network and bandwidth do not seem to be an issue and we are not having issues with users complaining about speed. The issue we have experienced today is an inability to log onto the application.
GP seems to know we are trying, as the users are told that they have a session in GP database, and it allows us to remove that session, however, it still seems to fail when continuing the connection to the server.
This is only happening for the users on the Terminal Server, as I have a direct to SQL server installation, I am able to log onto that machine with no issues. As long as the users stay in GP, no issues, as long as they do not attempt to change databases (company change) there are no issues, so, as soon as they try to log in, change databases they are not allowed and GP simply quits.
We have been running in the configureation for over a year and this is the first time we have experienced this level of user login issues.
Bill C
*This post is locked for comments