11. Troubleshooting

When troubleshooting an error lookup the matching code from this section. If you require further information on what is happening on the thin client follow the instructions on how to contact support in Chapter 8 under the section “Support”.

2X ThinClientOS Boot Process Error Messages

TCMR001 /proc filesystem already mounted!

Corrupt installation detected. Please contact 2X Technical Support.

TCMR002 Installer package not available.

Corrupt installation detected. Please refer to Chapter 6 and review the methodologies for creating a bootable CD from an ISO file. For further assistance please contact 2X Technical Support.

TCMR003 Distribution not found.

Corrupt installation detected. Please refer to Chapter 6 and review the methodologies for creating a bootable CD from an ISO file. For further assistance please contact 2X Technical Support.

TCMR004 Not enough memory to create root partition in ram.

Insufficient memory for correct operation. Please refer to minimum hardware specifications in Chapter 14.

TCMR005 Unable to load unionfs module.

Corrupt installation detected. Please contact 2X Technical Support.

TCMR006 Unable to mount distribution media.

Reconfigure your thin client’s BIOS settings to disable DMA or UDMA features on all IDE channels. Please contact 2X Technical Support.

TCMR007 Distribution version mismatch.

Corrupt installation detected. Please contact 2X Technical Support.

TCMR008 rootdisk.img failed integrity check.

Corrupt installation detected. Please refer to Chapter 6 and review the methodologies for creating a bootable CD from an ISO file. For further assistance please contact 2X Technical Support.

TCMR011 install.img failed integrity check.

Corrupt installation detected. Please refer to Chapter 6 and review the methodologies for creating a bootable CD from an ISO file. For further assistance please contact 2X Technical Support.

TCMR012 Unable to mount rootdisk image.

Corrupt installation detected. Please refer to Chapter 6 and review the methodologies for creating a bootable CD from an ISO file. For further assistance please contact 2X Technical Support.

TCMR015 Unable to mount installer image.

Corrupt installation detected. Please refer to Chapter 6 and review the methodologies for creating a bootable CD from an ISO file. For further assistance please contact 2X Technical Support.

TCMR016 Unable to pivot to new root.

Corrupt installation detected. Please contact 2X Technical Support.

TCMR018 Unable to update rootdisk image.

Hard Disk error detected. Please re-install 2X ThinClientOS to attempt to resolve this issue. If this error persists after repeated re-installation, it is likely that the only solution will be to replace the faulty Hard Disk.

TCMR020 Kernel version is unsupported.

The version of the loaded OS is not a version supported by the 2X ThinClientOS. Check that the correct files were installed on the system. For further assistance please contact 2X Technical Support.

TCMR021 Unable to load USB drivers.

The drivers for USB support on this device were not loaded successfully. Try to change between USB2/USB1 to enable support or disable the driver if the problem persists.

2X ThinClientOS Autoconfiguration Error Messages

TCAC001 No network devices were detected.

A network card was not detected by 2X ThinClientOS. Make sure that a working network card is installed on the thin client. If a network card is correctly installed and you still encounter this problem, please send us the full technical details of the model and manufacturer of the card in question.

TCAC002 No network settings were received from the DHCP service.

If no settings are provided by the DHCP service, or if the settings provided are incomplete, you should consult Chapter 3. The following settings are required for 2x ThinClientOS to boot up:

Should you be doing a PXE install you may optionally need:

TCAC003 Unable to mount root file system read-only.

Corrupt installation; reinstall 2X ThinClientOS.

TCAC004 Unable to mount root file system read/write.

Corrupt installation, reinstall 2X ThinClientOS.

TCAC005 Unable to correct root file system errors.

Corrupt installation, reinstall 2X ThinClientOS.

TCAC006 Started in install mode however installer is not available.

The installation package couldn’t be loaded from the Server or CD/USB.

TCAC007 No settings were received from the 2X ThinClientServer.

2X ThinClientOS was unable to contact the 2X ThinClientServer. Either the 2X ThinClientServer is off, or otherwise inaccessible. Check your firewall configuration.

2X ThinClientOS Update Error Messages

TCUP001 Unable to download latest package version.

No 2X ThinClientOS was uploaded to 2X ThinClientServer. This can be obtained as a ZIP file from:

http://www.2x.com/downloads

Please refer to the chapter entitled “Configuring 2X ThinClientServer”

TCUP002 Unable to download X11R6 package.

There seems to be an error while downloading the Video package for 2X ThinClientOS. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space.

TCUP004 Unable to download rootdisk package.

There seems to be an error while downloading the 2X ThinClientOS package. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space.

TCUP005 Unable to download minird package.

There seems to be an error while downloading the pre-boot image. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space.

TCUP006 Unable to download kernel package.

There seems to be an error while downloading the kernel package for 2X ThinClientOS. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space.

TCUP008 X11R6 package failed integrity check.

