We have reset all users FileMaker related profile fields. Please take the opportunity to update your information,  this will provide background to members whom read your posts. Click here.

Jump to content

Gnurps

Members
  • Content count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Gnurps

  • Rank
    novice

Profile Information

  • Gender
    Not Telling

Contact Methods

  • AIM
    gnurpsyrag
  1. On two Filemaker Server machines I manage, I cannot get FTPeek to activate. After checking the checkbox, a grey message appears appears stating that the plugin was enabled, but the checkbox is unchecked. I have checked the permissions of the plugins. Both owned by fmserver and group fmsadmin. I have restarted the machines. I have tried Wim's suggestion of installing with server-side script. Both have Java 1.6 installed. Both have the BaseElements plugin installed and successfully enabled. Both are running FMS 14.04. One is a Mac mini running Yosemite, with Core 2 Duo processor and 8gb. Other is a Mac mini running El Capitan with Core 2 Duo and 4gb.
  2. Plugin crashing Filemaker Pro

    Ryan, That worked. Thanks. Maybe add that solution to the documentation? Gary
  3. The plugin crashes Filemaker Pro Advanced, v15.0.3, when I execute FTPeek_DownloadFile(). The file actually does download. Next step is the error script and that never reports. Filemaker just beach-balls. Running Mac El Cap 10.11.6.; 16gb RAM. Not yet on server; just testing in development. Gary Gnurps
  4. I find this aspect of FTPeek unsatisfactory; a mistake by 360. The recursive nature of FTPeek_ScanLocalDirectory() needs a toggle. I am using the plugin to adapt a system which moves files that were uploaded from a directory into a subdirectory, "Archive". I want to start with a listing of the files NOT in Archive, loop through them and upload them, then move them into Archive. To use FTPeek for this feature, I would have to restructure the file system, moving Archive to a different location. Looks like instead I'll use the free BaseElements plugin: BE_ListFilesInFolder ( $moveSource; BE_FileType_File, False). The param "BE_FileType_File shows only files of the current folder. Its prototype: BE_ListFilesInFolder ( path {; type ; includeSubdirectories ; useFullPath } ). The includeSubdirectories param defaults to false, as should FTPeek's function. See: https://baseelementsplugin.zendesk.com/hc/en-us/articles/204700868-BE-ListFilesInFolder
  5. I have a portal where tabbing from the last field on a row takes me out of the portal to a field elsewhere, rather than going to the next portal row. What is causing this behavior? (I feel like I'm missing something obvious.) Actually, there is only only one field on the portal rows that allows entry and is in the tab order. The idea is to tab from portal row to portal row, staying in this field. If I allow entry into another field on the portal row and put it in the tab order, this does not change the behavior. The field is in the layout's tab order; not the last object in the tab order. The portal is based on relationship that allows creation of new records. The portal is not sorted or filtered. No script triggers; though, when I apply a trigger -- onObjectExit perform script Go To Portal Row [Next] -- that makes no difference. Tabbing out of the field runs the script, then the focus goes to a field outside the portal.
  6. WPE crashing despite fresh installs

    When the problem recurred today, we used the command line to try some fixes. First we ran, as Wim suggested, the fmsadmin restart adminserver. That of course restarted that process. The web publishing engine was still shown as off. Then, on the worker machine, we did fmsadmin restart wpe. The machine responded "Error: 10006 (Service already running)". So we tried fmsadmin stop wpe. That changed the server behavior somewhat. Pages started loading fast. If the page had no calls to Filemaker, it loaded correctly. In pages that did call Filemaker, our error checking captured "Communications terror: (22) The requested URL returned error: 503 Service Unavailable." Makes sense. But then we entered fmsadmin start wpe and got the same error 10006 (service already running). And, in the console on the master machine, the WPE switch remained gray, off. Finally, we restarted the worker machine and the WPE resumed running correctly. So we are still rather mystified as to what is going on. We have carefully examined the logs and cannot see a pattern that would link a PHP page to the problem, nor a user, nor a file. Will keep looking...
  7. Our Web Publishing Engine keeps crashing. We have a two-machine setup, both running on Mac El Cap, 10.11.6. Yesterday we did fresh downloads of Server 15.02 to both machines. We did the clean uninstall and reinstall procedure on both machines, as called for by FM KB article 15550. Filemaker tech support says that pretty much rules out Filemaker Server as the culprit. Today, the problem is actually worse. The WPE crashed three times this afternoon. Symptoms: We see no problem with Pro access to Filemaker. We see no problem with WebDirect. Several people within the office use that method of connection and it continues to work while CWP goes down. Maybe this means the WPE is not really crashed? In Activity Monitor, we do not see spikes in CPU or memory usage. The WPE log shows nothing unusual. In Filemaker Server console, we do see the WPE slider turned off, not showing green. We cannot slide it back to the on position. To fix that, we restart the worker machine. We are considering three possibilities: Software conflict... But not much else is running on these machines and they had a clean install of newest El Cap this past summer. They do have CrashPlan, which never interfered before. We will try quitting it. We have Dropbox running on the master machine and have turned it off. Hardware problem: We will try running for a different machine, or changing to a one-machine deployment. PHP web pages causing an issue? There have indeed been some significant PHP page/script changes in recent months. But the web site, an e-commerce store, appears to run fine until the crash, and we see no CPU or memory spikes in Activity Monitor, and Filemaker Server serves to Pro and WebDirect do not slow down, and the logs do not show problem with any page. The only errors we see in the log are 401's, from users or scripts performing searches that find no records. Regarding the possibility that a PHP page is the problem, I would like to look at the Apache logs. Where are they? In Console, they should show up under /var/logs/Apache 2. But that is empty on the worker machine, non-existent on the master. Filemaker Server takes over the Apache service, but where does it put the Apache logs? Anything besides the FM Console log viewer? I'll report back if we find that one of the machines has a hardware problem, or software conflict. Can anyone consider think of another possibility, or diagnosis approach?
  8. FileMaker Pro 15 Improvements??!!!

    At a FM15 demo at an Apple store in Denver, the FM engineer told us that portals now have a separate thread. So if you navigate to a record with a portal to many related records, the local record data appears immediately and the portal data later, when it's ready. If you are navigating record-to-record in Form views of portal-laden records, the portal data does not have to fully load before advancing to next record. I don't see this mentioned in the FM15 Help new features page. A significant performance enhancement.
  9. This was an upgrade from Snow Leopard Server to Mtn Lion Server. I'm not having any troubles with the Server app nor with web serving.
  10. FMS 11v5 on OSX 10.7 with Java 7.51

    Your screenshot helped tremendously. Thanks! I was getting totally blocked when trying to install FMS11 on a Mac 10.8 system with Java 7 v51.
  11. I did the uninstall first. I rebooted twice.
  12. The new installer for FMS12 on Mac 10.9 does not work for me. During deployment, the Web Publishing Engine fails to stop and fails to start. I initially tried to deploy with the OS X version of PHP, then tried with the Filemaker-provided PHP and got the same result. Here is the deployment log. You can see the Error: 10007 instances on starting/stopping WPE. I don't know how to solve this problem. Machine is an Intel Core 2 Duo 2.66GHz with 4GB RAM running new install of OS X 10.9.1. Deployment started at 2/17/14 12:59 PM --------------------------------- SETUP: PRECONFIGURE WEB SERVER Stop web server succeeded Create FMI virtual directory configuration file succeeded Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf succeeded Update WPE deployment configuration succeeded Test web server (http://172.16.19.2:80/fmi-test/test.xml) succeeded SETUP: PRECONFIGURE WEB SERVER Stop web server succeeded Create FMI virtual directory configuration file succeeded Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf succeeded Update WPE deployment configuration succeeded Test web server (http://172.16.19.2:80/fmi-test/test.xml) succeeded UNDO EXISTING DEPLOYMENT Step 1: Unconfigure Web Publishing Engine (WPE): Stop WPE Error: 10007 Set WPE AutoStart to disabled succeeded Update JWPC prefs file succeeded Update WPE deployment configuration succeeded Step 2: Unconfigure web server: Stop web server succeeded Restart web server succeeded Update WPE deployment configuration succeeded START DEPLOYMENT Step 3: Save settings: Save administrative configuration settings succeeded Step 4: Configure Web Publishing Engine (WPE): Stop WPE Error: 10007 Set WPE AutoStart to enabled succeeded Add JVM Route to JWPC Server XML file succeeded Create WPC prefs file succeeded Create CWPC prefs file succeeded Update JWPC prefs file succeeded Start WPE Error: 10007 Update WPE deployment configuration succeeded Update mDNS service info succeeded Step 5: Configure web server: Stop web server succeeded Back up apache configuration file succeeded Create FMI virtual directory configuration file succeeded Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf succeeded Disable line in httpd_server_app.conf: AddDefaultCharset succeeded Disable line in httpd_server_app.conf: LoadModule info_module succeeded Disable line in httpd_server_app.conf: LoadModule status_module succeeded Disable line in httpd_server_app.conf: AddModule mod_info.c succeeded Disable line in httpd_server_app.conf: AddModule mod_status.c succeeded Disable line in httpd_server_app.conf: <Location /server-status> succeeded Disable line in httpd_server_app.conf: <Location /server-info> succeeded Add FMI status config file to apache config file succeeded Create FMI mod_proxy config file succeeded Disable line in httpd_server_app.conf: LoadModule proxy_ajp_module libexec/apache2/mod_proxy_ajp.so succeeded Add mod_proxy_ajp to apache conf file succeeded Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf succeeded Update FileMaker API PHP setting: : $__FM_CONFIG['hostspec'] = 'http://127.0.0.1'; succeeded Stop web server succeeded Start web server succeeded Update WPE deployment configuration succeeded Disable line in httpd_server_app.conf: LoadModule php4_module succeeded Disable line in httpd_server_app.conf: LoadModule php5_module succeeded Disable line in httpd_server_app.conf: AddModule mod_php4.c succeeded Disable line in httpd_server_app.conf: AddModule mod_php5.c succeeded Disable line in httpd_server_app.conf: <IfModule mod_php4.c> succeeded Disable line in httpd_server_app.conf: <IfModule mod_php5.c> succeeded Disable line in httpd_server_app.conf: AddType application/x-httpd-php .php succeeded Disable line in httpd_server_app.conf: AddType application/x-httpd-php-source .phps succeeded Create FileMaker PHP configuration file succeeded Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Web Publishing/publishing-engine/php/mavericks/httpd.fmi.conf.php succeeded Update FileMaker API PHP setting: : $__FM_CONFIG['locale'] = 'en'; succeeded Restart web server succeeded Step 6: Configure Database server (DBS): Set WPE Authorization Info succeeded Set XDBC AutoStart to yes succeeded Update XDBC deployment configuration succeeded Update WPE deployment configuration succeeded Start XDBC succeeded Step 7: Configure AdminServer: Save WPE deployment settings succeeded Save web server deployment settings succeeded Save DBS deployment settings succeeded Restart WPE Stopping the WPE(wpe1) component failed: error code = 10007 Reindex log files succeeded Deployment completed at 2/17/14 1:12 PM
  13. FM Server 9 upgrade

    You could upgrade to FMS11 but not FMS12, because the Mac Leopard machines cannot run client 12. Filemaker, Inc. will sell you 12 with a "downgrade" option for just a few extra $$. I don't know the last version of FM that could run on Leopard. Probably not 11. A client with FM9 could open a file hosted by FMS11, but v.10 and v.11 features would not be accessible. Your file does not have such features, yet. Any way you look at it, that Leopard machine is getting obsolete. Time to upgrade. Could it at leasts run Snow Leopard?
  14. :laugh:The Solution to this problem turned out to be the SC Base URL, again. Our new SC installation confused me. On my development server, running SC in standalone mode, there is always a SuperContainer folder that holds children folders "Files" and "thumbnails." On new host's server, running SC in Tomcat, we have a "supercontainer" folder which holds the individual files and no "Files" folder. On the new server, the thumbnails folder is a sibling of supercontainer folder. My host said the SC url is http://domain:port/supercontainer. It turned out that despite the lack of a Files folder, the url still needs to have that word. So the base url is http://domain:port/supercontainer/Files. I previously posted about a similar upload problem and the solution was the same. Kinda confusing... No Files folder but you still have to add "/Files" in SC_BASE_URL. Gary
  15. I have a web page that allows users to upload files using normal HTTP upload. The PHP page to process the upload uses PHP's standard move_uploaded_file() function to get the user's file into a known directory, called "docsTemp" on this system. That works. My script then calls the the upload method of SC's PHP class to move the file into the SC directory. That SC step fails with error 404 (not found). The goal is to move the file from docsTemp to a nested folder inside the SC folder. The script specifies a section/subsection folder structure. SC, when used through FM web viewer, will create folders as specified by the web viewer URL. So the folder I would expect my PHP script to create would be supercontainer/section/subsection/pkID. But instead, SC is creating folders named "0","1", "2", "3"..."9" that do have the uploaded file. After 10 attempts, the SC upload cycles back to moving the files into folder 0, then 1,2,3 thru 9. Why is SC not creating folders like it does through FM web viewer?
×