Export to XL - "Cannot Create File on this disk"

[Shane Ervin]

I can't export to Excel using FM_9 Advanced on my Leopard Mac. The error message states: " cannot be created on this disk. Use a different name, make more room on the disk, unlock it, or use a different disk."

I can't "Save as..." using Excel as the file type, either.

.pdf exporting is ok. .csv exporting is ok.

[iMarcW]

Are you saving from a script? I had a problem saving on Windows (not on Mac) and it was the filewin:/filemac: prefix (or lack thereof) that was causing the problem:

http://fmforums.com/forum/showtopic.php?tid/196235/

[Shane Ervin]

No, I was simply using the command(s) from the file menu.

I'm scratching my head here.

Thanks for the reply!

[iMarcW]

A few other things to look at:

Folder permissions (where you're saving the file)

Unacceptable characters in the filename

FileMaker user privileges

[Lee Smith]

I've seen this message a couple of times. It happen to me when I was using an external HD as the Leopard Drive. There was a difference in my iBook Drive, and the External HD in the User ID, and PW, and I would get that message when trying to save to the iBook when using the External's System.

HTH

Lee

Edited July 8, 2008 by Guest

[Shane Ervin]

Yeah, I was double-checking all of those "usual suspects", but to no avail.

Thanks for the kind suggestions, though.

I see another poster may be on to something with his reference to an external drive (I have one too; for Leopard's Time Machine). I'll pick up the trail there.

[Shane Ervin]

It's late, and I'll check into this tomorrow. But I do use an external HD for Leopard's Time Machine.

It's a promising lead! I'll post with my results. Meanwhile, thank you for posting!

[Kent Searight]

Did you try appending the file path to begin with "filemac:" (or "filewin:" if you're testing on Windows too) as suggested by iMarcW . That's what I suspect the problem is.

Try something like this:

$filePath = "filemac:" & Get (DesktopPath) & "spreadsheetName.xls"

and see if that fixes the problem

[Venom71]

I'm having the same issue. FMP Advanced 9.0v3 on OS X 10.5.4. Not trying to export using a script - I did initially but then reverted doing it manually from the File Menu option.

Incidentally, and it may be related only more experimentation will tell, I am also getting "Port Conflict" messages when I start FMP and IWP will no longer start.

Here is the bug dump:

Process: OLEWrapperRPCServer [29813]

Path: /Applications/FileMaker Pro 9 Advanced/FileMaker Pro Advanced.app/Contents/Frameworks/OLEWrapperRPCServer

Identifier: OLEWrapperRPCServer

Version: (

Code Type: PPC (Translated)

Parent Process: FileMaker Pro [26483]

Date/Time: 2008-07-09 14:15:06.369 +1000

OS Version: Mac OS X 10.5.4 (9E17)

Report Version: 6

Exception Type: EXC_CRASH (SIGILL)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Crashed Thread: 0

Thread 0 Crashed:

0 : 0x801a308a 0 + 2149200010

1 translate 0xb80ecd11 gettimeofday_wrapper + 37593

Thread 1:

0 0x800bc4a6 0 + 2148254886

1 0x800c3c9c 0 + 2148285596

2 translate 0xb818b6ea CallPPCFunctionAtAddressInt + 202886

3 0x800ed6f5 0 + 2148456181

4 0x800ed5b2 0 + 2148455858

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0xb813cfcc ecx: 0xb7fffa6c edx: 0x801a308a

edi: 0xb81d8794 esi: 0x00000004 ebp: 0xb7fffa98 esp: 0xb7fffa6c

ss: 0x0000001f efl: 0x00000246 eip: 0x801a308a cs: 0x00000007

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

cr2: 0x002b7008

Binary Images:

0xb8000000 - 0xb81d7fe7 translate () /usr/libexec/oah/translate

Translated Code Information:

NO CRASH REPORT

[Venom71]

I've reinstalled FMP Advanced 9.0v3, cleaned up IWP so it works [again], repaired permissions [just to make sure] and am still getting this error when attempting an Excel export. It appears to me that OLEWrapperRPCServer is crashing.

EDIT: Logged with Filemaker as a bug.

Edited July 9, 2008 by Guest

[Codeus]

Could Office 2008 be a common factor?

It does screwy things with file associations (UTIs) (eg. breaks the way Safari downloads excel docs, wouldn't surprise me if it was at the root of this problem too).

[TRNET]

Good News!

I removed my FM prefs and I no longer get the "cannot be created on this disk" error when I export to Excel.

-Quit FM

-Find the pref file and move it to the Desktop for back up. (User:Library:Preferences:FileMaker Preferences)

-Restart FM

-Set memory file cache in preferences to 256 Mb

-Reset your other prefs

Thanks to Jack Rodgers - MacIntouch .

UPDATE

The error came back.

Turning off all my plugins, it worked again.

When I followed the procedure above, I also turned off my plugins which is why it actually worked, not because of removing the prefs file.

It seems that the plugin, Troi File is the culprit. Well it is for me anyway.

I tried using FileFire Express by Dacons for the part of my script that opened a dialog to name my export file(instead of Troi File) and it worked.

Everywhere else I use Troi File, I have had no problems ... so far.

I hope this helps.

Edited July 29, 2008 by Guest

[Merit Solutions]

I have a similar problem - it refuses to save exported pdf (Append not set) even when using the absolute pathname:

filemac:/Macintosh HD/Event Horizon ƒ/Db/$FN

it worked initially but now refuses and comes up with the "disk is locked error"

FM9 Advanced on Leopard.

[WC Banta]

I had the same problem, with the same error message: "Filename.xls could not be created on this disk. Use a different name, make more room on the disk, unlock it or use a different disk." I had no luck trying any of the suggestions listed.

[smoore]

I had a similar problem - just trying to save a new file from FMPA 11.0v2 to a folder on my desktop resulted in "cannot be created on this disk" error. I removed SMTPitPro 4.1.12 (their latest version) from /Applications/Filemaker Pro 11 Advanced/Extensions and that fixed it for me. (Mac OS X 10.6.6 on MacBook Pro)