A corruption has occurred in the package downloaded from 2X ThinClientServer. This may be due to an error in the file hosted on the 2X ThinClientServer, a network transmission error, or lack of space on the 2X ThinClientOS.

TCUP010 Failed to overlay X11R6 package.

TCUP014 Unable to access temporary filesystem.

2X ThinClientOS has run out of memory used during the update process.

TCUP015 Unable to mount X11R6 package.

TCUP017 Unable to mount services package.

TCUP018 Failed to overlay services package.

TCUP019 Services package failed integrity check.

TCUP020 Unable to download services package.

There seems to be an error while downloading the services package for 2X ThinClientOS. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space.

TCUP024 2X ThinClientServer has insufficient licences to start your session.

2X ThinClientServer has run out of licences while setting up this client. Purchase additional licences to implement more thin clients

TCUP025 2X ThinClientServer licence has expired.

The licence for 2X ThinClientServer has expired. Please purchase a licence to continue using 2X ThinClientServer.

TCUP029 Unable to overwrite kernel with update.

An error has occurred while replacing kernel with a newer version. This may be due to lack of space on the 2X ThinClientOS or a corruption on the hard disk.

TCUP030 Unable to overwrite minird with update.

An error has occurred while replacing a package with a newer version.

This may be due to lack of space on the 2X ThinClientOS or a corruption on the hard disk.

TCUP031 Unable to copy rootdisk update.

An error has occurred while copying new package version to disk. This may be due to lack of space on the 2X ThinClientOS or a corruption on the hard disk.

TCUP034 Unable to remount media as read/write.

An error has occurred while trying to configure hard disk for read/write access. This may be due to a corruption on the hard disk.

TCUP035 Unable to remount media as read-only.

An error has occurred while trying to configure hard disk for read-only access. This may be due to a corruption on the hard disk.

TCUP036 Unable to download install package.

An error has occurred while trying to download package from the network. This may be due to a network transmission error or 2X ThinClientServer is no longer available.

TCUP037 Unsupported running kernel version.

The version of the loaded OS is not a version supported by the 2X ThinClientOS. Check that the correct files were installed on the system. For further assistance please contact 2X Technical Support.

TCUP038 Unable to download checksum list.

An error has occurred while trying to fetch the package integrity checksums. This may be due to a network transmission error or 2X ThinClientServer is no longer available.

TCUP039 Rootdisk package doesn't match checksum.

A corruption has occurred in the rootdisk package. This may be due to an error in the file hosted on the 2X ThinClientServer, a network transmission error, or lack of space on the 2X ThinClientOS.

TCUP040 Minird package doesn't match checksum.

A corruption has occurred in the minird package. This may be due to an error in the file hosted on the 2X ThinClientServer, a network transmission error, or lack of space on the 2X ThinClientOS.

TCUP041 Kernel package doesn't match checksum.

A corruption has occurred in the kernel package. This may be due to an error in the file hosted on the 2X ThinClientServer, a network transmission error, or lack of space on the 2X ThinClientOS.

TCUP043 Installer package doesn't match checksum.

A corruption has occurred in the installer package. This may be due to an error in the file hosted on the 2X ThinClientServer, a network transmission error, or lack of space on the 2X ThinClientOS.

TCUP044 Kernel options do not match checksum.

A corruption has occurred in the boot option settings sent by the ThinClientServer. This may be due to an error in the file hosted on the 2X ThinClientServer, a network transmission error, or lack of space on the 2X ThinClientOS.

TCUP045 Unable to download kernel options.

An error has occurred while trying to download the default boot options from the network. This may be due to a network transmission error or 2X ThinClientServer is no longer available.

TCUP046 No settings were received from 2X ThinClientServer.

2X ThinClientOS was unable to contact the 2X ThinClientServer. Either the 2X ThinClientServer is off, or otherwise inaccessible. Check your firewall configuration.

TCUP047 Unable to download USB packages from 2X ThinClientServer.

An error has occurred while trying to download the packages necessary for USB support. This may be due to a network transmission error or the 2X ThinClientServer is no longer available.

2X ThinClientOS Video Error Messages

TCXS001 Failed to start in graphical mode.

2X ThinClientOS failed to start graphics mode correctly. A VESA compatible video card is required to start in graphical mode. Please contact 2X Technical Support with the exact details of the Manufacturer and Model of the video card used as well as that of the monitor.

TCSX001 No configuration was returned by 2X ThinClientServer.

2X ThinClientOS failed to receive the required configuration file from the 2X ThinClientServer. This could be possible to a misconfigured server or a server mismatch. Please check that the 2X ThinClientServer and 2X ThinClientOS are installed correctly.

TCSX002 Video card driver corrupted.

