Operational Defect Database
BugZero found this defect 1322 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000bpYZSAY
AD helper fails to start with error message: Found non-empty schema(s) "PUBLIC" but no schema history table
Last update date:
10/5/2020
Affected products:
TDR
Affected releases:
Any/Unknown
Fixed releases:
All
Description:
Issue
The TDR AD Helper service stores its configuration details in a database in the %WINDIR% directory of the host in which it is installed. If this database is missing or damaged, the AD helper service will fail to start. If the AD helper service does not start, check the the AD helper log file located at C:\Program Files (x86)\WatchGuard\Active Directory Helper\logs\helper.log for this message: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flyway' defined in com.watchguard.hawkeyeg.helper.database.spring.configuration.HelperEntityManagerConfig: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "PUBLIC" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
Workaround/Solution
To resolve this issue, you must reinstall AD helper to correct the database: Uninstall the existing AD Helper.Download the latest version of AD Helper from the TDR web UI. Note: If you are using a 32-Bit JRE you must also delete %WINDIR%\sysWOW64\config\systemprofile\helperapp\ before reinstalling AD Helper. Install the new AD Helper.Configure AD Helper with the account UUID and domain credentials.
