Outlook 2003 showing Red X in E-Mails with embedded pictures

[Paul]

I am having some users who have an issue with outlook 2003 showing a Red X
when they send an e-mail or received an e-mail with an embedded picture. If
they forward the e-mail they then see the picture. I know there is a
temporary solution by deleting the files in the temporary outlook folder
(OLK). What I am looking for is a permanent fix so we don't have to go and
clear out OLK folders every few weeks.
Thanks

 

[Nikki Peterson]

RED X’s IN EMAIL

When pictures in your email won't download, even though you have Outlook
configured to download external content (or allow it on a per-message
basis), the problem is usually a "full" temporary file folder.

You need to locate the SecureTemp folder and delete the contents (or the
entire folder) then restart Outlook. The images should display correctly.

The SecureTemp folder for Outlook 2000 to 2003 installed on Windows XP is
at
C:\Documents and Settings\username\Local Settings\Temporary Internet
Files\OLK*. The OLK directory will end in a series of numbers.

Outlook 2007 places the Secturetemp folder at
C:\Documents and Settings\user\Local Settings\Temporary Internet
Files\Content.Outlook\8A0VMD3A, where 8A0VMD3A can be any random characters.

Vista moves the Temp Internet folder to
C:\Users\username\AppData\Local\Microsoft\Windows\Temporary Internet Files\,
so you'll need to look there for the OLK or Content.Outlook folder.

You can look in the registry for the location of the folder by looking in
the registry. You can change the folder to point to a new location, but be
sure the new folder exists before changing it in the registry. The
OutlookSecureTempFolder value (for Outlook 2007) is at
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security. For older
versions of Outlook, change the 12.0 to your version number.

Nikki

 

[Diane Poremsky {MVP}]

Instruct users on the proper way to open attachments so the securetemp does
not get "full" of orphaned files. You could also use a log on script to
clean it out daily or weekly.

http://www.slipstick.com/outlook/securetemp.htm

 

[Nikki Peterson]

Thanks Diane! I didn't know that page existed.
Very good information.

Nikki Peterson

 

[Frenchy]

Instruct users on the proper way to open attachments so the securetemp
does not get "full" of orphaned files. You could also use a log on
script to clean it out daily or weekly.

http://www.slipstick.com/outlook/securetemp.htm

I am running Office 2007 on Vista Ultimate. I have all hidden folders
to show and there is no such folder as content.outlook and nor the next
alpha numeric folder.

In fact in the Reg key, it points to such a folder but there is no
folder of that name.
I have changed it to point to a specially made new folder, but that has
done nothing for the red x problem. Note the new folder remains empty
after an hour of opening and closing attachments in Outlook 2007

Frenchy

 

[Brian Tillman]

I am running Office 2007 on Vista Ultimate. I have all hidden folders
to show and there is no such folder as content.outlook and nor the
next alpha numeric folder.

Windows Explorer has code in it to prevent being able to see that folder by
traversing the folder tree. Manually enter the path into the Address bar
and you should be able to see it.

I have changed it to point to a specially made new folder, but that
has done nothing for the red x problem. Note the new folder remains
empty after an hour of opening and closing attachments in Outlook 2007

Did you stop and restart Outlook after making the change?

 

[Frenchy]

Windows Explorer has code in it to prevent being able to see that folder
by traversing the folder tree. Manually enter the path into the Address
bar and you should be able to see it.

Thanks, I did that and saw the folder, only 6 files in there, all from
last 1-2 days

Did you stop and restart Outlook after making the change?

I did, but it made no difference and now I can 'see' this folder, I have
reverted to this in the Reg Key

Thanks your clarification, although I still have the red x problem, that
you have flagged in the past as 'known by MS, but no solution yet'

Frenchy