The video card driver needed for the thin client has been downloaded incorrectly or is corrupted. In the case of CD booting, make sure that the CD was burnt correctly. In the case of HD booting, make sure the ThinClientOS is not running out of disk space. In case of PXE booting, make sure that enough ram is available for the ThinClientOS as described in the minimum requirements section.

TCSX003 Wrong number of parameters in config_device()

The video card has been initialized incorrectly with the wrong set of parameters. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSX004 Internal error.

Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSX005 Wrong number of parameters in config_device_dual()

The video card has been initialized incorrectly with the wrong set of parameters. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSX006 Internal error.

Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSX007 No working configuration was found.

All possible video configurations have been attempted and no working configuration was found. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSX008 Unable to download video card driver.

There seems to be an error while downloading the video card driver for the 2X ThinClientOS. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space

TCSX009 No banner was received from 2X ThinClientServer.

There seems to be an error while downloading the logon banner for 2X ThinClientOS. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space

2X ThinClientOS Sessions Error Messages

TCSP001 Missing session settings, aborting login session.

2X ThinClientServer failed to send one or more required settings. This could be caused by a network transmission error or 2X ThinClientServer is no longer available.

TCSP002 Failed top delete package cache.

An error has occurred while purging the package cache. This could be caused by a system corruption or failing hardware.

TCSP003 Package not available on CDROM.

A required package was not found on the CDROM media. This could be caused by a corrupted CD media or failing hardware.

TCSP004 Missing configuration files.

Required configuration file are no longer available on the system. This could be caused by a corrupted system or failing hardware.

TCSP006 Unable to download package from 2X ThinClientServer.

An error has occurred while downloading package from 2X ThinClientServer. This could be caused by a network transmission error or 2X ThinClientServer is no longer available.

TCSP008 Package failed integrity check.

A corruption has occurred in the package downloaded from 2X ThinClientServer. This may be due to an error in the file hosted on 2X ThinClientServer, a network transmission error, or lack of space on the hard disk.

TCSP009 Unable to mount package.

An error has occurred while loading the package into the system. This may be caused by a network transmission error or hardware failure.

TCSP010 Failed to overlay package.

An error has occurred while configuring the system with the new package. This may be caused by a system corruption or hardware failure.

TCSP011 Unable to copy download package from temporary location.

There seems to be an error while copying a package inside the 2X ThinClientOS. In the case of PXE booting this may be due to insufficient memory on the thin client. If you have performed a Hard Disk installation, this may be due to insufficient space or corruption.

TCSP012 Unable to remove package from local storage.

A system package couldn’t be removed during the update process. This can be due to hard disk corruption or bad memory.

TCSS001 Missing connection settings, aborting login session.

An error has occurred while provisioning settings to the 2X ThinClientOS. Either a corruption has occurred over the line or else there is some misconfiguration in the connection settings. Please double check your connection settings and associated protocol.

TCSS002 Your connection requires an NX session however the client is not available.

The 2X ThinClientOS you are using is designed for a different Terminal Server. Please contact your administrator to obtain a version of 2X ThinClientOS targeted for an NX session.

TCSS003 Your connection requires an RDP session however the client is not available.

The 2X ThinClientOS you are using is designed for a different Terminal Server. Please contact your administrator to obtain a version of 2X ThinClientOS targeted for an RDP session.

TCSS004 Your connection requires an ICA session however the client is not available.

The 2X ThinClientOS you are using is designed for a different Terminal Server. Please contact your administrator to obtain a version of 2X ThinClientOS targeted for an ICA session.

TCSS005 Your RDP session terminated abnormally.

A network error has occurred while connected to your Remote Session. This can be due to incorrect settings or else due to the session being interrupted from the Terminal Server. If this is not the case make sure that the thin client is not experiencing any memory corruption or network outages, or is out of disk space.

TCSS006 Your ICA session terminated abnormally.

TCSS007 Unable to logoff user from session.

A network error has occurred while connected to your Remote Session. This can be due to incorrect settings or else due the session being interrupted from the Terminal Server. If this is not the case make sure that the thin client is not experiencing any memory corruption or network outages or is out of disk space.

TCSS008 Your NX session terminated abnormally.

TCSS009 Empty password is not permitted in an NX session.

An empty password is not permissible to establish a valid session to 2X TerminalServer. Please supply credentials with a valid username and the respective valid, non-empty, password.

TCSS010 Your connection requires a local desktop however the window manager is not available.

A required component to configure your system as a local desktop is missing. This could be caused by a corrupted package.

TCSS011 Your connection requires RDP published applications however the client is not available.

A required component to access RDP publish applications is missing. This could be caused by a corrupted package.

TCSS012 Your desktop session terminated abnormally.

An error has occurred during the desktop session. This could be caused by a corrupted system or faulty hardware.

TCSS013 Your connection requires ICA published applications however the client is not available.

A required component to access ICA publish applications is missing. This could be caused by a corrupted package.

TCSS014 Missing thin client settings, aborting login session

