Troubleshooting › CA Catalyst Troubleshooting › Registry Errors

Registry Errors

Symptom:

You experience errors with Registry functionality, such as the following issues:

• Problems connecting to the SA Store database
• Cannot access Registry
• Registry content missing
• The sor.application program within the Registry is not starting

Solution:

Try the following solutions to fix Registry errors:

• Verify that the SA Store database credentials in the SOI_HOME\ws02registry\repository\conf\registry.xml file are correct.
• Access problems can be caused by invalid credentials or an unencrypted password that is stored in the Registry. If you cannot access the Registry, check the credentials in the ssaserver.xml and sorapp.xml files at SOI_HOME\tomcat\registry\topology\physical\node0\sor.
• If Registry content is missing, check the database credentials in the sorapp.xml and ssaserver.xml file.
• Check the SOI_HOME\tomcat\registry\topology\logical\tenant0\usmschema folder and verify that the following files exist:
  • addressing.xsd
  • sml.xsd
  • usm-core-200907.xsd
  • usm-query.xml
  • usm-elemconstraints.xml
  • usm-extensions-201001.xsd
  • usm-infradefaults.xml
  • usm-metadata-200907.xsd
  • usm-metrics-200907.xsd
  • usm-openenums.xml

  If these files do not exist or are corrupted, the USM schema did not install correctly.

• If sor.application does not start, check the topology\physical\node0\sorappbootstrap.xml file and verify that it correctly points to the sorapp.xml file. Also, verify that sor.application.war is deployed.