Jump to content

Search the Community

Showing results for tags 'wpe'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type

Community Forums

  • The New FileMaker Platform
  • Community Resources
    • Community Articles, Tips, & Techniques
    • FileMaker Marketplace Discussions
  • FileMaker Platform
    • FileMaker Interface Features
    • FileMaker Schema & Logical Functions
    • FileMaker Go for iPad and iPhone
    • FileMaker and the Internet
    • FileMaker Pro Advanced 17
    • Legacy FileMaker Platform Discussions
  • FileMaker Server Administration
    • FileMaker Server 17
    • FileMaker Server 16
    • FileMaker Cloud
    • FileMaker Custom SSL Certificates
    • oAuth and External Server Authentication
  • Brain Food
    • Security Concepts
    • The Left Brain
    • Upgrading & Migration
    • Data Analysis
    • Development Standards
    • The Separation Model
    • Relational Database Theory
    • Damaged / Corrupt File Problems
    • Bar Codes (Printer, Scanners, Software)
    • Hardware & Networking
    • OS Level Database Automation
    • Product Ideas
  • FileMaker Security Management
  • FMForums Affiliates & Sponsors
  • FileMaker Classifieds
  • FM Forums Operations
  • FileMaker Friday Night Chat's Topics


There are no results to display.

There are no results to display.


  • White Papers
  • Infographics
  • Samples
  • Solutions
  • FMGo
  • Plug-Ins
  • Tutorials

Product Groups

  • Workplace Innovation Platform
  • Site Advertising
  • Development & Hosting

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start







Website URL




OS Version