2X ThinClientServer failed to send one or more required settings. This could be caused by a network transmission error or 2X ThinClientServer is no longer available.

TCSS015 Missing session settings, aborting login session

2X ThinClientServer failed to send one or more required settings. This could be caused by a network transmission error or 2X ThinClientServer is no longer available.

TCSS017 An error has occured to populate the 2X managed desktop.

The list of published applications has caused an error in creating the appropriate 2X managed desktop. Reduce the list of published applications to identify which is the problem.

TCSS018 No published applications are available.

The user has no published applications available from the Terminal Server farm. Please check the applications provisioning for the particular user.

TCSS020 No published applications are available.

The user has no published applications available from the Terminal Server farm. Please check the applications provisioning for the particular user. Also check that all IP addresses and ports to the Farm are set correctly and that the username with the given domain and credentials have access to a set of applications.

TCSS021 Unable to populate protocol sessions.

An error has occurred when transferring the list of session settings for the user from the ThinClientServer. This could be due to a network error or due to a missing setting which is still registered to that user.

TCSS022 Unable to retrieve session settings from 2X ThinClientServer.

An error has occurred when transferring the list of session settings for the user from the cached store. This could be due to file corruption or due to a missing setting which is still registered to that user.

TCSS023 The administrator has terminated your session.

The administrator has forcefully stopped your session from the 2X ThinClientServer Management Console.

TCSS025 Your desktop requires Opera but it is not available.

A required component to run the Opera Web browser is missing. This could be caused by a corrupted package or lack of resources on the thin client.

TCSS026 Your desktop requires Flash but it is not available.

A required component to run the Flash plugin inside the Web browser is missing. This could be caused by a corrupted package or lack of resources on the thin client.

TCSS027 Your desktop requires Java but it is not available.

A required component to run the Java Virtual Machine is missing. This could be caused by a corrupted package or lack of resources on the thin client.

TCSS028 The server with your published applications could not be contacted. Check that your network settings are correct.

A problem occurred when trying to contact the published application server due to the network settings that are currently being used by the thin client. Make sure that the server is reachable and that all hostnames and domain suffixes can be resolved. Also check that no ports on the server are blocked. Use the network diagnostics tool to troubleshoot this problem.

TCSS029 Invalid credentials when connecting to <host>.

The credentials supplied to the 2X desktop are not valid for this host. Make sure that the username, password as well as the domain are correct.

2X ThinClientServer (Windows) Slave Redundancy Error Messages

TCSRD001 This is not the master server.

The IP/hostname of the server you provided is not a 2X ThinClientServer in master mode.

TCSRD002 The master cannot reach the slave server.

The external IP/hostname of the slave server is not reachable by the master 2X ThinClientServer. Make sure that the network configuration is correct and that the address is routable. Also, ensure that no ports are blocked by a firewall.

TCSRD003 Schema Mismatch.

The database schema of the master server does not match the one installed on this slave server. Make sure that the versions of the both the master server and of this server match. If the error persists, follow the instructions to generate a debug log and send it to the 2X Support Centre.

TCSRD004 Session Error.

An error has occurred during the replication process. This can be due to a network error or to lack of resources on the master of slave server.

TCSRD005 Invalid console credentials.

The credentials provided for the master 2X ThinClientServer do not match the credentials used in the Management Console. Verify that the credentials are correct in the Management Console and try again.

TCSRD006 Administrator does not have the rights to install new slaves in this farm.

You do not have enough rights to install a slave server. Contact your administrator.

TCSRD007 Cannot get mysqldump.

A critical error has occurred when replicating the database contents. Follow the instructions to generate a debug log and send it to the 2X Support Centre.

TCSRD008 Invalid or expired licence key.

Contact your 2X ThinClientServer sales representative for an Enterprise Edition licence key.

TCSRD051 Cannot open session lock file.

An error has occurred when attempting to read the session lock file. Make sure that you have the sufficient credentials to perform these operations.

TCSRD052 Cannot write session lock file.

An error has occurred when attempting to write the session lock file. Make sure that you have the sufficient credentials to perform these operations.

TCSRD053 Cannot connect to the master server.

The IP/hostname of the master server is not reachable by this server. Make sure that the network configuration is correct and that the address is routable. Also, ensure that no ports are blocked by a firewall.

TCSRD054 Missing parameters.

An internal error has occurred. Follow the instructions to generate a debug log and send it to the 2X Support Centre.

TCSRD055 File transfer error.

An error has occurred during the replication process. Please try again. If the error persists, check that the network connection is working properly.

TCSRD056 File open error.

A required file in the replication process is missing. Ensure that all ThinClientOS images on the master server are installed correctly. If the problem persists, follow the instructions to generate a debug log and send it to the 2X Support Centre.

TCSRD057 File write error.

