We’re having problems with the Server Admin Console and WPE, described below in a memo from our server people. This server hosts a dozen databases that are in use 24-hours a day, so we’d really like to know what we’re doing before we shut it down or do other maintenance steps to end the flaky behavior of the Admin Console and the hourly WPE error messages we’ve been getting.

There was a server incident that apparently started the WPE warning and error messages: a backup script malfunctioned and filled the hard drive with extra copies of various files, leading to the Warning 86 disk full error from FileMaker Server. After we cleaned up the drive and restarted the databases, we began getting the WPE Component error messages regularly.

Thanks for any advice!

FMS9 admin console, FMS Overview display is inconsistent. The Web publishing engine radio button is gray, not green, but the Web Publishing icon in upper left-hand corner shows Web Publishing Engine "On" (dimmed).

Have restarted Database Server and Web Publishing using icons in upper left-hand corner. No change in FMS Overview display. But did notice Web Publishing icon change from "On" to "Off" several minutes after restarting Web Publishing Engine. Hosted data bases appear to be unaffected. Data base back ups and consistency checks are OK.

Am receiving two FMS warning messages every hour:

FMS ERROR wpe1

Some problems were detected in the WPE COMPONENT: COMPONENT IS NOT RESPONDING.

FMS WARNING wpe1

Some problems were detected in the WPE COMPONENT: POTENTIAL PROBLEM.

Running FMSA9.0.3.326, with IWP on, XML off, XSLT off, ODBC/JDBC on.

FM Web Publishing 9.0v2.

OSX10.5.8 G5 (3.1) Power PC Dual 2.3GHz, 1 GB memory

Java 1.5.0_24

Running FMSA9.0.3.326, with IWP on, XML off, XSLT off, ODBC/JDBC on.

FM Web Publishing 9.0v2.

OSX10.5.8 G5 (3.1) Power PC Dual 2.3GHz, 1 GB memory

Java 1.5.0_24

Triple ouch on the RAM!! That's nowhere near enough.

Steven

Hey Harvey,

We are experiencing a similar issue, although the warnings are being generated at longer intervals than yours ( 2 in a week) and kills the WPE. Coincidentally it did start happening after we had a full disk issue too.

Did you get to the bottom of your issue?

Thanks,

Catherine

Steven was suggesting that the problem is most likely insufficient RAM.