Recently while using Microsoft Outlook, I ran into a strange problem while trying to open an attachment that was inside an email. Each time I tried to open the attachment from the email, I would get the error message: “Can’t create file: groovypost.doc. Right-click the folder you want to create the file in, and then click Properties on the shortcut menu to check your permissions for the folder.”
Here’s a screenshot of the error message:
Fortunately, the fix is easy! But first, a little background information on the problem.
The user opens email attachments with the same name multiple times over a period of time as a result of a particular job function and/or workflow. (i.e. The user receives or accesses a public folder with email notifications that contain the same attachment name; to view them, they must repeatedly open them individually through Outlook.)
Every time an email attachment is opened in Outlook, then a cached copy of the attachment is created within an Outlook temporary OLK folder. This folder is generated with a random name and therefore is different for every user. To see this folder, view the registry key from the user’s profile based on their Outlook version. I wrote a post earlier on how to Find the Microsoft Outlook Temporary OLK Folder. Take a look there for a MAP that details the location of the OLK folder for all versions of Outlook.
Browse to the Outlook Temp OLK folder (also known as the OutlookSecureTempFolder) and delete all files matching the “<attachment name>(number).” Typically the list of cached attachments is not cleared out automatically and has reached the number of (99). Due to long file names, the cached attachment name is not able to grow any higher, and therefore file creation fails, which sends a notification to the user (hence the error message). But once the cached files are cleared out, the user should once again be able to open the attachments after restarting Outlook.
FYI – As a security measure, I recommend you delete ALL files in the OLK folder regularly OR, encrypt the entire folder using Microsoft EFS.