A required file in the replication process could not be written. Ensure that you have enough permissions to complete the replication process and that there is enough disk space to replicate the master server. If the problem persists, follow the instructions to generate a debug log and send it to the 2X Support Centre.

TCSRD058 Cannot register the slave server.

An error has occurred when registering the slave in the database. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSRD059 Post update schema mismatch.

The schema that was replicated does not match the schema which was originally installed on the slave server. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSRD065 Cannot open server_id.

An error has occurred when trying to identify the ID of the master server. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSRD066 Cannot write server_id.

An error has occurred when trying to register the identity of the slave server. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSRD067 Cannot add new server entry to local database.

An error has occurred when registering the slave in the database. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TCSRD070 Cannot remove directory content.

Ensure that you have enough rights to the folder containing the ThinClientOS images on the slave server.

TCSRD071 Cannot create licence file.

An error has occurred when attempting to write the session lock file. Make sure that you have the sufficient credentials to perform these operations.

TCSRD072 Cannot write licence file.

An error has occurred when attempting to write the session lock file. Make sure that you have enough disk space.

TCSRD073 License file transfer error.

An error has occurred when transferring the licence to the slave server.

TCSRD099 An error has occured in the replication process.

The installation could not be completed successfully due to an error that occurred during part of the installation.

2X ThinClientServer (Linux) Install Error Messages

TSIN001 A critical internal error occurred while executing the installation scripts.

The installation could not be completed successfully due to an error that occurred during part of the installation.

TSIN002 Either critical tools are missing or could not detect critical directories. Please check the 2X files under /tmp.

Before proceeding with the installation the package checks for all the required tools and important directories. This error is displayed if either a required tool or an important directory is missing.

TSIN003 Could not create the directory/file log structure. Please check the 2X files under /tmp.

During the installation a random directoy is created under /tmp that contains the current installation log files. If this directory cannot be created this error message is displayed.

TSIN004 Could not service request <xml request>.

This is a generic error message that is displayed when a particular xml request could not be complete. Please review the error message for more information about what is causing the problem.

TSIN005 Could not read information from the XML report file. Please check that the 2X report file 2Xdetectionreport.xml exists.

This error is displayed when the xml request does not return any information.

TSIN006 The previous installation might be corrupt. Please remove it completely and re-install your latest version.

An error has occurred during the update which does not allow you to use your previous version of 2X ThinClientServer. Uninstall your current versions and install your latest version.

TSIN007 The FQDN and the local hostnames resolve to different IPs.

The IP addresses resolved by the Fully Qualified Domain Name (FQDN) and the local hostname do not match. Please check your network configuration.

TSIN008 The resolved IPs are not bound to any physical interfaces or local hosts.

A safety check is done to determine whether the IP addresses resolved by the Fully Qualified Domain Name (FQDN) and local hostname are bound to a local interface.

TSIN009 Could not resolve both local and FQDN hostnames.

The installation could not resolve both the FQDN and local hostname. This could create an unreachable connection.

TSIN010 Cannot ping the resolved IP. Installation will continue.

The IP resolved by the DNS could not be reached. Please check your network configuration.

TSIN011 Cannot resolve the FQDN. Fixing configuration.

The /etc/hosts file is modified such that the Fully Qualified Domain Name (FQDN) resolves to the local machine.

TSIN012 Either local hostname or FQDN setting is empty. Fixing configuration.

The /etc/hosts file is modified such that the Fully Qualified Domain Name (FQDN) or the local hostname resolve to the local machine.

TSIN013 Cannot resolve local hostname. Fixing configuration.

The /etc/hosts file is modified such that the local hostname resolves to the local machine.

TSIN014 Cannot create or modify the services' users or group .

Each service has its own set of credentials that are created or modified during installation. This error message will be displayed if this process fails.

TSIN015 Could not install/configure the services' wrapper scripts.

Each service is managed by a wrapper script that sets the required paths and libraries. This error occurs if these scripts cannot be configured during installation.

TSIN016 There were errors when setting up the configuration files.

During setup, the configuration files could not be configured with the settings entered by the administrator. Please restart the configuration script and try again.

TSIN017 Could not create important DHCP Helper files or the releases, backup, log files, and upload directories.

Some important files and directories involving the dhcphelper could not be created

TSIN018 Cannot secure critical directories and files.

The setting of permissions during installation was not completed successfully.

TSIN019 Could not register our services in the /etc/services file. Installation will continue.

The installation registers the DHCP Helper service in /etc/services file. If this fails this error will be displayed.

TSIN020 Could not install services start up script.

This error will be displayed if the services start up script could not be installed in the /etc/init.d directory.

TSIN021 Could not remove the MySQL database.

The MySQL database in the /var/opt/2X/thinclientserver/mysql/data/ could not be deleted during installation.

TSIN022 Could not install the MySQL database.

The post-install script could not install the MySQL databases necessary to store configuration information. 2X ThinClientServer installation cannot proceed. The log file indicated will provide further details to identify the issues affecting your server relevant to this error to assist in resolving the issue.

