Jump to content
View in the app

A better way to browse. Learn more.
FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FileMaker 4.0 Web Interface crash

MazdaBoi
in Custom Web Publishing

Featured Replies

  • Newbies

Hello all.

I'm a novice with FileMaker Pro... I am a MySQL nut, personally... But

I'm having some problems with a database machine at my workplace. It's

FileMaker Pro 4.0 running on MacOS.

For the past week or so, the web interface to the database has been

dying for no apparent reason. The GUI on the Mac itself continues to work

just fine...

To revive the web interface, I have to shut FM down, and restart it.

The web interface will be fine for about 15 minutes, then it will die

again....

Has anyone ever seen this behavior? If so, do you happen to know any

fixes for the problem?

Thank you in advance for any advise

Brad

It can be anything on that machine. Possibly the TCP/IP settings or some problem.

What is the meaning of "the web interface to the database has been dying“?

  • Author
  • Newbies

I think it's called the Web Companion? FileMaker's GUI on the mac continues to work perfect, as if nothing happened.

The Web Companion ceases to accept connections at all... The port isn't even open on the machine....

Both 'Code Red' and 'Nimda' can disable Web Companion on Mac. On our server it can happen in about 20 minutes after restarting the computer. These worms may be able to do this by not allowing the TCP/IP connection to close and in the case of 'Code Red' it may cause a buffer overflow. A single threaded sever such as Web Companion in FMP Unlimited 5.0 can be disabled if the connection is not allowed to close. You can read more about this at http://www.sustainablesoftworks.com. I have ended the problem for our server by using their IPNet Sentry. You will need to configure the triggers to block all types of 'Nimda' packets. I believe there are about six. Also it is important to set the trigger to close the connection. If you do not then I have found the connection does not close and web companion stops serving. Go to http://www.sustainablesoftworks.com/site/net_sentry/command_syntax_document.htm to see an example. It is about half way down the page.

  • Author
  • Newbies

Interesting... I turned up the logging to see what's going on... Hopefully I'll have an answer soon...

Create an account or sign in to comment

https://fmforums.com/topic/1076-filemaker-40-web-interface-crash/
Go to topic listing

Important Information

By using this site, you agree to our Terms of Use.

I accept

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.