How To: Troubleshoot a non-working client

Table Of Contents

Check for an Error Log
Things to Check
Additional Information
Advanced User Feature
Troubleshooting a Khaos Control client that fails to load requires a good understanding of Windows permissions, network access and SQL Server connectivity.
There are a limited number of common issues that can prevent Khaos Control from starting successfully. This guide explains the most likely causes and where to look for diagnostic information.

Check for an Error Log

When Khaos Control fails to start, an ErrorLog.txt file is usually created automatically.
The file is typically located in the:

KeystoneSoftware\Applic folder, which is normally the same location specified in the shortcut's Start In property.

The error log contains detailed information that can help identify the cause of the problem.

Tip: Always check the ErrorLog.txt file first, as it often identifies the exact issue preventing Khaos Control from loading.


Common Causes of Startup Problems


1. Shortcut Configuration Problems


The Khaos Control shortcut may be unable to:

  1. Run the program specified in the Target field.
  2. Access the folder specified in the Start In field.

Things to Check

  1. The executable file still exists in the Target location.
  2. The Start In folder exists.
  3. The user has permission to access both locations.
  4. Network drives referenced by the shortcut are available.

2. Registry Permission Issues

Khaos Control requires access to the KeystoneSoftware registry key.
If the application cannot read from or write to this registry location, it may fail to start.

The affected registry location is:

HKEY_LOCAL_MACHINE under the KeystoneSoftware key.
​
Things to Check
​
The registry key exists.
The user has the required permissions.
Security software has not restricted access.
​
Warning: Modifying the Windows Registry should only be performed by experienced administrators

3. Shared Folder Access Problems
​
Khaos Control stores and reads data from shared KeystoneSoftware folders.

The application may fail if it cannot:

  1. Read files from the shared location.
  2. Create files in the shared location.
  3. Modify files or folders where required.

Things to Check
  1. ​The shared drive is available.
  2. Network connectivity is working.
  3. Folder permissions allow read and write access.
  4. The user account has the correct security permissions.

4. SQL Server Connectivity Issues

Khaos Control requires access to the SQL Server instance hosting the database.
Startup will fail if the application cannot connect to the server or database.

Things to Check

  • The SQL Server service is running.
  • The database server is online.
  • Network connectivity exists between the workstation and server.
  • Firewalls are not blocking SQL communication.
  • Database login credentials are valid.
  1. Attempt to start Khaos Control.
  2. Locate and review the ErrorLog.txt file.
  3. Check the shortcut Target and Start In locations.
  4. Confirm access to the KeystoneSoftware shared folders.
  5. Verify registry permissions.
  6. Confirm SQL Server connectivity.
  7. Retry launching Khaos Control after resolving any identified issues.

Additional Information

Common symptoms include:
  • Nothing happens when launching Khaos Control.
  • An error message appears immediately.
  • The splash screen appears briefly and then closes.
  • The application hangs during startup.
In most cases, the ErrorLog.txt file will provide enough information to identify whether the issue relates to permissions, network access, file locations or SQL Server connectivity.

Did you find this article helpful?