Jump to content

jasonfb

Newbies
  • Posts

    3
  • Joined

  • Last visited

Everything posted by jasonfb

  1. I am trying to use the "Export Field Contents" script step, but when I output a file using this step I get one that is not encoded correctly. (To be specific, my web browser can't execute it properly). I've diagnosed the problem to the file not being encoded correctly-- when I re-save the file as Unix encoded UTF-8, it executes fine. Does anyone know of a way in FileMaker I can save a file as UTF-8?
  2. We are using FileMaker Server 7 and have remote users connecting to the server from a mix of Mac/Win FM client apps. Because we have set the Server to only show databases allowed for the user, the user is prompted to enter an account name & password once when they click on the host in the Open Remote window and again after they click "Open". I realize this double-password entry is because we set the server to only show dbs allowed for the user, and I also realize there's nothing that can be done about having two screens appear. On the Mac, we can click "Add to Keychain" so that the user doesn't have to enter the password ever-- the windows appear with the account name and password already filled in. Does anyone know how to do something like this on Windows? Out 1 Windows user doesn't like having to re-enter the account/password twice each time, so if there's a way we could "store it to the keychain" that's what we want. But alas, it's Windows. Any ideas? I think she has Windows XP but I can double-check if it makes a difference. Thanks for any tips
  3. getting the "Internal Server Error" message when trying to configure Web Publishing Engine FileMaker Server Advanced recap: Mac OS X 10.4 Tiger (mac mini), FIleMaker server Advanced 7.0 (updated FMS to 7.0v4 updated FMSA to 7.0v3) symptom: getting the "Internal Server Error" message when trying to configure WPE via the web interface at /fmi/config - after trying this problem (as described above) on the FSA forums, I attempted several uninstall/re-installs of FMS and FMSA from disk image, as recommended by many. I then even tried a clean install of Tiger (Mac OS X 10.4), a re-install of FMS & FMSA as outlined, and STILL got stuck with the same problem (Internal Server Error in browser) This is still the place I am stuck-- although I have learned along the way a great deal about what to look for, I need to know even more about what to look for and how to nail this one. Here are my notes and observations of the machine as of today: I have discovered that the Web Publishing Engine seems not to be running or loading, which is why I am getting the "Internal Server Error" message in the browser when I go to configure it (http://localhost/fmi/config) I do not see a process for the WPE in Activity Monitor-- the only filemaker processes running are 'FileMaker Server' and 'fmserver_helperd' -- I do not see any processes owned by 'fmweb' This is consistent with my observations of of the machine-- FIleMaker server is working fine but WPE fails to respond (because, as I have figured out with help, it is not loading) I have attempted to stop, start, restart, stop, and start the WPE by command line-- as specified on pg 52 of the WPE Installation guide-- I have even discovered (not specified in the manual) that you can execute the SystemStarter with the -d flag to show debugging information, as follows: sudo SystemStarter -d start "FileMaker Web Publishing" When I execute this command the WPE does not load (can see this from Activity Monitor). As I can see from the debugging info, it says some things I don't understand, and then the last thing it says is an ominous "Unknown service: FileMaker Web Publishing". Here are my questions about the debugging output (below) -- any assistance would be greatly appreciated. #1) There's something fishy about the disabled StartupItem: /Library/StartupItems/FileMakerPublishingEngine --- I'm not sure how to fix this. In the past I've repaired disk permissions (Disk Utility) and this has fixed the startup item warnings that appear in the OS. But here I'm NOT seeing warnings in the OS and I am WPE fail to load when I SystemStarter by command line to start it. #2) I don't really understand the 'required', 'uses', and 'found' -- can someone enlighten me here -- are these errors (i.e. what should it look like)? #3) I don't understand why it abruptly ends with "Unknown service: FileMaker Web Publishing" and if that has to do with #1 (the startup items) So where did I go wrong? The install was in the order specified (as discussed on that post http://www.fmforums.com/forum/showtopic.php?tid/168284/post/169897/ ) after a clean installation & Apple software update of Mac OS X 10.4 on a relatively brand new Mac Mini. Any other ways to examine the WPE startup problem? (Like, are there log files?) Terminal session with debugging output below.... sandbox:~ admin$ sudo SystemStarter -d start "FileMaker Web Publishing" Password: SystemStarter[228] Found item: FileMakerPublishingEngine SystemStarter[228] Skipping disabled StartupItem: /Library/StartupItems/FileMakerPublishingEngine SystemStarter[228]: Found item: FileMakerServer SystemStarter[228]: Skipping disabled StartupItem: /Library/StartupItems/FileMakerServer SystemStarter[228]: Found item: FileMakerServerHelper SystemStarter[228]: Requires: Evaluating Resolver SystemStarter[228]: Uses: Evaluating Disks SystemStarter[228]: Uses: Keeping Disks SystemStarter[228]: Uses: Evaluating Network SystemStarter[228]: Found item: Apache SystemStarter[228]: Uses: Evaluating Disks SystemStarter[228]: Uses: Keeping Disks SystemStarter[228]: Uses: Evaluating NFS SystemStarter[228]: Uses: Keeping NFS SystemStarter[228]: Found item: AppleShare SystemStarter[228]: Requires: Evaluating Disks SystemStarter[228]: Requires: Keeping Disks SystemStarter[228]: Found item: AppServices SystemStarter[228]: Found item: AuthServer SystemStarter[228]: Found item: CrashReporter SystemStarter[228]: Found item: Disks SystemStarter[228]: Requires: Evaluating SecurityServer SystemStarter[228]: Uses: Evaluating System Tunin
×
×
  • Create New...

Important Information

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