Question
CF 8.0.1 Upgrade
I have two issues:
1.) The 8.0.1.195765 install breaks the JRun Launcher and Web Server Configuration software for my Enterprise 8.0.0.176276 install.
We have a server running the multi-server environment. When I install 8.0.1, JRun Launcher returns error:
"Exception in thread "Main" java.lang.UnsatisfiedLinkError: sun.awt.windows.WCanvasPeer.setNativeBackgroundErase(ZZ)V
The Web Server Configuration software also returns a error like this, but the batch window closes before I can read what it says.
2.) The second issue is with the Administrator logs. The archive function is not working correctly in MX8. In MX7 and earlier versions, the archive button copies the existing log file and adds a number to the file extension. The behavior in 8.0.0.176276 creates a fresh 'active' log record with no archive log record. When I apply the 8.0.1 upgrade, the process works better but not completely correct. With 8.0.1, it creates the first archive record (1), but the numbering of the subsequent archive records is not consistent or it creates (2) and deletes (1), or some other crazy combinations.
The reason for my 8.0.1 update attempt is to correct the archive log file issue. The upgrade works fine for single-server install, but breaks the multi-server install.
Any suggestions?
1.) The 8.0.1.195765 install breaks the JRun Launcher and Web Server Configuration software for my Enterprise 8.0.0.176276 install.
We have a server running the multi-server environment. When I install 8.0.1, JRun Launcher returns error:
"Exception in thread "Main" java.lang.UnsatisfiedLinkError: sun.awt.windows.WCanvasPeer.setNativeBackgroundErase(ZZ)V
The Web Server Configuration software also returns a error like this, but the batch window closes before I can read what it says.
2.) The second issue is with the Administrator logs. The archive function is not working correctly in MX8. In MX7 and earlier versions, the archive button copies the existing log file and adds a number to the file extension. The behavior in 8.0.0.176276 creates a fresh 'active' log record with no archive log record. When I apply the 8.0.1 upgrade, the process works better but not completely correct. With 8.0.1, it creates the first archive record (1), but the numbering of the subsequent archive records is not consistent or it creates (2) and deletes (1), or some other crazy combinations.
The reason for my 8.0.1 update attempt is to correct the archive log file issue. The upgrade works fine for single-server install, but breaks the multi-server install.
Any suggestions?
