User Guide Support Frequently asked questions

 Troubleshooting power outage-related problems

Troubleshooting power outage-related problems

A discussion of typical issues you may experience after a power outage, and their solutions.

Repository problems

• Unable to connect to a repository

  Problem: A power outage causes data synchronization between a primary and replication repository server to be interrupted. When you attempt to connect to a TestArchitect repository, you receive one of the following error messages:

  • Case #1:
    
    

  • Case #2:

    Cannot access repository <name of repository>. Server: TATCPIPReceiver.receiveData(): The TCPIP Receiver received a number of read bytes < 0. In particular, number of read bytes has value is ‘-1’. This means that the socket was timeout or was closed by another thread or remote client. So we break here.

  Solution: The repository is corrupted and should be deleted:

  1. Stop the repository server.
  2. Go to the following location:
     • Windows: C:\Users\Public\LogiGear\TestArchitect\RS\database\
     • Linux: /usr/local/logigear/testarchitect/data/rs/database/
     • macOS: /Application/TestArchitect/data/rs/database/
  3. Delete the folder containing the corrupted repository.
  4. Start the repository server.

• Data synchronization no longer works

  Problem: Data synchronization between a primary and replication repository server no longer functions after recovery from a power outage.

  Solution: To remedy this problem, do the following:

  1. Re-setup the primary/replication repositories.
  2. Restart the primary and replication repository server machines.

License Server

Unable to start TestArchitect License Server

Problem: After a power outage, TestArchitect License Server cannot be started, even though the Start button is enabled on the License Server Control Panel.

Solution: Perform a clean installation of the license server:

1. Uninstall TestArchitect License Server.
2. Reinstall TestArchitect License Server.

TestArchitect Client

• Unable to start TestArchitect

  Problem: After a power outage, TestArchitect occasionally cannot be launched.

  Solution: Perform a clean installation of TestArchitect:

  1. Uninstall TestArchitect.
  2. Restart your machine.
  3. Reinstall TestArchitect.

• Unable to show content on a test module editor

  Problem: A power outage occurs during the check-out process of a test module. Upon opening the test module in the editor, the file appears to be empty.

  Solution: The data file is most likely corrupt. To resolve this issue:

  1. In TestArchitect, disconnect from the repository containing the test module.
  2. Reconnect to the repository.