Hopefully someone will be able to assist with this issue, because I'm stumped at this point.
We have been in the process of migrating users from a workgroup to an Active Directory domain. All workstations are running XP Pro and Office XP (I realize the version of Office is quite old, but the customer does not have the funds to upgrade to a newer release at this time). Email is POP3 from a 3rd party company. We have been copying the contents of the users' old local profile into their new local profile for their domain account. For the majority of the users, there have been no issues. However, for a small percentage of users, we are running into an issue where they are not able to open or save any email attachments. When an attachment is opened, nothing happens. When an attempt to save the attachment is made, Outlook generates an error window stating "Outlook could not save the file". There are no errors in the Windows event logs as to what the error is. Upon checking the OLK directory, the attached file is there and can be opened without issues. The problem appears to be that Outlook is saving the attachment to the Outlooksecuretemp location, but fails to actually open the file. The user account is a member of the local administrators group on the workstation and has full permission to everything.
We have tried everything we can think of to resolve the issue, with no luck. We have deleted all files in the OLK directory and logged out/logged in or rebooted/logged in. We have changed the location of the OutlookSecureTemp location in the registry. We have created a new .pst file, sent a test message with a .doc attachment and were unable to open or save it. We have deleted all local profiles on the workstation and started from scratch. We have logged in as other users (including the Domain Administrator account) and configured Outlook and still are not able to open or save attachments. We have uninstalled/reinstalled Office with no effect.
We've searched through Experts-Exchange and the web in general for a solution. We have found many posts with similar issues, but they all have been resolved by deleting the files in the OLK directory, which has had no impact on the issue.
I have a feeling that there is a key in the registry that is causing the problems, since the problem occurs regardless of what user is logged onto the pc, but I have no idea what it could be.
If anyone has any ideas or has run across this issue, please let me know. I would rather not have to resort to completely reimaging the workstations that are affected.