Jetro CockpIT™ Version 3.0 Knowledge Base
     

:: Quick search Users Cannot Access the CockpIT Logon Page Login Button Does Not Work Single User Cannot Access CockpIT Login Fails for All Users CockpIT Administrator Cannot Access the Site Jetro Client Failed to Download, Operate, or Install Users Cannot Launch Programs Now but Could Before Application Launching and Closing Takes a Long Time User Does Not Get a Newly Defined Application Specific Application Sometimes Works and Sometimes Doesn't White Screen Appears Instead of an Application Terminal Server Asks for Username and Password Terminal Server Fails to Communicate with CockpIT "No server available" Error Message Newly Defined Users or Groups Can Not Be Added to a Security Policy "Maximum concurrent users reached" Error Message "Failed to check in, wrong login parameters" Error Message Jetro Client Failed to Login Automatically When Restarting Computer Configuring CockpIT for the NAT Environment Removing CockpIT Plug-in Files Changing the Domain to Which CockpIT is connected to Determining the size of the Directory Service Optimizing CockpIT Synchronization with Directory Service Creating a Server Failure Alert Script Creating a Load Balancing File Changing a Server's Load Balancing File Backing-up CockpIT Data, Files, and Site Icons Restoring the CockpIT Administrated Server Farm JdsWebClient.dll or MstsCax.dll Can Not Be Found Failed to Trigger Application

JKB00314 A Terminal Server Fails to Communicate with CockpIT Symptoms: · After installing the Terminal server agent, no new line appears in the “Load Monitor” page in the CockpIT admin site · Previously working terminal server stopped communicating with CockpIT and a red server icon shown in the 'Load Monitor' page Possible Causes: · Terminal server cannot resolve the CockpIT Server host name · Jhgate Service on the terminal server has stopped or is not working · The load balancing policy file is corrupted or missing. · The performance monitor on the terminal server is not working Possible Resolutions: · Check the terminal server Jhgate service status on the services program. 1. Restart the service and check the application log on the event viewer. Jhgate reports to the Event Viewer about success or failure in reading the Registry setting and initiating the PerfPolicy.xml settings file. 2. Check the network connectivity of the CockpIT Server. 3. Ping the CockpIT Server name and IP address. · Check the registry settings in the terminal server. The CockpIT Server name (netbios name) is defined in two different Registry keys. HKEY_LOCAL_MACHINE\SOFTWARE\Jetro\jhgate\PerformanceMonitor: DispatchUrl = http://server name/cockpit/bin/wgate.dll RemoteHost = server name · You can copy the value of the 'DispatchUrl' and paste it in Start - Run and see if you get the Wgate.dll version shown in Internet Explorer window. · Lastly, un-install the Terminal Server Agent and re-install it.   Back to top