Server-side Export, OK Status, File Not created

[DanielScott]

We're running FM Server 11 on Windows Server 2003 R2.

I've followed the export instructions to the letter, and have read everything I can find on the topic. My script is as follows:

When I run the script on the server, the Status is "OK," and these are the logs:

2010-10-28 08:00:41.704 -0600 Information 518 SPECED01 Administrator connected: "fmadmin [162.99.12.87]" (admin console).

2010-10-28 08:00:54.970 -0600 Information 146 SPECED01 Schedule "Daniel ProComp Export" run now by "fmadmin [162.99.12.87]".

2010-10-28 08:00:54.970 -0600 Information 689 SPECED01 Schedule "Daniel ProComp Export" has started FileMaker script "Daniel Export ProComp Data".

2010-10-28 08:00:55.236 -0600 Information 150 SPECED01 Schedule "Daniel ProComp Export" completed.

Yet the file never appears in C:Program FilesFileMakerFileMaker ServerDataDocuments. There's nothing there. I've even done a system-wide search for the file name, just in case, and it's nowhere to be found. The script also seems to run really fast...on the client a similar script takes a few seconds.

Any ideas? Thank you!

[Steven H. Blackwell]

Take a look at this FMF article.

Steven

[DanielScott]

Thank you for the reply -- I looked at that article, and others written by FMPro experts. I'm following (I think) the instructions to the letter.

I even tried to export one file on the server that has only three fields, and is not linked to other files. I get the same problem. The Status is "OK," the logs show everything as running just fine, but...no file is created.

My permissions look okay, and the backup writes to the correct folder. It's just the export that won't work.

Thanks again!

[Wim Decorte]

do some error trapping after the goto layout, show all records and export script step (log the errors to a field so you can inspect it after running).

[DanielScott]

I error-trapped, re-booted servers, and banged my head against this problem forever. I also spent 40+ hours trying to get FileMaker Server to act as an ODBC data source so I could connect via SQL Server. I had *no* luck with that, and I'm pretty well-versed in ODBC. The Web has numerous complaints about the same problem.

SO...I went back to working on an export. If I can export it, I can pick it up via MS Integration Services and bring it into SQL.

The export solution? On the Export Records step of the export script, activate the checkbox for "Specify export order." I didn't see this documented anywhere, but that seems to have been the magic bullet. Just wanted to document it here in case some other poor soul is dealing with this problem.

I'm no Microsoft evangelist, but FileMaker server doesn't play very well with other (non-Mac) data sources. I find their marketing claims in this area to be very, very dubious in real-world situations.

[Steven H. Blackwell]

The export solution? On the Export Records step of the export script, activate the checkbox for "Specify export order." I didn't see this documented anywhere, but that seems to have been the magic bullet. Just wanted to document it here in case some other poor soul is dealing with this problem.

Well, if you don't supply an export order nothing gets exported. You must select the fields to be exported when you create a scripted export. There are several ways to do this.

Steven