Jump to content

Gnurps

Members
  • Content count

    37
  • Joined

  • Last visited

Everything posted by Gnurps

  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. 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
  3. Plugin crashing Filemaker Pro

    Ryan, That worked. Thanks. Maybe add that solution to the documentation? Gary
  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. 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?
  7. 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...
  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. 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
  10. 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.
  11. 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.
  12. I did the uninstall first. I rebooted twice.
  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. 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?
  15. :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
  16. I developed a SuperContainer solution on a test server where SC ran in the standalone mode. All worked great. It's time to launch it on a live, production server, which has SC installed using the Tomcat method. The system is not behaving the same, nor the way I would expect.  Normally, SuperContainer places uploaded files into a Files folder within the SC directory. On the new, production server I am able to upload with both the SC plugin and the upload button in the SC web viewer. But for me the uploaded files are going into folders the top level of the SC directory. These folders, created by SC, are at the same level as Files. To initially create the Files folder, I uploaded a Files folder with a bunch of subfolders and documents using FTP. Maybe that was a mistake? Maybe I should have let SC build that Files folder itself? I also uploaded a thumbnails folder. Normally, there is an accompanying thumbnails folder, at the same level as Files, which stores multiple previews for each file at the size of any web viewer that has viewed the file. The files I'm uploading with SC don't have any accompanying thumbnails files; or at least I cannot see any thumbnail files. I seeing related problems with the web viewer. If I set its base url to "http://www.aiare.info:8072/SuperContainer/Files/", SC will display files that are actually not in the Files folder; files that are in folders at the same level as Files. The pictures I uploaded using FTP show nothing in the web viewer, even though the URL is actually correct for them. If I change the url for the web viewer to leave off the /Files/ folder, then the web viewer shows an error, for both files uploaded with SC and files uploaded with FTP. I tried changing the base used by the plugin, too. We're supposed to call a function SCSetBaseURL in the format SCSetBaseURL("http://server.mycompany.com:8020/SuperContainer/Files"). That works. If I leave off /Files, it does not. This is the behavior I would expect. But SC does not put files into the Files folder.  Accompanying screenshot shows folder structure. Folders named "62" and Admin__Program_Management were created by SC and I think should be inside Files. Below them are the Files and thumbnails folders I uploaded with FTP. Programs folder created by SC.  Any ideas out there?  Gary
  17. I don't know if I would call this problem "solved," but my SC plugin is now working on the live server. I just used a normal url in SCSetBaseURL, ending in /Files, despite the fact that my new host does not have a "Files" folder in the SuperContainer path. The "supercontainer" folder acts like the Files folder. There is a "thumbnails" folder at the same level as supercontainer folder, instead of inside the sc folder. Is this normal for a Tomcat setup? I have always used the standalone on my servers, where the structure is a SC folder, with Files and thumbnails folders inside SC folder.
  18. We upgraded our Windows Server running Windows Server 2003 R2 from FMS11 to 12 and PHP stopped working. All files with a.php extension yield a 404 error. We re-deployed several times. According to KB6538, the deployment wizard... None of those settings appeared: no ISAPI filter, no index.php in Documents tab, no .php mapping, and no Web Service Extension. Yet the deployment log says those changes succeeded. (log below) I did a little work to try to manually change those settings and decided I do not know IIS well enough. I don't know how to overcome this deployment problem, nor does our IT manager. Any ideas? Thanks. Gary Deployment log: Deployment started at 11/3/12 4:15 PM --------------------------------- SETUP: PRECONFIGURE WEB SERVER Stop web server succeeded Create PHP test page virtual directory succeeded Restart web server succeeded Start default web site succeeded Update WPE deployment configuration succeeded Test web server (http://128.117.97.210:80/fmi-test/test.xml) succeeded UNDO EXISTING DEPLOYMENT Step 1: Unconfigure Web Publishing Engine (WPE): Stop WPE succeeded 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 , Attempting stop..., , Internet services successfully stopped, , Attempting start..., , Restart attempt failed., , IIS Admin Service or a service dependent on IIS Admin is not active. It most likely failed to start, which may mean that it's disabled., , ErrorInput: 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 succeeded 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 succeeded Update WPE deployment configuration succeeded Update mDNS service info succeeded Step 5: Configure web server: Stop web server succeeded Back up IIS metabase succeeded Create PHP test page virtual directory succeeded Restart web server succeeded Start default web site succeeded Create worker properties file succeeded Create Workers mount file succeeded Install ISAPIRedirect web server extensions succeeded Create isapi_redirect properties file succeeded Create jakarta virtual directory succeeded Install Isapi redirect filter succeeded Update FileMaker API PHP setting: : $__FM_CONFIG['hostspec'] = 'http://128.117.97.210:80'; succeeded Stop web server succeeded Start web server , Attempting start..., , Start attempt failed., , IIS Admin Service or a service dependent on IIS Admin is not active. It most likely failed to start, which may mean that it's disabled., , ErrorInput: Update WPE deployment configuration succeeded Update FileMaker PHP ini file succeeded Create PHP ini registry entries succeeded Add PHP path to PATH environment variable succeeded Create PHPRC environment variable succeeded Uninstall FileMaker PHP Module succeeded Backup fcgiext.ini succeeded Add PHP extension to IIS succeeded Set PHP instance max requests to 10000 succeeded Set PHP activity timeout to 600 succeeded Set PHP request timeout to 600 succeeded Set PHP PHP_FCGI_MAX_REQUESTS to 10000 succeeded Update FileMaker API PHP setting: : $__FM_CONFIG['locale'] = 'en'; succeeded Restart web server , Attempting stop..., , Internet services successfully stopped, , Attempting start..., , Restart attempt failed., , IIS Admin Service or a service dependent on IIS Admin is not active. It most likely failed to start, which may mean that it's disabled., , ErrorInput: 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 Start WPE succeeded Reindex log files succeeded Deployment completed at 11/3/12 4:17 PM
  19. To solve this problem, we upgraded to Windows Server 2008 with IIS 7. We built a fresh install of the OS, ran the FMS 12 installer, and used the Deployment Assistant. It did install PHP, but PHP was still not working. Our IT guy had to do a lot of tweaks to get PHP running -- sorry, I don't know what he did. It was not as smooth as it should be, but at least we have CWP running again. Filemaker's PHP install came in with error reporting set to E_ALL + Deprecated. My check-email function used eregi which was deprecated recently. IIS was just throwing a HTTP 500 error -- unknown error -- and not displaying the PHP info. It took us a while to figure that out. Other files threw PHP errors because of the max-level reporting set in PHP.ini. The errors were our programming mistakes, but the HTTP500 error blocked the PHP error display and made it really difficult to learn what was going on. This install was way too complicated.
  20. The documentation for the SuperContainer PHP class says there is a method to download files: $localPath = $sc->download('uploads/12345', '/tmp'); How does one use this? Is it the action of a form from a submit button? A link? Are there any code examples beyond that one line example in the documentation? I'm building a full doc management solution in PHP using SC. People can click or right-click on the SC <iframe> or <img> to do the download, but a lot of people won't know that. A button to invoke the $sc->download() function would be better. Also, how does one specify the desktop as destination in cross-platform manner? Use a block like if(Mac), ~/Desktop, else if(Windows)...? Thanks. Gary
  21. I am trying to use the SuperContainer PHP API. It was working before, but is no longer. I am getting error 505. The message is "The requested URL returned error: 505". This same file and server used to work. What does 505 mean? Is there a list of the SC error codes anywhere? Are the codes for the API the same or congruent with the codes for the plugin,. Permissions? Destination folder is owned by regular Mac account on OX Server 10.6, with Read and Write. Group is wheel, read only. Gary
  22. While developing a new CWP solution, some of my pages have errors, like incorrect URLs. Whenever I call a page with an error, FM Web Publishing "freaks out" on my test machine running OSX Snow Leopard Server. Activity Monitor shows CPU activity in the 60-90% range. During this period, the web server serves pages very slowly, if at all. The database server shows high activity, too. FM Web Publishing eventually settles down to 0.1%, but it takes several minutes or more. Using the FMS Console to stop Web Publishing does not stop the activity. I have to also quite the database server to get it to stop. It's not infinite loops causing this. A simple incorrect URL will cause the problem (as well as other mistakes). Running FMS 11.04.404. Snow Leopard Server updated to newest. I don't recall ever seeing this problem before with FMS. It seems like FM Web Publishing should handle such errors much better. What to do? Must I reinstall FMS? Gary Sprung
  23. Position Title: Just a single programming task Description of Duties: We want to display our shopping cart on the same pages as our product listings. We want the add-to-cart function to update the cart on the page without refreshing the entire page, ala Ajax. We want this to be built using Jquery. Location: your work location Deadline: Within two weeks Skills Required: PHP FM API for PHP understand shopping carts Jquery and its AJAX functions and classes Contact Details: Gary Sprung, gary@gnurps.com or (303) 859-9331 Disclaimer: FM Forums does not endorse or warrantee these positions please contact the poster for further information regarding the position particulars.
  24. So what OS's are 32 bit these days? Aren't both OS X 10.6 and 10.7 64-bit? And Windows 7? And the Server versions of all of those? Don't we have to use the plugin to make SC work with web publishing, just to do the SetBaseURL at least? Gary Gnurps
  25. My client downloaded and installed the new 2.832 SuperContainer to deal with the Jave update issue. Unfortunately, they just double-clicked on the installer.jar file, which means they used installation option 2, installing SuperContainer into Apache Tomcat. We had been using SC with option 1, as a standalone server. I had the client open installer.jar and use its uninstall option. However, two problems remain. First, the images display in the web viewer at their original size, not sized to the web viewer. Second, when I access the database via Internet, the web viewer displays an error: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException com.prosc.supercontainer.web.JSPModel.getIconUrl(JSPModel.java:425) com.prosc.supercontainer.web.JSPModelFilter.doFilter(JSPModelFilter.java:96) com.prosc.supercontainer.web.ActionFilter.doFilter(ActionFilter.java:103) com.prosc.supercontainer.web.RegistrationFilter.doFilter(RegistrationFilter.java:82) com.prosc.supercontainer.LogFilter.doFilter(LogFilter.java:38) note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs. It seems we have not fully uninstalled option 2. What do we need to do to return our server to its original condition? Must I reinstall FileMaker Server? Or perhaps just change the Apache config file? Worst case scenario is a full reinstall of Apache, which would probably mean a full reinstall of the OS X. Thanks. Gary Sprung
×

Important Information

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