• Overview
• FAQ
• Documents
• Knowledge Base
• Download Center
• Patches and Updates
• Contact Support

Home >> Support >> FAQ

Troubleshooting FAQs

ThinPATH PC Suite and ThinPATH Portal

ThinPATH PC devices will not register with the Portal server
ThinPATH PC One Click Install does not auto-define Portal server IP Address
ThinPATH PC Fails to download RDP connections from Portal Server
ThinPATH PC One Click Install Displays Memory Exception Error in IE 8

ThinPATH PC devices will not register with the Portal Server

If you have just installed the ThinPATH Portal software on a Windows 2003 server with either SP1 or SP2 and the ThinPATH PC devices will not register with the ThinPATH Portal Server or in the list of managed devices in the ThinPATH Portal Explorer window, no devices are present. Also when looking in the event viewer on the Windows 2003 server you also get the error:

  The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {9D213191-F074-4F96-94E5-ABE12D40D6AE} to the user TPSEXCH\IUSR_TPSEXCH SID (S-1-5-21-1759471975-1393815153-4041956381-1003). This security permission can be modified using the Component Services administrative tool.

Solution Details

The line “Server.CreateObject("NCDPortalService.NCDXmlReg")” in the TERMXml.asp page is trying to access a DCOM object 9D213191-F074-4F96-94E5-ABE12D40D6AE=NCDXmlReg and the user IUSER_TPSEXCH does not have Launch or Activate permission so the Web server replies with Error 500.

  1. To change the permissions for the NCDPortalServe DCOM object, Click Start, and then select the Control Panel.
  2. Next select Administrative Tools, and then Component Services.
  3. In the Component Services snap-in, expand Computers, next expand My Computer, and double-click DCOM Configuration.
  4. In the right pane of the DCOM Configuration window, locate the program NCDPortalService.
  5. Right-click on the program name, and then select Properties.
  6. On the Security tab in the Launch and Activation Permissions group box, select Customize and then click Edit.
  7. Add the user IWAM_<your_server> and IUSER__<your_server> as users and all Launch and Activation to Allow. The value <your_server> should be the local Windows Server name and not the Windows Domain name. Pick these two names from the Users and Groups window with the "From This Location" set to the name of the local host not your WIndows Domain. The user that needs to be granted use of the NCDPortalService resources is defined by the local IIS serervice on the local Windows 2003 server.
  8. Save and Exit
  9. Restart IIS.
  10. Restart the ThinPATH PC Device.
  11. Open the ThinPATH Portal Explored UI and the device will now be present. In case you are still having problems check to make sure the Event viewer errors are no longer present. If still present recheck you settings under step 7 above.

 back

ThinPATH PC One-click Install does not auto-define Portal server IP Address

When using the One-click Install to install ThinPath PC from a ThinPATH Portal server running version 4.1 the Management Server setting is not automatically set. One of the files associated with the One-click Install was not correctly created during installation of the ThinPATH Portal Server. When you open the ThinPATH PC Properties window you will see the setting for the Management Server is not set. Without this setting correctly defined the ThinPATH PC Client software will not be able to communicate to the ThinPATH Portal Server to get Updates, Configuration changes and Licensing information.

  When Installing ThinPATH PC or running the ThinPATH PC Client software on a Windows 2000 or XP end user PC you must be logged in as a user with local Administrative rights. Previsions are provided in ThinPATH PC to restrict PC access. The security settings are accessible through the ThinPATH PC Properties window.

Solution Details

