Skip to main content
Participant
July 1, 2008
Question

CF 8.0.1 Upgrade

  • July 1, 2008
  • 4 replies
  • 866 views
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?
    This topic has been closed for replies.

    4 replies

    Steve@FSU
    Participating Frequently
    August 14, 2008
    Reinstalling the Updater has fixed the issue.

    Thx for the info.

    Steve@FSU
    Participating Frequently
    August 14, 2008
    I am experiencing Issue 1. on my multiserver install. Please if anyone finds a fix for this please let me know.

    This is the error I get when I run wsconfig.exe

    Exception in thread "main" java.lang.UnsatisfiedLinkError: sun.awt.windows.WCanvasPeer.setNativeBackground
    Erase(ZZ)V
    at sun.awt.windows.WCanvasPeer.setNativeBackgroundErase(Native Method)
    at sun.awt.windows.WCanvasPeer.initialize(WCanvasPeer.java:79)
    at sun.awt.windows.WPanelPeer.initialize(WPanelPeer.java:58)
    at sun.awt.windows.WWindowPeer.initialize(WWindowPeer.java:105)
    at sun.awt.windows.WFramePeer.initialize(WFramePeer.java:108)
    at sun.awt.windows.WComponentPeer.<init>(WComponentPeer.java:602)
    at sun.awt.windows.WCanvasPeer.<init>(WCanvasPeer.java:26)
    at sun.awt.windows.WPanelPeer.<init>(WPanelPeer.java:54)
    at sun.awt.windows.WWindowPeer.<init>(WWindowPeer.java:101)
    at sun.awt.windows.WFramePeer.<init>(WFramePeer.java:92)
    at sun.awt.windows.WToolkit.createFrame(WToolkit.java:380)
    at java.awt.Frame.addNotify(Frame.java:459)
    at java.awt.Window.pack(Window.java:668)
    at jrunx.connectorinstaller.gui.ConfigFrame.addConfig(ConfigFrame.java:203)
    at jrunx.connectorinstaller.gui.ConfigFrame.getConfigList(ConfigFrame.java:216)
    at jrunx.connectorinstaller.gui.ConfigFrame.getConfigPanel(ConfigFrame.java:150)
    at jrunx.connectorinstaller.gui.ConfigFrame.<init>(ConfigFrame.java:102)
    at jrunx.connectorinstaller.gui.ConfigFrame.run(ConfigFrame.java:407)
    at jrunx.connectorinstaller.ConnectorInstaller.main(ConnectorInstaller.java:751)
    Participant
    August 14, 2008
    We solved this problem by manually stopping ALL jrun.exe processes and re-installing the updater.
    Inspiring
    August 1, 2008
    WBJP01 wrote:
    >
    > 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?
    >

    No real help, but we had absolutely no problems with the 8.0.1 update
    with our multi-server install.

    Participant
    August 1, 2008
    Did you find the answer to your upgrade problem? We are experiencing the same problem ...