TSIN023 Could not start/stop the MySQL server. Please check both the MySQL error log file under /var/opt/2X/thinclientserver/mysql/data/2XTCSmysql.err and the 2Xlogreport.txt file.

The post-install script could not start/stop the MySQL database engine necessary to store configuration information. The 2X ThinClientServer installation cannot proceed. The log file indicated will provide further details to identify the issues affecting your server relevant to this error to assist in resolving the issue.

TSIN024 Could not install/upgrade the 2X ThinClientServer database.

The post-install script could not update the MySQL databases necessary to store configuration information. The 2X ThinClientServer installation cannot proceed. The log file indicated will provide further details to identify the issues affecting your server relevant to this error to assist in resolving the issue.

TSIN025 Could not secure the the databases directory.

Permissions to secure the database directory for 2X ThinClientServer could not be applied.

TSIN026 Cound not finalise the installation.

While finalising the installation the configuration files could not be identified as being configured properly. This will cause the installation to fail. Please try reinstalling the product.

TSIN027 Could not load the init.d path from detection file. Will try to detect path using the find command.

When uninstalling the product the installer fetches the init.d directory path from the XML file generated during installation. If the XML file is not found the installation will try to find the path using the Find utility.

TSIN028 Could not find the critical directories. Cannot continue the un-installation.

The paths to the init.d and run level directories must be known so that the 2X ThinClientServer service can be removed. If these directories are not found than the un-installation cannot be completed.

TSIN029 Could not load the run level paths from detection file. Will try to detect path using the find command.

When uninstalling the product the installer fetches the run level directory paths from the XML file generated during installation. If the XML file is not found, the installation will try to find the path using the Find utility.

TSIN030 Could not un-install the 2X thinclientserver service and associated links.

This error occurs when the 2X ThinClientServer service and associated run level links cannot be removed from the init.d and run level directories.

TSIN031 Cannot secure directories under /var/opt and /etc/opt or remove the installation directory.

The un-installation process does not remove the data and configuration directories. It only removes the binaries directory. If it fails to either remove the binaries directory or secure the remaining directories this error will be displayed.

TSIN032 Could not remove users/group. Either these do not exist or there were some errors during removal. Please check.

This error occurs if the un-installation process could not remove the services’ user accounts and group.

TSIN033 Could not un-register our services from the /etc/services file. Please check for 2X comment lines and remove.

This error is generated if during un-installation, the DHCP Helper service could not be removed from the /etc/services file. The service can manually be removed by editing the file /etc/services

TSIN034 The machine’s host name starts with a number. Please re-configure the host name if you experience problems.

The machine’s host name should not start with a number. Please check you settings to make sure that it starts with a letter.

TSIN035 Could not create the libexpat.so.0 link.

The installation process checks for the existence of libexpat.so.0 link. If this link is not found the installation process will try to create it. This error is displayed if this link could not be created.

TSIN036 Errors were encountered when un-installing the 2X ThinClientServer AppArmor profiles.

This error only applies if AppArmor is running. During the un-installation process the AppArmor profiles are removed from the /etc/apparmor.d directory. This error occurs when this process could not be completed.

TSIN037 Could not copy database upgrade scripts to the htdocs directory.

This error occurs when the thin client database upgrade scripts could not be copied to the Apache htdocs directory.

2X ThinClientServer (Linux) Configuration Error Messages

TSCS001 A critical internal error occurred while executing the configuration scripts.

An unexpected error occurred during the execution of the configuration script.

TSCS002 Failed to initialize XML report file.

The XML report file could not be created in the /tmp directory.

TSCS003 Failed to detect critical tools.

Some tools that are necessary for the execution of the script are missing.

TSCS004 Could not backup the configuration files.

Before starting configuration the old configuration files are backed up. This error is displayed if this process fails.

TSCS005 Could not create the directory/file log structure.

During the installation a random directory is created under /tmp that contains the current installation log files. If this directory cannot be created this error message is displayed.

TSCS006 The appropriate EULA file for your language setting is missing.

The EULA file for your current language is missing.

TSCS007 A suitable pager, to display the EULA file, was not detected. Please check that you have the less, more, or cat utilities installed.

To display the EULA file on screen one of the following pagers must be installed on the system: less, more or cat. Please install either one of them and restart the configuration.

TSCS008 Could not display the EULA file.

This error can be generated due to a number of reasons. Please check if the EULA file is installed in the /opt/2X/thinclientserver/msgdb/<language>.

TSCS009 Could not restore previous backed up configuration files.

This error is generated if the backed up configuration files are either missing or corrupt.

TSCS010 Failed to detect the path for the init.d directory.

The path to the init.d directory is critical for the configuration script to be able to check, start or shutdown the 2X ThinClientServer services.

