Cybersecurity
DevOps Cloud
IT Operations Cloud
Fortify SSC 24.4
User updating SSC server from 23.1 to 24.4 and facing the following seeding error.
This happens when seed "Fortify_Process_Seed_Bundle-2024_Q2_0006.zip" file.
[INFO] com.fortify.manager.DAL.HibernateDatabaseInterface - Using JDBC driver MariaDB Connector/J [3.1.4], connecting to MySQL [8.0.35] [WARN] com.fortify.manager.service.scheduler.NullSchedulerServiceImpl - Null scheduler service instance, analysis trace refresh not scheduled [WARN] org.mariadb.jdbc.message.server.ErrorPacket - Error: 1062-23000: Duplicate entry '22-85155-3' for key 'user_pi.PRIMARY' [WARN] org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 1062, SQLState: 23000 [ERROR] org.hibernate.engine.jdbc.spi.SqlExceptionHelper - (conn=159) Duplicate entry '22-85155-3' for key 'user_pi.PRIMARY' [INFO] com.fortify.manager.service.objectstorage.ObjectStorageMigrationServiceImpl - Ignoring request to stop object storage migration - it is not running or stop has already been requested. [ERROR] com.fortify.ssc.init.endpoints.AppInitDatabaseOperationsController - Unable to seed all init seed bundles. com.fortify.ssc.init.SeedingException: Unable to seed all init seed bundles. at com.fortify.ssc.init.SeedContextProvider.seedInitBundles(SeedContextProvider.java:114) ~[ssc-init-24.4.0.0336.jar:?] at com.fortify.ssc.init.endpoints.AppInitDatabaseOperationsController.lambda$seed$2(AppInitDatabaseOperationsController.java:270) ~[ssc-init-24.4.0.0336.jar:?] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.base/java.lang.Thread.run(Thread.java:840) [?:?] Caused by: com.fortify.manager.exception.FMDALGeneralException: An unexpected error occurred.
Find resolution on support portal