After initially being unable to activate ApexSQL Audit 2021, as the manual activation dropdown only listed 2023 and 2024 versions, then after upgrading to ApexSQL Audit 2024, the installation process stalled at the final step and did not complete successfully. After performing a clean installation to allow successful activation, immediately afterwards, the GUI becomes unresponsive during server data retrieval, showing “retrieving server” indefinitely.
Reviewing the application logs reveals multiple SQL-related exceptions such as:
- Invalid column name 'Deleted', 'EventId', 'Resolved', 'Summary'
- Invalid object name 'ApexSQL.AlertReportsProxyView'
- Error: “An error occurred while processing request on central instance”
- Stack traces referencing ApexSQL.Audit.Shared.Crd.FluentApi.EntitySet and CrdInstaller.UpgradeTo2024_01_2240
These errors indicate potential schema inconsistencies between the database and application version — likely caused by a failed or incomplete upgrade process.
Check to confirm:
1. Whether the repository upgrade or migration failed.
2. If the Central repository schema became incompatible with the new 2024 build.
3. How to validate and repair the schema to restore normal functionality.
1. Confirm that only ApexSQL Audit 2023 and 2024 appears as manual activation options.
2. Recommend to upgrade to 2024 and activate that version.
3. Verify that installation froze at the final step and did not deploy correctly.
4. Check Admin rights, disable antivirus, ensure all services are stopped, and review Event Viewer (Application Hang Event ID 1002).
5. Try running the installer again, confirming .NET 4.7.2+, clearing Temp, and applying Windows updates.
6. After several failed attempts, try performing a clean installation
7. Post-installation, the GUI may freeze with “retrieving server” errors, and logs showing missing SQL objects.
Please perform a complete clean installation and reset the ApexSQL repository.
Recommended Steps:
1. Open the ApexSQL Audit UI and stop all auditing services.
2. Back up configuration, reports, scheduled reports, and custom alerts (if needed).
3. Remove all registered servers from the UI.
4. Uninstall all ApexSQL Audit components.
5. Rename the ApexSQLCrd database to ApexSQLCrdOld.
6. Rename the following folders (if present):
- C:\Program Files\ApexSQL
- C:\ProgramData\ApexSQL
- The Temp package folder (location available in SSC logs).
7. If any folder cannot be renamed, verify that no ApexSQL services or sessions are still running. In such cases, schedule a remote support session for assistance.
8. Restart the server.
9. Run the ApexSQL Audit 2024 installer again.
After completing these steps, the application should install successfully, activate properly, and the “retrieving server” issue should no longer be observed.