TSCS011 Unable to call the startup script due to missing path.

The path to the init.d directory is critical for the configuration script to be able to check, start or shutdown the 2X ThinClientServer services.

TSCS012 No physical network interface was detected.

Your machine does not have a network card installed. Please check your drivers and/or you device if you already have a network card connected to your machine.

TSCS013 Please configure the conflicting services on a different port and run the configuration script again.

This error is displayed when there are services which might conflict with the 2X ThinClientServer services. Please configure these services on a different port and run the configuration script again.

TSCS014 Could not remove the MySQL database.

The MySQL database in the /var/opt/2X/thinclientserver/mysql/data/ could not be deleted during installation.

TSCS015 Could not install the MySQL database.

The configuration script was unable to create the necessary MySQL databases. The 2X ThinClientServer configuration cannot proceed. The log file (/var/opt/2X/thinclientserver/mysql/data/2XTCSmysql.err and the 2Xlogreport.txt) will provide further details relevant to this error to assist in resolving the issue.

TSCS016 Could not start/stop the MySQL server. Please check both the MySQL error log file under /var/opt/2X/thinclientserver/mysql/data/2XTCSmysql.err and the 2Xlogreport.txt file.

The configuration script was unable to start/stop the MySQL server. The 2X ThinClientServer configuration cannot proceed. The log file indicated will provide further details relevant to this error to assist in resolving the issue.

TSCS017 Could not install/upgrade the 2X ThinClientServer database.

The post-install script could not update the mysql databases necessary to store configuration information. The 2X ThinClientServer installation cannot proceed. The log file indicated will provide further details to identify the issues affecting your server relevant to this error to assist in resolving the issue.

TSCS018 Could not secure the the databases directory.

Permissions to secure the database directory for 2X ThinClientServer could not be applied.

TSCS019 Could not configure the Apache Web service.

The Apache Web service used to display the 2X ThinClientServer interface could not be configured.

TSCS020 Could not configure the DHCP Helper service.

The DHCP Helper service used during PXE booting of thin clients could not be configured.

TSCS021 Could not configure the TFTP service.

The TFTP service used to serve the kernel and root disk images during PXE booting of thin clients could not be configured.

TSCS022 Could not backup the XML report and log files.

When the configuration finishes, the XML report and log files are backed up for safe keeping. This error is displayed if the backing up process fails.

TSCS023 The appropriate SELinux file for your language setting is missing.

The SELinux read-me file for your current language is missing

TSCS024 Could not display the SELinux file.

Please check if the SELinux file is installed in the /opt/2X/thinclientserver/msgdb/<language>.

TSCS025 Could not perform a backup of the audit log file under /var/log/audit.

A backup of the /var/log/audit file is saved before the audit log is cleared. This error occurs if the backup operation fails

TSCS026 Could not determine the necessary SELinux rules to add to the configured policy.

If SELinux has been enabled, the configuration script will check whether the 2X ThinClientServer services will run properly. If this is not the case, SELinux rules are determined so that the services can be run properly. This error will be displayed if no rules can be detected.

TSCS027 Could not display the SELinux rules file. Please check under /var/opt/2X/thinclientserver/backup directory.

The SELinux rules are saved to a file in the /var/opt/2X/thinclientserver/backup directory. This is done so that the user can confirm whether he/she wants the rules to be applied to the installed SELinux policy. This error is displayed if the rules file is missing.

TSCS028 Could not detect the installed policy name.

The configuration script could not detect the installed SELinux policy name.

TSCS029 Unable to install the necessary packages.

The configuration script could not install the necessary SELinux packages to be able to configure the SELinux policy.

TSCS030 Could not backup the current policy directory.

Before attempting any SELinux policy configuration changes, the old policy directory is backed up. If the backup process fails, this error will be displayed.

TSCS031 Failed to append the custom rules to the policy’s local.te file.

The configuration script failed to add the SELinux determined rules to the policy’s local.te file.

TSCS032 Unable to rebuild and load the new policy.

The SELinux policy was not rebuilt and reloaded successfully. This is necessary for changes to the policy to take effect.

TSCS033 Failed to compile the 2Xthinclientserver policy module.

The 2Xthinclientserver policy module failed to compile. This is necessary before packaging and loading the module.

TSCS034 Could not package the compiled 2Xthinclientserver policy module.

The SELinux tools failed to package the compiled 2Xthinclientserver policy module.

TSCS035 Could not move the new 2Xthinclientserver policy module to the policy share directory.

The configuration script failed to copy the new 2Xthinclientserver policy module to the policy share directory. This is necessary before loading the 2Xthinclientserver policy module.

TSCS036 Could not load the new 2Xthinclientserver policy module.

The configuration script failed to load the new 2Xthinclientserver policy module from the policy share directory. This is necessary for the policy changes to take effect.

TSCS037 Could not switch SELinux to permissive mode.

