When one of the files in the tomcat "work" directory gets locked by another process (for example by not fully stopped tomcat instance), Configurator fails to proceed with copying webapp contexts files. This may lead to issues with Tomcat without any indication of the problem in Configurator.
Admin DB connection file./u01/serena/collage/sql/config/adminoracle.xml the Tomcat log gives: # An unexpected error has been detected by HotSpot Virtual Machine:
The following errors may occur if SBM is started while the SBM database is not accessible. If you start SBM while the SBM database is not running or is not accessible but later make it accessible the normal user interface will be fine because IIS is able to recover gracefully. Tomcat on the other hand isn't able to recover from this and you will consequently see the following issues until the Tomcat service is restarted while the database is available.
The error in the logs is not fatal, as it merely indicates that /merantfs could not be loaded (which is okay, since you opted to not install the File Server), but to avoid the error you can rename the file: vm/common/ tomcat /conf/PVCS/localhost/merantfs.xml to:
DA Server will not start. The following error can be found in the DA or Tomcat logs: 2018-02-16 14:10:24,331 - Failed to start Serena DA java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:459)
