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.

Two Servers 5.5 & 8 Not Playing Nicely

Featured Replies

  • Newbies

I have a windows 2003 Enterprise Server running FM server 5.5 successfully. We are trying to set up our new FM8 files and have a second server in the domain also running 2003 Enterprise Server with FM server 8.

Server #1 with FM 5.5 - works perfectly

Server #2 with FM 8 - services are started, and databases are sort of accessible in that they can be seen and opened - BUT - upon opening the served files an error comes up [pardon the paraphrasing]:

Unable to host filemaker file as the filemaker service is aleady in use.

The file functions except the annoying error message AND all container fields "loose" their contents - like all logos were not mapped. FYI all images are Inserted, not referenced.

If I shut off the FM 5.5 service on server #1 and restart the FM 8 service on server #2 i do not get the error message and all the container contents magically show up.

If I then try to start FM 5.5 on server #1, i get a error in the event log and the files are not served.

Any suggestions would be helpful as we want to move to the FM8 databases.

I believe this was a known issue when Server 7 was released, but I am not 100% sure about that. I do know that if you are coming from outside the subnet through a router that the Port 5003 forwarding issue can complicate matters. Maybe move one server or the other to a different subnet.

BTW, 2003 Enterprise is not a certified OS for Filemaker Server 8.

Steven

There must be some routing issues on the network or configured on the machine. Try to find out why the machine thinks port 5003 is already taken when you start FMS8. That's the key here.

Create an account or sign in to comment

Important Information

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

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.