Designer
Try to install the new version of Designer again to a different location, preferably outside the Program Files folder, using a new workspace. If it doesn’t work, contact support@cloverdx.com (the more details you provide in the issue description, the quicker the solution will be; for more details please see the following article: What do I need to supply to Support in order to speed up the response?).
Server
If the Server upgrade fails, firstly, make sure that your user account has enough permissions to the Server database and the file system and try to perform one of the following (assuming that you have the DB backup and config.xml available from the last working version):
- Perform the upgrade process again:
- Stop your application server.
- Reestablish the database again by importing DB backup (dump.sql) to your Server DB.
- Remove WAR files from application server folders (in Tomcat: <TOMCAT_HOME>/webapps/clover.war and <TOMCAT_HOME>/webapps/profiler.war) and also delete folders created as a part of deployment (directories <TOMCAT_HOME>/webapps/clover and <TOMCAT_HOME>/webapps/profiler).
- Download the correct version of clover.war and profiler.war again from the authenticated section in our Customer portal.
- Deploy the CloverDX Server files again (in Tomcat: copy the WAR files to “webapps” directory) and Run application server, in other application servers follow the instructions in the documentation).
- Repeat the upgrade process with a new database:
- Stop your application server.
- Create a brand new DB and import the dump.sql into the new database (e.g. CloverServer2), make sure that the application server uses the new DB (in the properties file).
- Then perform steps 3 to 5 from above again.
- If it still won’t get your Server back online, considering the situation, we would suggest trying a brand new Server DB without importing the sql-dump DB data. Please be aware that you would lose run records and transaction history for now, but once the Server is back up, you can import config.xml file which stores the configuration of your original Server (user accounts, schedulers, event listeners):
- Stop your application server
- Create new DB, leave it empty
- Then perform steps 3 to 5 again
- Import config.xml in the Server GUI. This will get the Server back online, running with the original configuration.
- If none of this helps, in order to revert your production CloverDX server to the original version:
- Stop your application server
- Reestablish the database again by importing DB backup (dump.sql) to your Server DB.
- Remove WAR files from application server folders (in Tomcat: <TOMCAT_HOME>/webapps/clover.war and <TOMCAT_HOME>/webapps/profiler.war) and also delete folders created as a part of deployment (directories <TOMCAT_HOME>/webapps/clover and <TOMCAT_HOME>/webapps/profiler).
- Deploy the original WAR files to the CloverDX Server again (in Tomcat: copy the original WAR files to “webapps” directory and Run Tomcat, in other application servers follow the instructions in the documentation).
In either case, please contact support@cloverdx.com and attach the application server related log file and CloverDX Server all.log file (in Tomcat located in <TOMCAT_HOME>/logs/Catalina.log and <TOMCAT_HOME>/temp/cloverlogs/all.log).
Comments 0