C
carlPjohnson
I am using Windows 2003 SP1 with 2x AS 4.1 and the Terminal Server Agent stops responding (services shows started) time to time and a simple restart fixes it. Any others having this problem?
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
N
nixu
Hi there,
Can you give more information regarding this issue...
OS, System setup etc...
If you restart the 2X Controller instead of the 2x Terminal server Agent does it solve the issue??
Is the 2X Terminal Server Agent using a lot of CPU power ?
Can you "Check Agent" from the Console?
Regards
Nixu
Can you give more information regarding this issue...
OS, System setup etc...
If you restart the 2X Controller instead of the 2x Terminal server Agent does it solve the issue??
Is the 2X Terminal Server Agent using a lot of CPU power ?
Can you "Check Agent" from the Console?
Regards
Nixu
C
carlPjohnson
.. more info
Windows 2003 Standard SP1
Dual 3G Xeon
4gb Ram
20 Concurrent RDP Users
5-10 concurent 2X Users
2X TS Agent CPU usage is minimal, except for when starting.
When checking the agent via the Console, it always reports all the correct information. But in the Information->Status display it will show Not Verified until I stop/start the Terminal Server Agent. I will need to wait until this happens again to try stopping/starting the Controller instead.
Windows 2003 Standard SP1
Dual 3G Xeon
4gb Ram
20 Concurrent RDP Users
5-10 concurent 2X Users
2X TS Agent CPU usage is minimal, except for when starting.
When checking the agent via the Console, it always reports all the correct information. But in the Information->Status display it will show Not Verified until I stop/start the Terminal Server Agent. I will need to wait until this happens again to try stopping/starting the Controller instead.
C
carlPjohnson
.. occured again
The issue occured again this morning so I tried stopping/starting the publisher, no luck. Tried the same with the gateway, no luck. Stop/Started the agent and all was well. Please consult, I will open a ticket if need be.
The issue occured again this morning so I tried stopping/starting the publisher, no luck. Tried the same with the gateway, no luck. Stop/Started the agent and all was well. Please consult, I will open a ticket if need be.
N
nixu
Hi there,
The issue seams to be found, will upload a new build later on today or tomorrow.
Will update you when there is the new version.
Thank for your help.
Nixu.
The issue seams to be found, will upload a new build later on today or tomorrow.
Will update you when there is the new version.
Thank for your help.
Nixu.
N
nixu
A New beta version (161) has been uploaded.
Can you update your software with this version.
Nixu
Can you update your software with this version.
Nixu
N
nerdpatrol
Will the agent and loadbalancer/publisher both need to be updated? I hate to load a beta on production servers
BTW: We started experiencing this yesterday after it worked for a while.
BTW: We started experiencing this yesterday after it worked for a while.
N
nixu
We always recommend that you update all the components.
Nixu
Nixu