There are two different solutions you can use to solve this issue. 1) you can just set the correct setting for the "Management Server" setting in the ThinPATH PC Properties window ( <IP Address of Portal Server>/TMS ) on the PC where ThinPATH PC was installed or 2) follow the steps below to correct the file on the server associated with the ThinPATH PC One-click Install.

  1. To have the Management Server setting automatically set during installation using the ThinPATH PC One-click Install will require editing one file on the ThinPATH Portal Server.
  2. On the ThinPATH Portal Server login as Administrator.
  3. Open File Explorer and open the file "Setup.htm" using Wordpad so it can be modified. The file is normally located in "C:\Program Files\NCD\ThinPATH Management\TPPC\PC Client\OneClickInstall" unless during installation a different drive other than C: was selected.
  4. On the first line of the file you will see:
    ether.SetProperty("ManagementServer", "<serverIP>/TMS");
    This line needs to be removed and replaced with:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
  5. Next search for line "//Ready to install" in the file.
  6. Just above this line listed in step 5 install the code below.
    // PC Client Installation Properties
    ether.SetProperty("AutoLogon", false);
    ether.SetProperty("LogonName", "Administrator");
    ether.SetProperty("LogonPassword", "Password");
    ether.SetProperty("UseLocalDomain", true);
    ether.SetProperty("LogonDomain", "any_domain_name");
    ether.SetProperty("ManagementServer", "10.0.0.100/TMS");
    ether.SetProperty("PortalURL", "ThinPATH%20Portal/TermAccess/TERMXml.asp");
    ether.SetProperty("GUI", true);
    ether.SetProperty("Autohide", false);
    ether.SetProperty("AutoRestart", false);
  7. Change the IP address 10.0.0.100 in the code just added to the IP address of your Server. Leave all other lines unchanged.
  8. Save the changes to the file.
  9. BackNow perform the ThinPATH PC One-click Install following normal procedures.

 back

ThinPATH PC Fails to download RDP connections from Managed Groups defined in Portal Server.

New to IIS in Windows 2003R2/2008 is tougher security which caused downloads of most file types to be disabled. ThinPATH PC transfers these configuration files via HTTP from the ThinPATH Portal Servers through IIS Web Services. After defining a Managed Group on the Portal Server and pushing the configuration to a managed Thin PATH PC device it fails to download any RDP connection information. When the .rdp file is requested for download by the ThinPATH PC device it is refused by the IIS Web Server. The result is a incomplete RDP connection definition on the ThinPATH PC device.

Solution Details

By default in IIS you can add MIME type definitions to enable certain file types to downloaded from the IIS Web Server. The MIME type can be defined to a Virtual Directory under IIS so as not to allow global file downloads of a specific type. This insures the security of IIS on your network is not compromised. samebperform the steps below. To allow .rdp files to be downloaded, perform the steps below to add the necessary MIME type to the IIS Web Server..

  1. Login as the Administrator on the Windows Server where the ThinPATH Portal Software was installed. Open the IIS Internet Information Services management window.
  2. Select the Server name, Web Site, Default Web Site, TMS. TMS is the Virtual Directory created when the ThinPATH Portal Software was installed .
  3. With TMS Selected right click and select Properties to open the TMS Properties window.
  4. In the TMS Properties window select the tab "HTTP Headers" .
  5. In the lower left of the window click the Button "MIME Types...".
  6. The MIME Types window lists the types of files the Web Server is allowed to access. If the .rdp extension is not included in the list then it should be added..
  7. Click on the New button to add the .rdp MIME Type.
  8. In the MIME Type window enter ".rdp" in the Extension field and "application/octet-stream" in the MIME Type field.
  9. Next click the OK button and then OK again.
  10. Click on Apply button to Save the changes, and OK to exit from IIS..

Back back

ThinPATH PC One Click Install Displays Memory Exception Error in IE 8

New to IE 8 is tougher security with addition of Data Execution Prevention and expanded Memory Protection. By default this is enabled which blocks the One-click Install from running. As soon as entering the URL "http://PortalServer/PC Client" in the Browser window to install the ThinPATH PC Client component IE immediately aborts its operation and displays a Memory Exception Error.

  When Installing ThinPATH PC or running the ThinPATH PC Client software on a Windows 2000 or XP end user PC you must be logged in as a user with local Administrative rights. Previsions are provided in ThinPATH PC to restrict PC access. The security settings are accessible through the ThinPATH PC Properties window.

Solution Details

By default in IE 8 the setting "Enable memory protection to help mitigate online attacks" is enabled by default. This setting needs to be temporary disabled it you want to use the One-click Install feature. To disable this feature perform the steps below.

  1. To temporary disable "Enable memory protection to help mitigate online attacks" open IE 8.
  2. In the Tools pull down menu select Internet Options and select the Advanced tab.
  3. Scroll down the list till you see the section labeled Security.
  4. Uncheck the item "Enable memory protection to help mitigate online attacks".
  5. Save settings and close IE 8.
  6. Open IE 8 and enter the URL "http://PortalServer/PC Client" where PortalServer is the IP address of DNS name of the ThinPATH Portal Server.
  7. Perform the One-click Install as instructed.
  8. When the installation has completed, before rebooting open the Security settings in IE 8 again and check "Enable memory protection to help mitigate online attacks".
  9. Save the changes in IE 8 and reboot as requested.

Back back