The configuration script failed to set the SELinux state to permissive mode before trying to determine the SElinux rules.

TSCS038 Could not switch SELinux to enforcing mode.

The configuration script failed to set the SELinux state to enforcing mode before trying to test whether the 2X ThinClientServer services started correctly.

TSCS039 Could not populate the list of AppArmor profiles to install.

If AppArmor is enabled a set of profiles is installed into the /etc/apparmor.d directory. This process cannot be done if the configuration script cannot acquire the list of the profiles to install.

TSCS040 Could not configure AppArmor profiles.

Due to the RPM package being re-locatable, the AppArmor profiles must be configured with the new installation path. The AppArmor profiles cannot be activated unless they are configured.

TSCS041 Could not install AppArmor profiles under /etc/apparmor.d directory.

This error will be displayed when the configured profiles cannot be copied in the /etc/apparmor.d directory. This could be either a question of permissions or a case of missing profiles.

TSCS042 Could not activate AppArmor profiles.

After the profiles are copied to the /etc/apparmor.d directory, they must be activated for them to take effect. This is done by reloading all AppArmor profiles in the /etc/apparmor.d directory. Check that the 2X ThinClientServer profiles have been copied in the /etc/apparmor.d directory.

TSCS044 Failed to setup master server.

An error has occurred while setting up the master server. This might due to an error while setting the master values in the MySQL database. Please check for errors in the 2X log files located in the /tmp/2Xlatestlogdirectory directory.

TSCS045 Unable to start the necessary services to configure installation.

The Apache and MySQL services must be started before the installation is configured as either master or a slave server. Please check for errors in the 2X log files located in the /tmp/2Xlatestlogdirectory directory.

TSCS046 Cannot reload installed policy.

After the necessary changes, the SELinux policy must be reloaded for the changes to take effect.

TSCS047 Unable to clear shared memory. Please clear it manually by using the ipcrm and ipcs tools.

At the start of the configuration process, the shared memory is cleared to minimise the chances of errors during configuration. If this fails, use the ipcrm and ipcs tools to find and clear the shared memory segment allocated to the 2X ThinClientServer.

TSCS055 An error occurred when closing the XML report file.

An XML report file element could not be properly closed, making the file not well formed.

2X ThinClientServer (Linux) Slave Redundancy Error Messages

TSRD001 This is not the master server.

The IP/hostname of the server you provided is not a 2X ThinClientServer in master mode.

TSRD002 The master cannot reach the slave server.

TSRD003 Schema mismatch.

TSRD004 Session error.

An error has occurred during the replication process. This can be due to a network error or to lack of resources on the master of slave server.

TSRD005 Invalid console credentials.

TSRD006 Administrator does not have the rights to install new slaves in this farm.

You do not have enough rights to install a slave server. Contact your administrator.

TSRD007 Cannot get mysqldump.

A critical error has occurred when replicating the database contents. Follow the instructions to generate a debug log and send it to the 2X Support Centre.

TSRD008 Invalid or expired licence key.

Contact your 2X ThinClientServer sales representative for an Enterprise Edition licence key.

TSRD051 Cannot open session lock file.

An error has occurred when attempting to read the session lock file. Make sure that you have the sufficient credentials to perform these operations.

TSRD052 Cannot write session lock file.

An error has occurred when attempting to write the session lock file. Make sure that you have the sufficient credentials to perform these operations.

TSRD053 Cannot connect to the master server.

TSRD054 Missing parameters.

An internal error has occurred. Follow the instructions to generate a debug log and send it to the 2X Support Centre.

TSRD055 File transfer error.

An error has occurred during the replication process. Please try again. If the error persists, check that the network connection is working properly.

TSRD056 File open error.

TSRD057 File write error.

TSRD058 Cannot register the slave server.

An error has occurred when registering the slave in the database. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TSRD059 Post update schema mismatch.

The schema that was replicated does not match the schema which was originally installed on the slave server. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TSRD065 Cannot open server_id.

An error has occurred when trying to identify the ID of the master server. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TSRD066 Cannot write server_id.

An error has occurred when trying to register the identity of the slave server. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TSRD067 Cannot add new server entry to local database.

An error has occurred when registering the slave in the database. Follow the instructions to generate a debug log and send them to the 2X Support Centre.

TSRD070 Cannot remove directory content.

Ensure that you have enough rights to the folder containing the ThinClientOS images on the slave server.

TSRD071 Cannot create licence file.

An error has occurred when attempting to write the session lock file. Make sure that you have the sufficient credentials to perform these operations.

TSRD072 Cannot write licence file.

An error has occurred when attempting to write the session lock file. Make sure that you have enough disk space.

TSRD073 License file transfer error.

An error has occurred when transferring the licence to the slave server.

TSRD099 An error has occurred in the replication process.

The installation could not be completed successfully due to an error that occurred during part of the installation.