I would like to know to! I have the same error on one of my servers (acctually errorcode 2505). It is a new Win2k3 Server freshly installed running nothing but FileMaker server advanced 9.0.3 as a one machine configuration. FileMaker server was installed using the v3_full installer so no patching has been needed.
Also all windows OS updates was applied before installing FMS. I´m using the JavaRE installed by the FileMaker server installer.
It failed instantly after configuration. I have tried reinstalling but with the same results. I have been reading about this on technet to but there is few threads about this for windows servers. Since the same error seem to occur on MacOS I´m guessing TomCat or Java problems?
Any pointers how do deal with this would be great! I´ll by you cakes!
when I asked FM direct this is what I got back (VERY helpful...)
Thank you for contacting Customer Assistance. Individual Technical Support is provided via the telephone only. With your Support Access Code* or a valid credit card, FileMaker Technical Support representatives can help you with installation, plus one free launch and basic troubleshooting case on FileMaker features. If, when speaking with a Support Engineer, the issue is determined to be an installation issue, or software failure, your Support Access Code will not be debited, and you may use it again in the future.
Contact Technical Support, Monday - Friday, 7 a.m. - 5 p.m. US Pacific Time (holidays excluded) by calling 800-325-2747 and selecting option #4 from the options menu.
Alternatively, you may be able to find an answer to your questions by visiting our Forums at http://www.filemaker.com/support/forums.html, or by searching the FileMaker Knowledge Base at http://www.filemaker.com/kb.
Customer Assistance Specialist
ProductPoorlySupported and KalleSamuelsson:
Thank you for your posts.
First, in all fairness to our Customer Assistance department, they are there to handle all customer inquiries. If you have a technical question in nature, they do give you the options how to receive support.
This error has been a bit elusive to us. It works fine on some machines, and then it fails. This has happened on both Mac and Windows machines, so it is not platform specific.
As I look through old notes, I did find one user have a user created file in the WebPublishingEngine.app, and that prevented the installation of the WPE.
Another user had it working on Windows 2000, but couldn't get it to work on XP, 2003 & Vista. No solution was provided. Please don't take it that Windows 2000 will work for you. We have it running on Windows XP, 2003 and Vista without problems, and from the sound of it, your other machines also work.
Please... if you do find the cause of this, please let us know!
My criticism was that of unpublished error codes, and your department's unwillingness to provide a definition, or even a location of these error codes without paying. I stand by my criticism, Kalle, as by reading the above reply it appears that point is still lost on FM, and thus why I am forced to reach out to other users in this forum for help.
I confirm this bug. I too have experienced this bug and its error message during the deployment process (in the most recent case, on in an Intel C2D w/ Mac OS 10.5.4). On one occassion my workaround was to wipe out FMSA and start over. On another, I believe I may have somehow ignored the error and restarted the machine.
It does not go away - even with multiple reboots.
good Lord! All we want is someone from FM to at least DEFINE the error codes for their server product! Why is that too much to ask?
I'm getting this error (and others) as well. I have tried just about everything but cannot get this working in a two machine configuration.
I'm going to have to start from scratch again this weekend.
Anyone aware of a successful two-machine install for getting FM to the web?
I'm still researching this problem, but no additional information is available at this time.
I am DEFINITELY trying to obtain a list of error codes for the Web Publishing Engine.
That is all we ever wanted! THANK YOU!:smileyhappy:
Thank you for your patience on this. Here is the latest information I have from our Developers...
This error (-150) usually occurs when the deployment is unable to restart either the WPC (Web Publishing Core) or CWPE (Custom Web Publishing Engine) after configuriing it.
If this is a multi-machine deployment, the first thing to do is make sure that the Admin Helper on the worker is running - restarting the machine or the service is the easiest way, then make sure that all the processes are running. Then, redeploy from the master.
If this is a single machine, just re-deploy. If it still fails, try to start the Web Publishing Core from the command line (e.g. "/Library/FileMaker Server/Web Publishing/publishing-engine/wpc/FM Web Publishing.app/Contents/MacOS/FM Web Publishing" on OSX). Taking a look at the logs can also help.
Please let me know if this helps any of you.
We have successfully deployed FileMaker Server 9 Advanced in single- and multi-machine configuration several times, on a variety of platforms. But even after -150 WPE(wpe1) deployment/configuration errors are overcome, and a deployment is finally achieved, our single- and multi-machine Filemaker Servers still have not performed as expected, because the Custom Web Publishing Engine (CWPE) is observed to hang and crash when things get busy with XSLT, and, on an infrequent basis, crash FATALLY (see my comments below).
Yes, we are having more than a few well functioning two machine setups. BUT we are also facing problems like those described here - and we are being contacted by other Danish IT-people trying to set up FileMaker servers ...
We are not happy to find that FileMaker support know as little about how to solve it as the users. We still have to see if it goes for FileMaker 10 as well.
It is crucial to have this solved since all important installations are two machine based.
Our only clue is that we so far has only had problems with two machine setups across firewalls. And, yes, we are sure that all access through the firewals are as described by FileMaker.