Outlook problem: Can't open attachment; can't save attachment.

Is office 2003 SP3 installed?
http://www.microsoft.com/downloads/details.aspx?FamilyID=E25B7049-3E13-433B-B9D2-5E3C1132F206&displaylang=en

Do these users have the whole Office Suite Installed (Word, Excel....) or just Outlook?

>Apache09: SP3 is already installed.

>War1: I will try to delete it...

>War1: Outlook is one who reverting back reg settings. Try it, change it to Temp, run Outlook, open some message, open reg key again and it will be Temporary Internet Files again...

Why this is happening?!? Why Outlook cash all images and documents from mail to this location while he has them in my PST.

Is MS Word Installed and working?

>Apache09: Yes.

Here is a VBscript that can empty the folder in XP and up for Outlook 2003 and 2007. Works awesome for us. Can also be added as a startup script.

Set oWSH = CreateObject("WScript.Shell")
Set oFSO = CreateObject("Scripting.FileSystemObject")
 
For Each sKey in Array("11.0","12.0")
sOutSecTmp = Empty
On Error Resume Next
sOutSecTmp = oWSH.RegRead("HKCU\Software\Microsoft\Office\" _
& sKey & "\Outlook\Security\OutlookSecureTempFolder")
If Len(sOutSecTmp) > 3 Then
oFSO.DeleteFile oFSO.BuildPath(sOutSecTmp,"*.*"), True
End If
Next

Select allOpen in new window

We have te same problem, when outlook start the reg key is restored.

Actually, the reg key is not being "restored", per se... it is being recreated.

Each time you change the name of the folder (i.e. to TEMP), and then you reopen Outlook, it looks for the outlooksecuretempfolder and doesn't find it (because you changed its name). It then creates an outlooksecuretempfolder to store its temp files - hence the issue arrizes in another 99 *.pdf files (since it starts from scratch with each reset of the outlooksecuretempfolder.)

You can fix it each time it occurs by doing any of the following:
== Fix #1 ==
REGEDIT.EXE
       HKEY_CURRENT_USER\Software\Microsoft\Office\11.0*\Outlook\Security
(*use the highest number available and work backwards until you find the number path that houses the Outlook\Security path)
       Modify key "OutlookSecureTempFolder" - change it to anything, i.e. TEMP
Restart Outlook

== Fix #2 ==
1. Open REGEDIT.EXE and go to Edit -> Find... In the Find dialog box type "OutlookSecureTempFolder" without the quotes and locate that registry key.
2. That key will contain the actual folder location, and will look like:
C:\Documents and Settings\%USER_NAME%\Local Settings\Temporary Internet Files\OLK#\
(where # is a random letter or number)
3. Copy the location of that folder.
4. Click on Start -> Run... and paste the folder location from step #4 then click OK.
5. Windows Explorer will open that folder. delete all files present.
6. Restart Microsoft Outlook and you should be able to open your attachments.

And I've been told you can create a batch file to empty the folder for you.
del "c:\documents and settings\%username%\local settings\temporary internet files\(OLK folder name)\*.pdf"
It has been suggested that the batch be set to run on log-out or shut-down (rather than start up) so that sensative (temporary) files/materials are removed prior to leaving the PC (just an extra security precaution).

I am not familar with writing batch files or I would post instructions here.  (any help or instructions on writing a logout batch would be appreciated)

Since Outlook seems to name the OLK folder at random each time it creates it, there is no way to that I've seen to set up a batch file that applies to an entire floor staff's pdf issues - or even for two seperate people.  You need the exact OLK file name for each individual PC.  Each file would need to be taylor made for each user.

And finally...
  If you have the exact same problem with Outlook 2007 on a Windows VISTA workstation...
the files are stored slightly differently but the fix is the same.
C:\Users\<username>\AppData\Local\Temporary Internet Files\Content.Outlook\X30MWG3N

I would LOVE to know why some computers can count above 99 or how they delete the temp files and others - like the ones we're having issues with - can not.  If anyone can help us correct this - the illness - we wouldn't have to treat the symptoms anymore (regedits every couple of weeks or batch files)

May the fix be with you
Todd

As jdines commented, this is not a solution, it is a time ($$) intensive workaround. MS needs to come up with a solution.