Link to home
Start Free TrialLog in
Avatar of Brian B
Brian BFlag for Canada

asked on

Can't Open Attachment in Outlook

We have had several occurences of this problem, but I can't always reproduce it. When an Outlook 2010 user opens a file attached to a message, they get an error like this:

C:\Documents and Settings\username\Local Settings\Temporary Internet
Files\Content.Outlook\F2E0M??\filename.xls could not be found.  Check the
spelling of the file name, and verify that the file location is correct.

This seems to happen for Excel the most, but we also deal with a lot of Excel files here. After the error, the program for the attachment stays open, but the file is not open. If you go back to the message and double-click the attachment again, it will open.

From what I can tell, this is not the same as the "object not found" that I am finding in my searches, since the program is opening.

I was wondering if anyone has come across this specifically, or has any ideas about the problem. This issue has happened in both XP SP3 and Win7, but always with Outlook 2010.
ASKER CERTIFIED SOLUTION
Avatar of skrga
skrga
Flag of Croatia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Dan Muzrall
Dan Muzrall
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Rick
Rick

Try this:

Go to the control panel > Folder Options > File Types
Select XLS
Click Advanced > Open entry > Edit
Uncheck "Use DDE"
In the application box add a space then "%1" to the end of that string
Avatar of Brian B

ASKER

Interesting ideas.

@skgra & @moonie, I would think if the filename was the problem, it wouldn't open the second time either, but stranger things have happened. Although the file I was sent as an example is a long filename.

@rick_gwu, I'll try that for XLS and XLSX, but the problem is I can't reproduce the issue. I would also hate to think this is the global solution as it would mean updating 80 PCs.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Brian B

ASKER

Actually, the path I used is just an example of the error message I copied from somebody else. Don't know for sure my users' had those question marks.

So it kind of seems like there is no specific solution, just workarounds.
Avatar of Brian B

ASKER

I didn't mean to accept my own comment as part of the solution. Please correct.
Avatar of Brian B

ASKER

Thanks for all the help. There was no specific solution, but as a fellow expert I appreciate the effort and it got me looking in the right places.