ewit
asked on
Outlook Attachment Preview Slow After Server Shutdown
Recently we have moved all shares from an old file server to a new one. The shares on the old server were then disconnected, and everything seemed to be working fine using only the new server. Once we shut the old server down, Outlook started to take an unreasonable amount of time to open attachments by double clicking them in the email. Saving the attachment first and opening from the local computer works at normal speed. Turning the old server back on seems to fix this, but we are looking to retire that machine.
Hi, ewit.
Is Outlook running in cached mode?
Is Outlook running in cached mode?
ASKER
Net use doesn't show any connections to the old server. BlueDevilFan, we are running Outlook in cached mode. I have deleted users' content.outlook files in their Temporary Internet Files, but that didn't seem to help.
If Outlook is running in cached mode, then opening/previewing/saving attachments should all take place locally. It shouldn't matter whether the old server is available or not. What happens if you set Outlook to work offline and open one of these same attachments?
ASKER
It looks to be taking the same amount of time to open attachments when in offline mode. I tried opening before and after turning off Cached mode. I know these problems don't appear related to a server being turned off, but this all started happening at that point on 30+ machines.
I understand. I don't think the server is the issue though. Since it takes just as long to open the attachments when working offline, and that eliminates the server entirely, it seems like the problem is local. Have you tried deleting Outlook's cache file (i.e. Outlook.ost) and letting it create a new one? If you're nervous about deleting the cache file, then you can move it to another location and move it back later on.
ASKER
BlueDevilFan - Deleted their .ost and reopened Outlook and let it rebuild their local inbox. Still the same results with opening the attachments.
Then I'm stumped. I've not seen this behavior before.
ASKER
I think I might have a lead...Add-Ins. There is a PDFMOutlook Add who's load behavior states: "Not loaded. A runtime error occured during the loading of the COM Add-in." Figuring it needed updating, I started and canceled the update. The error that popped up said "Error 1606. Could not access network location \\OLDSERVER\Users\USERNAME
Good deal! Glad you have a fix and thanks for sharing it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This particular method worked in our cases, because the microsoft program installer was looking for the user's home directory on the network. While the registry key solution worked in some cases, rebuilding the profile worked in all, so there was some local piece of data that was never located causing the problem.
You're welcome!
If you do a NET USE in a command prompt what does it show?