When you try to open a Microsoft Office for Mac document, you may receive the following error message:
The operation could not be completed
An unexpected error occurred (error code -10660)
This issue occurs when one of the following conditions is true:
- You created the Office for Mac document with the Microsoft Office for Mac Test Drive, and the Office Test Drive is in the Trash.
- You have more than one copy of the same version of Microsoft Office for Mac installed on your computer.
- The Mac OS X Finder could not locate the Office for Mac program that owns the Office for Mac document.
- The Office for Mac document has the wrong file name extension associated with it.
To resolve this issue use one of the following methods.
Remove additional copies of Office for Mac
To remove additional copies of Office for Mac from your computer, follow these steps:
- Click Empty Trash on the Finder menu.
- Click Find on the File menu.
- Click Local Disks on the Search in list.
- In the Search for item whose area, click Name in the Item list, click Contains in the Condition list, and then type Microsoft Word for the value.
- Click Search.
- If two or more Microsoft Word X for Mac programs are found, click the first one that is found, click Get Info on the File menu, and then note the version number.
- Single-click the next instance of the Word X for Mac program that was found, click Get Info on the File menu.
- If the two Word for Mac programs have the same version number, you must remove both versions of Office for Mac from your computer.
For additional information about how to remove Office for Mac from your computer, click the following article number to view the article in the Microsoft Knowledge Base:
312172Â
(http://kbalertz.com/Feedback.aspx?kbNumber=312172/
)
How to remove Office v. X for Mac and Office 2004 for Mac Standard
- Install a single copy of this version of Office for Mac on your computer.
Re-associate document types with the Office for Mac program
If you do not have more than one copy of an Office for Mac program on your computer, or if you removed the duplicate copies of the same version of an Office for Mac program, you may still receive the error message that is mentioned in the “Symptoms†section. If you still receive the error message that is mentioned in the “Symptoms†section, you must re-associate each Office for Mac document type with their parent program. To do this, follow these steps:
- Locate one of each type of the Office for Mac documents that you regularly use.
- Click the first Office for Mac document, and then click Get Info on the File menu.
- Click the Open with tab.
- Click Other from the list of programs.
- Locate the Office for Mac program that owns the document type, and then click Add.
- Click Change All, and then click Continue.
- Repeat steps 3 through 6 with each document type for Office for Mac.
Verify file name extension
If the issue occurs with only some of your Office for Mac documents, verify that the Office for Mac documents have the correct file name extension. To do this, follow these steps:
- On the Finder menu, click Preferences.
- Click the Advance tab.
- If cleared, click to select the Show all file extensions check box.
- Close the Preferences dialog box.
- Click the document that is experiencing this issue, click File, and then click Get Info.
- Click the Name & Extension tab.
- If selected, click to clear the Hide extension check box.
- At the end of the document name, type the appropriate file name extension from the following list depending on the program that you are using:
- For Microsoft Excel workbooks, type .xls
for the file name extension.
- For Microsoft Excel template, type .xlt
for the file name extension.
- For Microsoft Word documents, type .doc
for the file name extension.
- For Microsoft Word templates, type .dot for the file name extension.
- For Microsoft PowerPoint presentations, type .ppt
for the file name extension.
- For Microsoft PowerPoint templates, type .pot for the file name extension.
- Close the Get Info dialog box.
- Repeat steps 5 through 9 for each document that is experiencing this issue.