Found 5 results

  1. I successfully deployed SuperContainer (SC) via the Web Publishing Engine (WPE) of FileMaker Server 11 for years, on a Mac mini (2010) running OS 10.6.8 (Snow Leopard), with no problems. But I ran into the following problem with Mavericks and SC: I upgraded to more modern versions of OS X and FMS by doing a completely clean installation: Formatted the Mac mini's drive; Did a clean installation of OS X 10.9.1 (Mavericks); and Installed FileMaker Server 12v6 without problems. Next, I downloaded the latest SuperContainer from 360Works (v2.896). When I double-clicked the "Mac Installer.app" (also known as "SCInstaller") to deploy SC with FMS, as I did before with FMS11, I was surprised to see this alert pop up: "'Mac installer' is damaged and can't be opened. You should move it to the Trash." Mac Installer is damaged.tiff I tried downloading a fresh copy, using Safari and Firefox; same error. I’d never seen this message before when installing any software, and I found no reports of it in this forum or in TechNet. The icon displayed in the alert window indicated that it was originating from Mac OS Gatekeeper. So the solution I tried was to change the "Security & Privacy" System Preference of Mavericks, under the "General" tab, to "Allow apps downloaded from Anywhere", rather than the more restrictive "Mac App Store and identified developers" option. (Perhaps another option would have been just to control-click the app icon and then select “Open”, to exempt the app from Gatekeeper; I didn't test that.) Apple’s support article on Gatekeeper mentions this “Damaged” app warning message is an indication that “the app has been altered by something other than the developer.” I doubt that any “true damage” is present in the Mac Installer for SC. I think the message appeared because AppleScript scripts get modified after they’re signed. An Apple support article on Mavericks security states: “Some apps and tools, such as AppleScript applications and some legacy tools, modify themselves after signing. These types of apps cannot be opened unless the Gatekeeper setting in Security & Privacy preferences is set to Anywhere” I had only tried the SC Installer on Mavericks, but I suppose the same error might have occurred on Mountain Lion or Lion, since Gatekeeper was introduced with Lion. It appears, for now, that we may need to temporarily disable Gatekeeper (by choosing the "Anywhere" option) in order for SC's Mac Installer to work. David M. Hollander, MD Combined Fields Consulting
  2. Our FMS 15 is running on a dedicated server at a hosting provider (running on Windows 2008 R2). We have two databases - a small 30 MB "UI" front end for accessing via FM Pro clients and a larger 7 GB database containing all the data. The only access to our databases are either (1) via FM Pro clients or (2) via WPE calls made from another non-FM server to retrieve data and add/update records. We are having a problem keeping the WPE up during times when staff are also doing other tasks on their computers via their FM Pro clients - in particular, when they are uploading spreadsheets of data which trigger scripts to process the data. Symptoms are the WPE just turns itself off in the admin console. Or even if it's on the WPE goes unresponsive and needs to be toggled off an on again. We are working with FM tech support now to see why, because they admit that running scripts like this should not cause the WPE to stop, and they are pouring through logs for us now. Our server meets all their requirements and has plenty of available RAM, etc. But it's like FMS can't walk and chew gum at the same time. When the staff are not updating things with spreadsheets, the WPE, if it times out at all, it might be 1 timeout out of 1,000 WPE calls. Overnight last night the WPE ran fine for about 12 hours straight. But when the staff came in and uploaded a few spreadsheets the WPE came down again. It came down 4 times today. So... I'm wondering if MirrorSync can help with this problem. Looking at the price list, it seems MirrorSync has a free and $400 solution that I think, from what I read, we could use in the following manner (that's what I want to confirm and why I'm posting today): We continue to run just one FileMaker server. But the staff don't connect to the remote server with their FM clients to the server for the update work they are doing. Instead, each staff member who needs to do updates of the time-consuming spreadsheets opens up a local copy of the database and does their work on their own Mac or Windows. No server is required at this point, and the scripts run offline on their computer. Then when done, MirrorSync will sync their changes into the database on the server. Staff can still connect to the FileMaker server if needed. But would just avoid doing the problematic updates of spreadsheets directly on the server. They would do them locally and then sync. Does this kind of work flow sound correct in terms of what MirrorSync does? If so, how do the local FM Pro clients also stay synced with changes being made in the database via the WPE during this time? The WPE calls might add or update records in different layouts. Is there some process where a staff member would first sync with the server to get the updated data, then do their own data updates and reports offline, and then sync again with the server to send the data back online? Or is the work flow different from that? Thanks. Doug
  3. Since going from version 2 to 3 of MirrorSync last year we have constantly had MirrorSync crashing the Web Publishing Engine. Sometimes it says "Error from server: FileMaker XML WPE Web Publishing Engine is not running at <the hosted IP>. Ensure that the WPE is working correctly, and then try this operation again." But usually it is an Error 10 error. "Error 10 while connecting to http://<the hosted IP>/sync?ping=1&config..." Early on we made the documented suggested changes for this error, to the connectionTimeout Property in the IIS Manager application. With no noticeable effect. Most of the time MirrorSync works as expected and does a great job and then clients can't sync and all hell breaks loose. Do you have any other suggestions for what might be causing this issue?
  4. According to the following KB article, FMS12 isn't compatible with 10.9: http://help.filemaker.com/app/answers/detail/a_id/11930 However, it is possible to get it to work with a few adjustments. The database server works just fine, but WPE does not. Here is how to get WPE working (based on http://fmforums.com/forum/topic/89802-109-mavericks/#6 with a few corrections) Open up Terminal cd /Library/Server/Web/Config/apache2/ Add the following lines to the end of the httpd_server_app.conf file: Note: they may already be there, commented out, after installing the FileMaker Server <IfDefine WEBSERVICE_ON> Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf' Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fm-server-status.conf' LoadModule proxy_ajp_module libexec/apache2/mod_proxy_ajp.so Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf' </IfDefine> Some of the modules may be commented out with #FMI_Configuration_V1 which you will need to uncomment. Restart your Web server Restart the FileMaker Server Restart the Web Publishing Engine Go to http://<your_server_url>:16000 and perform FileMaker Server 12 Technology Tests in the Troubleshooting section. Tested 10.9, 10.9.1, FMS 12.0v4. Not tested with 12.0v5, but it should work as well.
  5. I am finding on mature systems with lots of found records that the WPE gets bogged down when FMPS passes the found set to it. This can even cause PHP to timeout and throw an error. Plus no user wants to wait that long. Normall I would deal with this with paging. Pagination still has the full found set passing from FMPS to the WPE, then PHP sends just the current pages records to the browser. This is better but still boggs the Server down. Best WPE efficiency comes from transferring small amounts of data. But some times there be something else that slower performance down ... C
  • Create New...

Important Information

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