Quantcast
Channel: FileMaker Forum > Report an issue
Viewing all articles
Browse latest Browse all 3510

IWP Unstable (again) in 12.0v6 Error 701 (2 Comments)

$
0
0

Issue report by J HUme

Product

FileMaker Server

Version

12.0v6

Operating system version

OSX 10.9 Server

Description of the issue

WP 701 error caused by portals with containers issue:

I previously had this issue with Filemaker Server 12.0v5, so I trolled the forums and eventually found this hot fix: http://help.filemaker.com/app/answers/detail/a_id/12617/kw/instant%20web%20publishing%20crashes/session/L3RpbWUvMTM5MDg0MDYwOS9zaWQvcDlrOWNyTGw%3D
Ok. I understand hot fixes are a necessary evil in the development world, and after several hours of pain, I got the hot fix applied, and everything ran ok.
I just migrated to a new server running Maverick and updated to 12.0v6, and the error has returned. I find it utterly unthinkable that a development organization the size and scope of Filemaker would fail to incorporate a previous hot fix into the next release (12.6), so I am therefore concerned that the error has been reintroduced. I am concerned abut trying to apply this hot fix again because I absolutely cannot believe that FileMaker would have failed to include it in the 12.0v6 release, and I am therefore concerned that I would break something or make matters worse.

Steps to reproduce the problem

Try keeping Filemaker IWP running for more than a couple of hours in a row if you use forms with portals with containers on any version post 12.0v3.

Expected result

A stable product

Actual result

embarrassment and headaches

Exact text of any error message(s) that appear

email notifications:

Email 2:
FileMaker Server 12.0.6.600 on mac340102 reported the following event:

Mon Jan 27 10:18:21 CST 2014 FMS WARNING wpe1

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

Email 1:
FileMaker Server 12.0.6.600 on mac340102 reported the following event:

2014-01-27 10:16:48.728 -0600 Error 701 mac340102 Instant Web Publishing process has terminated abnormally.

Workaround

constantly monitor the server console and try to restart web services before the phone line lights up.

Viewing all articles
Browse latest Browse all 3510

Trending Articles