Have you every wondered what error code -22 in Finder means, or error code -49 in iMovie. A lot of these are very simple and not at all helpful. Nothing is worst than an error message that simply says ‘Error!’. You might as well not have bothered telling me (this infuriates me at work). However, help is at hand. You can actually interpret the errors within Terminal. You can find out what the error code means. A way to determine what it means and how to solve it.
Determine Error Codes In Mac OS X
How are we going to determine what an error code means? The trick is simple, tell Terminal your error code and let it give you a response. For this trick we are going to use a Terminal commadn called
This command takes the error code you have and tells you the answer. For example in iMovie I occasionally get error code -49. If I type into Terminal (located in your Applications > Utilities folder) the following:
It will give the following output.
Mac OS error -49 (opWrErr): file already open with with write permission
This tells me that iMovie is trying to open a file that is already open. If I have the file open in two locations and it wants to write to it, there will be problems.
You can repeat this for any error code you encounter, some are more useful than others. These are general error codes that are system wide. So a specific application error code may not yield a response.
Note that -49 and 49 are two different error codes, therefore you must add a dash if one is present.
List of Error Codes
Below is a list of errors codes. I have not listed every single one as there are duplicates, and some that are not useful.
- error -50 paramErr: error in user parameter list
- error -49 opWrErr: file already open with with write permission
- error -48 dupFNErr: duplicate filename (rename)
- error -47 fBsyErr: File is busy (delete)
- error -46 vLckdErr: volume is locked
- error -45 fLckdErr: file is locked
- error -44 wPrErr: diskette is write protected.
- error -43 fnfErr: File not found
- error -42 tmfoErr: too many files open
- error -41 mFulErr: memory full (open) or file won’t fit (load)
- error -40 posErr: tried to position to before start of file (rw)
- error -39 eofErr: End of file
- error -38 fnOpnErr: File not open
- error -36 ioErr: IO error (bummers)
- error -35 nsvErr: no such volume
- error -34 dskFulErr: disk full
- error -33 dirFulErr: Directory full
- error -24 closErr: IO System Errors
- error -23 openErr: IO System Errors
- error -22 unitEmptyErr: IO System Errors
- error -21 badUnitErr: IO System Errors
- error -20 writErr: IO System Errors
- error -19 readErr: IO System Errors
- error -18 statusErr: IO System Errors
- error -17 controlErr: IO System Errors
- error -8 seNoDB: no debugger installed to handle debugger command
- error 16 dsFPErr: Floating point error
- error 25 dsMemFullErr: out of memory!
- error 26 dsBadLaunch: can’t launch file
- error 31 dsNotThe1: not the disk I wanted
- error 40 dsGreeting: welcome to Macintosh greeting
- error 41 dsFinderErr: can’t load the Finder error
- error 90 dsNoFPU: an FPU instruction was executed and the machine doesnÕt have one
- error 98 dsNoPatch: Can’t patch for particular Model Mac
- error 99 dsBadPatch: Can’t load patch resource
- error 101 dsParityErr: memory parity error
- error 20002 dsForcedQuit: allow the user to ExitToShell return if Cancel
- error 20003 dsRemoveDisk: request user to remove disk from manual eject drive
- error 20109 dsShutDownOrResume: allow user to return to Finder or ShutDown
- error 32767 dsSysErr: general system error
It takes a little bit of interpretation into why the error has appeared. However, with this little bit of information you might be able to do something about it.