Troubleshooting your installation

Need a hand with your installation? Did you have trouble installing the product? This section describes basic installation issues and provides troubleshooting information.

Unable to start the Database Server because the path to the socket file is too long

If the path to the socket file (including separators and the name of the socket file) is greater than 107 characters, you will be unable to start the Validate Database Server. The database log will indicate that this is the problem.

The socket file is located in the following directory:

<projects_root>/locks

To remedy this situation, move your projects to another projects_root with a path length of less than 68-72 characters, depending on the length of the Database Server port number (which can be 1 to 5 characters).

Unable to start Validate Servers following Windows installation

If you see one of the following messages after installing the Validate Server package on Windows:

  • Error 1920. Service Validate 24.3 Server (Validate 24.3 Server) failed to start. Verify that you have sufficient privileges to start system services.
  • Service Validate 24.3 License Server failed to start. See installation log for more details.

An earlier version of the Validate Server and/or Validate License Server may be running on the port that you specified during installation of Validate 2024.3. It is not possible to run two versions of a server on the same port.

You need to set a different port number for the Validate Server and/or Validate License Server with validate service set-service-property, and then start the servers.

Database connection error

Do not locate the projects_root directory on NFS to avoid issues with file locking.

If you see the following error:

Error occurred while connecting to database: Database connection to <database> refused: Communications link failure due to underlying exception

Check the host name in the error message. If the host name is not a fully qualified host name that includes the domain (for example, server1.Validate.com), you need to set the fully qualified domain name for the Database Server.

To do this:

  1. Stop the Database Server: 
    validate service --projects-root <projects_root> stop database
  2. Run the following command: 
    validate service --projects-root <projects_root> set-service-property database host <fully-qualified-host-name>
  3. Start the Database Server: 
    validate service --projects-root <projects_root> start database