Solved

FilemaKER Advanced Server 12

Posted on 2014-02-11
15
776 Views
Last Modified: 2014-04-07
I am running FileMaker Advanced Server 12.0.5 on Windows Server 2003 Sp2 (32bit). Periodically (about 3-4 times daily) my Web Publishing Engine stops which consequently does not allow my user to access the database from internet. I have to start web publishing several times daily. Any ideas?
0
Comment
Question by:sti007
  • 5
  • 4
  • 4
  • +1
15 Comments
 
LVL 24

Expert Comment

by:Will Loving
ID: 39851120
I've actually having a similar issue with one of my clients, though on Windows Server 2008. I would first check the Log Viewer in the FMS Admin Console for Publishing and Web Publishing  errors (and are you using Instant Web Publishing or Custom Web Publishing with PHP?)

The following thread may not help but it's worth checking over to see if it looks relevant: http://forums.filemaker.com/posts/c906efb534
0
 

Author Comment

by:sti007
ID: 39856125
I checked the Log Viewer under Publishing Engine Access and saw  the following error:
127.0.0.1:1444 - - "fmi/conf/config.wpc" 401 0.
0
 

Author Comment

by:sti007
ID: 39856127
And yes, I am using Instant Web Publishing.
0
 
LVL 24

Expert Comment

by:Will Loving
ID: 39856475
A tip I got from FileMaker tech support recent with respect to resolving issues like this is that you need to do an uninstall/re-install of FMS but you need to make sure you get rid of the entire FileMaker Server folder.

1. Uninstall FileMaker Server
2. Move the remaining "Data" folder from Program Files -> Filemaker -> Filemaker Server folder to the desktop and then completely Delete the entire FileMaker Server folder
3. Restart the computer
4. Re-install FileMaker Server
5. Re-upload your databases into FM Server using the Admin console
0
 
LVL 1

Expert Comment

by:grnassar
ID: 39876936
We also had a client with this problem.  They had a two-machine installation; the worker (web server) machine was the one that would have to be regularly restarted.

We called this one in to FMI, and never got a resolution.  This isn't going to be what you want to hear, but: moving to FMS13 with a fresh reinstall (and deleting the old folder, of course) solved the problem.  (Unless you are on a maintenance contract with them, in which case you won't mind hearing it because the FMS13 upgrade is free.)
0
 
LVL 1

Expert Comment

by:grnassar
ID: 39914174
apologies, posted from wrong account.  Will repost (with deleted question re-added)
0
 
LVL 6

Expert Comment

by:slinkygn
ID: 39914175
We also had a client with this problem.  They had a two-machine installation; the worker (web server) machine was the one that would have to be regularly restarted.

We called this one in to FMI, and never got a resolution.  This isn't going to be what you want to hear, but: moving to FMS13 with a fresh reinstall (and deleting the old folder, of course) solved the problem.  (Unless you are on a maintenance contract with them, in which case you won't mind hearing it because the FMS13 upgrade is free.)

By any chance, are you using CWP as well?  Or only IWP?  (There was a known issue with early versions of FMS12 where using both would sporadically crash the server; I can give more info if needed.)
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 

Accepted Solution

by:
sti007 earned 0 total points
ID: 39972731
I have just found a work around for this problem. I think IWP is just not cleaning up after itself after several SQL queries and data entries. Stopping and restarting once a week the FileMaker Server under services seems to resolve my constant  crashes.
Thanks everyone.
0
 

Author Closing Comment

by:sti007
ID: 39982552
Because nobody else has come up with any solution to permanently fix the issue. SO I posted a work around that I used to temporarily avoid the crashes.
Thank you.
0
 
LVL 24

Expert Comment

by:Will Loving
ID: 39983091
Thanks. This has actually come up with a client of mine so  it will be interesting to see if this resolves prevents the issue.
0
 
LVL 6

Expert Comment

by:slinkygn
ID: 39983175
If you're crashing less than once a week, that should work :) since after all a crash and restart is stopping and starting the service, just on a far less controlled schedule.

As I mentioned, it's a common issue with 12, and is tricky because it can be caused by a numbet of issues.  If it occurs when using both IWP and CWP, and the end user moved to 12 early in the release cycle and is using a volume license key for Server, it is because of an authentication bug caused by a malformed license key and can be resolved by calling FM and asking them to generate a new one.  Outside of this, the problem seems to be particular to IIS 6 on Server 2003 and FM 12 as far as we've been able to tell; we had some luck rolling back versions of Java on that server as far as problem frequency goes but eventually settled on a scheduled task that would periodically restart the Web service. Moving to FM 13 made the problem go away entirely, in a way that no fresh reinstall of 12 ever did.
0
 
LVL 24

Expert Comment

by:Will Loving
ID: 39983216
I've been working for an extended period with a senior level FM Tech advisor to resolve WPE crashes in FM Server 12 while running CWP only. We have tried many many things including new license key, complete and clean re-install of FMS, and a complete re-install of the OS and FMS. Nothing worked and the I finally downgraded them back to the FM 11 version doing a manual re-import of about 80 tables. We're moving towards an FM 13 and WebDirect solution to replace the PHP.
0
 
LVL 6

Expert Comment

by:slinkygn
ID: 39983796
That sounds incredibly frustrating.  We were having similar problems -- though I think I can rule out PHP as a problem point; the web application that we were using this for was just pulling the raw XML from FMSA and then parsing it itself instead of going through the PHP engine (it was an ASP solution, and porting to a civilized back-end language wouldn't have been cost-benefit appropriate).  So whatever the problem was, it was independent of PHP.  If I'm remembering correctly, we tracked it back to a Java crash bug within the Jakarta/Tomcat component itself, but I don't recall any detail past that.  Our FMI tech was also stymied by the problem.

Bright side, though -- it's possible you guys may not have to replace the PHP if you don't need to.  If you discover more about the FM12 problem, I'd love to hear it, if only to get some resolution on what is seemingly quite the mystery.

Was your web worker component on Windows Server 2003 as well, or were you using 2008?
0
 
LVL 24

Expert Comment

by:Will Loving
ID: 39983886
It was a one-machine setup using 2008 and PHP was definitely related to the crash. As long as the website was quiet there were no crashes, but as soon as we started hitting the site, it would crash within a short time, but not at any identifiable function or place in the PHP code.
0
 
LVL 6

Expert Comment

by:slinkygn
ID: 39983916
Ours was definitely only when used as well -- but are you sure it might not have been with the WPE itself when under load, instead of the PHP on top of it?
I suppose that could be tested: make some PHP pages that don't hit the DB and load-test the PHP, then make some HTML pages that use JS to pull XML from FM and load-test those, see if one of those two cases don't give you failures -- I'm betting you'll still get crashes from that second case, meaning the problem isn't on the PHP side but with the WPE (which is the Tomcat plugin part of Web Publishing, meaning it'd be the same thing we were seeing).
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Pop up windows can be a useful feature of any Filemaker database.  Though best used sparingly, they can be employed in a multitude of different ways, for example;  as a splash screen at login, during scripted processes to control user input, as pick…
Problem: You have a hosted FileMaker database and users are tired of having to use Open Remote or Open Recent to access the database. They say, "can't you just give us something to double-click on rather than have to go through those dialogs?" An…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
Excel styles will make formatting consistent and let you apply and change formatting faster. In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. You'll also learn how to use your custo…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now