www.gsx.com | log in | register

Last update: . Author: Christian Stokes .

Repairing a Corrupt GSX Analyzer Database

A database is a system file, this means that any issue with writing to disk can cause a database corruption. When the GSX Analyzer database becomes corrupt, you may notice specific error messages when logging into GSX Analyzer, or when managing the database via GSX Analyzer Manager.

This article shows how to identify and repair a corrupt GSX Analyzer database.

GSX Analyzer


  • An error has occurred when verifying login : GetWSCheckLogin: I/O error for file "GsxAnalyzer". 
  • ERROR: Backup Error : Exception of type 'FirebirdSql.Data.Common.IscException' was thrown. 

How to Solve the Issue

To fix the GSX Analyzer database we need to:

  1. Stop the GSX Analyzer Agent and restart the Firebird Server services.
  2. Run the GSX Analyzer Database Repair Utility.
  3. Compact the GSX Analyzer Database.

Stop the GSX Analyzer Agent and restart the Firebird Server Services:

  1. Launch Services.msc to open the Windows Services Manager.
  2. Stop the GSX Analyzer Agent service:
  3. Restart the Firebird Server Service:

Run the GSX Analyzer Database Repair Utility

  1. Open a Windows Elevated Command Prompt.
  2. Run one of the following commands depending on the Firebird bit version:

For 64-bit Firebird, use:

  • C:\Program Files\Firebird\Firebird_2_0\bin\gfix -mend -full -ignore -user SYSDBA -password "masterkey" localhost:"<GSX Analyzer install path>\Config\Analyzer.fdb"

For 32-bit Firebird, use:

  • C:\Program Files (x86)\Firebird\Firebird_2_0\bin\gfix -mend -full -ignore -user SYSDBA -password "masterkey" localhost:"<GSX Analyzer install path>\Config\Analyzer.fdb" 

In this example, GSX Analyzer is installed on drive D: of a 32-bit operating system:

Compact the GSX Analyzer Database

  1. From the Start menu, navigate to All Programs > GSX > GSX Analyzer Administrative Tools > GSX Analyzer Manager.
  2. Select Database.
  3. Select Compact Database.
  4. Once the compaction is complete, click Yes to confirm the database deletion:
  5. Close the GSX Analyzer Manager.
  6. Start the GSX Analyzer Agent from Services.msc.
  7. Launch GSX Analyzer and log in to verify that everything is now working as expected:

Was this article helpful?

1 out of 2 found this helpful

Not finding what you are looking for?

Have more questions? Submit a request