Ironically enough for the same reasons I tend to disagree.
For these types of problems, locked files, invalid formats, etc. They're generally something that's easy to check for. In my world the user entering filenames that might not exist, a text or XML not being of the expected format, or not having write access are all considered common occurances. It's just something that should be checked.
Programatically handling an error can be easily done with an error handler without breaking modular code. (Generally something I consider a utility anyway) You call your error utility to notify where and what type of error occured, (and the severity,(silent, log, popup to the user, critical))the error handler knows how to handle the GUI, (potentally even waiting for user input) and you can continue on with execution as normal.
Note @Arevos:
Googling for: When to use exceptions : comes up with a blog with a point of view similar to your own
Blog Linky
Googling for : Proper use of exceptions: comes up with an article similar to my point of view
Article Linky
They're both good reading, and might give everyone a better idea of what exceptions should be for.
-MBirchmeier