2X Terminal Server Agent...

  • Thread starter Thread starter iconian
  • Start date Start date
I

iconian

Hi All,
I am currently using the trial of Application server, I have installed on Win2003 Server R2 in Single terminal Server Mode, and I can’t get the TS Agent to start, I keep getting the message “The 2X Terminal Server Agent service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.” When I try to launch an application from a windows xp desktop I get the message “A specific Terminal Server was not found. Please inform your system administrator.”

A copy of the Information window is below:

Thu Jan 18 12:30:04 2007

2X Client Gateway running normally
2X Client Gateway running on port 8080
RDP direct gateway running on port 3388
SSL enabled, running on port 443
Broadcast service running on port 20000
0 active RDP tunneled session(s)
0 active Citrix tunneled session(s)

2X Terminal Server Agent not running, please check log file for more information

2X Publishing Agent running normally

Load Balancing 1 server(s)

Active Disconnected

Server Type Agent CPU Memory Sessions Sessions
192.168.0.206 RDP Not Verified


Any help Appreciated....

Matthew
 
Hi there,

Most probably, the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\ is corrupted.

Copy this key from an other similar machine (ideally with a fresh OS).

Nixu
 
Nearly There.....I think

Thanks Nixu - the Terminal Server Agent is now running sucessfully, but i still have the same message “A specific Terminal Server was not found. Please inform your system administrator.” when trying to launch anything

Matthew
 
More Info

I think it may be something else I have installed as now I have tried it again a clean Virtual Server and it works with just terminal services installed.
 
A specific Terminal Server was not found message appears when the application is published on a server and that server is not verified.

Nixu
 
by not verified do you mean just the check agent button in the console?

if so then it verified ok.
 
The server is made of different components, the 2X Terminal server Agent, the 2X Publishing agent, and the Console (UI).

At Run time the 2X Publishing agent needs to communicate (verify) with the 2X Terminal server Agent.

From the Console you can check if the 2X Terminal server Agent is alive by clicking the check agent button.

In the information tab you can find the status, from here you can see if the 2X Publishing agent has managed to communicate (verified) with the 2X Terminal server Agent.

So make sure that from the status the 2X Terminal server Agent is verified.

Nixu
 
Thank you for your patience nixu

this is from the info screen....
Thu Jan 18 18:23:20 2007

2X Client Gateway running normally
2X Client Gateway running on port 80
RDP direct gateway running on port 3388
Broadcast service running on port 20000
0 active RDP tunneled session(s)
0 active Citrix tunneled session(s)


2X Terminal Server Agent running normally

2X Publishing Agent running normally
Load Balancing 1 server(s)

Active Disconnected
Server Type Agent CPU Memory Sessions Sessions
BPDATA RDP OK 0% 9% 2 0

Server: "BPDATA" running on: Microsoft Windows Server 2003 family Service Pack 1
ID User IP Protocol State Type
0 Administrator 0.0.0.0 Console Active Desktop

As can see it says it's running normally now but still same error

Matthew
 
Ok then, the Terminal server agent is working fine..

Now the issue must be in the published application.

From the Console -> Publishing, select the application and publish from.
Make sure that the setting is either set to All servers, or a ticked group that has BPDATA in it, or individual server and BPDATA server is ticked on.

Nixu
 
You must log in or register to reply here.
Back
Top