Darrin King

We currently run FileMaker Server Advanced 11 on Mac OS X server. We will be making the move to FMS 13 in the next 6 months and are exploring the option of moving our FMS to our Windows virtual server farm. We use the AppleScript script step in a few of our solutions to run shell scripts and modify text files in the OS on the server. I am struggling to find an equivalent method for the Windows side. Below are a couple of examples of what we currently do. My hope is someone here can post an explanation with examples to get us off and running. #Add header to export file and convert to Windows CRLF Perform AppleScript [ Native AppleScript: --Add header row do shell script "perl -i -lne 'if($.==1){print "uidNumbertgidNumbertSamAccountNametPasswordtSurNametGivenNametEmailAddresstHomeDirectorytadPathtLocaleIDtphysicalDeliveryOfficeNametUpdateFlagr$_"}else{print}' ~/Desktop/AD_Account_Info.txt" --Convert from Mac to Windows line breaks do shell script "perl -i -pe 's/015/015012/g' ~/Desktop/AD_Account_Info.txt" ] #Add Date & Time Stamp to file name Set Variable [ $DateTimeStamp; <calculation redacted 'cause it's gnarly> ] Perform AppleScript [ Calculated AppleScript: "do shell script "mv ~/Desktop/AD_Account_Info.txt ~/Desktop/AD_Account_Info_" & $DateTimeStamp & ".txt"" ] Regards, Darrin

Hi Steven, Here are the permissions. I set them according to the documentation. -rwxrwx--- 1 fmserver fmsadmin 7.6K Jul 29 09:43 sentinel_amdb.sh -rwxrwx--- 1 fmserver fmsadmin 3.4K Jul 25 15:24 sentinel_volunteer_db.sh -rwxrwx--- 1 fmserver fmsadmin 7.5K Jul 25 14:24 data_downloader.sh Regards, Darrin

HI Vaughn, It is not a specific script that is causing the problem. It is ALL schedules that use a shell script in pre or post flight that fail. Schedules that do not call shell scripts continue to work fine. Regards, Darrin

Well this issue has cropped up again a couple of times since early August. Most recently today between 11:30 and 12:00. Restarting the box seems to clear up the issue, but it then returns with in a couple of weeks. I am at a loss as to why this is happening. Any thoughts? Regards, Darrin Mac OS X Server 10.5.4 xServe 2.66 GHz Dual-Core Intel Xeon FMS 11.0.3.309

Quick Update: A restart of the box seems to have cleared things up. Keeping my fingers crossed.... DK

For the second week in a row, all my server schedules that call shell scripts started failing with the following Error in the event log: Error 154 Schedule "<schedule name>" aborted; "<shell script name>" could not be found or is invalid. Just started happening in the middle of the night last night. The only fix I could figure out last week was to reinstall the server. Any thoughts?

He he he. Even a blind squirrel finds a nut every once in a while. FYI- Here is the link for bug reporting. http://www.filemaker.com/company/problems.html Regards- Darrin

I've seen this exact issue with all new installs of FMP 8.5 & 9 on our network since I reinstalled our FMP 9 Server last week. The explanation regarding the server.pem cert file from KB article # 5493 got me thinking this might be an SSL issue. http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/enduser/std_adp.php?p_faqid=5493 Sure enough, when I turned off the Secured Connections option in the FMS Admin application the clients could then see the files being broadcast and open them up. That gets us up and running for now. Unfortunately I have no idea how to fix this cert issue. Regards, Darrin

Not recently. I was able to the track progression of the corruption using our nightly backups. The records became corrupt over a two day period (Friday and Saturday). On Saturday the file was only accessed by our "Sentinel" box so that leads me to suspect it. This box is set up to automatically import data every morning around 5:45 AM & runs 24/7. It has not had a problem in weeks so I don't think it is crashing out, but the imports are kinda big so that might be munching the data. As for the conversion question... Yes, it has been converted over the years starting with FMP 4 or 5. I've never seen problems like this in any of our DB's hosted by FMS 4, 5 & 7. We did upgrade this year to FMP 9 Server Advanced, but can't directly tie this issue to the upgrade. Thanks, Darrin

I've seen this a couple of times in different DB's where a record in a database display question marks (?) in all the fields. When I perform a file recovery, no errors are reported, but the record in question disappears. What is odd is the record can be found based on data that was on the record, say, by Student ID number. As far as I can tell the record is completely corrupted so I import a good copy of the record from a backup. Any ideas on why this is happening?

Ok, I switched back to using the bw keyword as suggested by you and page 83 of the FMSA CWP guide. Being able to access all the FMP find operators is a really cool feature! Unfortunately it is not working for me. I still get a 401 error (No Records Match Request) when I specify a value of "==". Any other thoughts? Compounding my frustration, I have discovered the CWP engine will pass wildcard find operators to the database. All someone needs to find a record (or records) in this solution are the first couple of characters of the ShortName and Password coupled with a "*". Not good since this is an authentication database I'm trying to grant access too. Thanks, Darrin

I replaced the following code for the password field: Password: Password Password With the suggested code of: Password: and FileMaker returns an error code of 401 (No Records Match Request). Note: I did change the operator value from 'bw' back to 'eq', but I've tested both ways and that doesn't seem to make a difference. What am I doing wrong? Thanks, Darrin

Thanks Martin that answered by question. My problem now is it only works if a user enters data into a field. If a field is left blank then the match requirement is skipped. How do I make a find request require exact matches in two different fields (i.e. shortname AND password must match to find the record). I thought the tag would do the trick but it doesn't get me where I want to go. The find executes just fine with the password field blank. Thanks, Darrin

Using the FileMaker Site Assistant, I generted a simple stylesheet that does a find on a database. The generated code provides a drop down menu for each field to select the desired operator. <tr> <td align="right" width="25%"> <b>ShortName: </b> </td> <td align="left" width="5%"> <select> <xsl:attribute name="name">ShortName.op</xsl:attribute> <option selected="selected" value="eq">Equals</option> </select> </td> <td align="left"> <input size="50" type="text"> <xsl:attribute name="name">ShortName</xsl:attribute> <xsl:attribute name="title">ShortName</xsl:attribute> </input> </td> </tr> Can these operators be hard coded so they are not a user definable selection? If so how? Thanks, Darrin

Duh. Works like a champ now. Thanks!!