-
1
- #1
Overview of configuration:
Terminal Services is configured as an application server and Terminal Service licensing has been activated and is installed properly.
All 3 Terminal Service Clients are Windows 2000 Sp3 and patched. However I have tested with Windows XP RDP client with same results.
Description of Problem:
All Terminal sessions connect perfectly and are capable of running any application during concurrent sessions except Accpac.
It seems when a user is connected and successfully logged into Accpac when a second user goes in we get an Accpac license warning and are brought to an anti-piracy web page. It appears all Accpac Lan Pak licenses are installed correctly.
We have better luck of getting back into Accpac if we choose to close the company from the menu and then exit Accpac.
What I've done that has helped:
I have created 10 user accounts to log into Terminal Services with termuser1 - termuser10. The account that successfully gets into Accpac can vary from day to day.
Accpac will work if all users are logged in with the working account once we know which on it is.
It seems without notice the next time you log in you may not be able to get into Accpac.
We have also noticed the following peculiarity:
If we are connected as any user (lets just say Termuser1) and successfully get into Accpac, then connect another session
with any different user (Lets say Termuser2) once both sessions disconnect Termuser 2 will be the only user account able to login to Accpac.
When we say we can't get into Accpac we do not get an error message. The Accpac splash screen shows briefly and the application never opens. It is as if the Accpac Signon Module never gets started.
I have noticed if I choose to run the application as a different user in the shortcut properties for Accpac I get the signon but cannot get any further.
Any comments will be helpful
Terminal Services is configured as an application server and Terminal Service licensing has been activated and is installed properly.
All 3 Terminal Service Clients are Windows 2000 Sp3 and patched. However I have tested with Windows XP RDP client with same results.
Description of Problem:
All Terminal sessions connect perfectly and are capable of running any application during concurrent sessions except Accpac.
It seems when a user is connected and successfully logged into Accpac when a second user goes in we get an Accpac license warning and are brought to an anti-piracy web page. It appears all Accpac Lan Pak licenses are installed correctly.
We have better luck of getting back into Accpac if we choose to close the company from the menu and then exit Accpac.
What I've done that has helped:
I have created 10 user accounts to log into Terminal Services with termuser1 - termuser10. The account that successfully gets into Accpac can vary from day to day.
Accpac will work if all users are logged in with the working account once we know which on it is.
It seems without notice the next time you log in you may not be able to get into Accpac.
We have also noticed the following peculiarity:
If we are connected as any user (lets just say Termuser1) and successfully get into Accpac, then connect another session
with any different user (Lets say Termuser2) once both sessions disconnect Termuser 2 will be the only user account able to login to Accpac.
When we say we can't get into Accpac we do not get an error message. The Accpac splash screen shows briefly and the application never opens. It is as if the Accpac Signon Module never gets started.
I have noticed if I choose to run the application as a different user in the shortcut properties for Accpac I get the signon but cannot get any further.
Any comments will be helpful