After Updating to GWAVA 4.51, GWAVA is not Starting Up

I have updated GWAVA from 4.5 build 125 to 4.51 latest build. After restarting GWAVA, if I run 'rcgwavaman status'  several modules are not running.

Currently, GWAVA 4.51 is not compatible with SLES 9. We are working on a solution to resolve this.. We don't have an ETA on when/if we will have a solution yet.

It is recommended to either update to a newer version of Linux if you can, or switch over to the GWAVA Appliance (Link to what the GWAVA Appliance is). If you are not able to do either of those, you can back rev GWAVA to your previous version (before the upgrade). To do this, do the following:

1) From a server prompt, shut GWAVA down: rcgwavaman stop
2) Rename the GWAVA files back, so that you are using ones from before the update. All of the files that were updated from the previous build were renamed with a .old extension. Files are located in /opt/beginfinite/gwava/assets/bin.

a) Rename gwavaupd to gwavaupd.new, then rename gwavaupd.old to gwavaupd
b) Rename gwavaman to gwavaman.new, then rename gwavaman.old to gwavaman
c) Rename gwvsmtp to gwvsmtp.new, then rename gwvsmtp.old to gwvsmtp
d) Rename gwvgwia to gwvgwia.new, then rename gwvgwia.old to gwvgwia
e) Rename qms2 to qms2.new, then rename qms2.old to qms2
f) Rename gwvrelay to gwvrelay.new, then rename gwvrelay.old to gwvrelay
g) Rename gwavapoa to gwavapoa.new, then rename gwavapoa.old to gwavapoa
h) Rename gwava to gwava.new, then rename gwava.old to gwava
i) Rename libgwvsmod.so to libgwvsmod.so.new, then rename libgwvsmod.so.old to libgwvsmod.so
j) Rename autoblkr to autoblkr.new, then rename autoblkr.old to autoblkr
k) Rename asengine to asengine.new, then rename asengine.old to asengine

Note: You can ignore any of the .nlm files, as they are for Netware only.

3) Replace your gwavaman.db with one from before the update.

a) Rename /opt/beginfinite/gwava/config/gwavaman.db to gwavaman.db.new
b) In /opt/beginfinite/gwava/config/backup. Extract the gwavaman.db from a zip file that is from before the update. Place it in /opt/beginfinite/gwava/config.

4) Start GWAVA back up: rcgwavaman start

GWAVA should now load and run successfully, using the previous build.

This article was originally published in the GWAVA knowledgebase as article ID 1718.