ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.
This website uses cookies. By continuing to browse or login to this website, you consent to the use of cookies. Learn more.
OK
nathaniel_clien
Absent Member.
Absent Member.
‎2016-02-22 07:24 PM
4615 views

Unable to initialize IndexManager com. fortify.manager.DAO.alert.AlertDefinition - after 4.40 upgrade

Ran into this error in SSC.log when starting Tomcat after completing the upgrade.  Has anyone seen this error or know how to correct?

0 Likes
Report Inappropriate Content
1 Reply
mfeferman
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
‎2016-02-24 12:09 AM

Is this because you don't have a directory for the indexing stuff to be written to?  When you go through SSC configuration, there is a location to specify a directory for the database indexing.  I didn't have one and SSC failed to start, but upon creating one, it worked flawlessly.

0 Likes
Report Inappropriate Content
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.