Hello All, I have an unusual situation, I think. We have approx 70 users on an Exchange 2010 SP1 server and these 70 users aren't "heavy duty" users. This issue affects some, but not all users. In ia nutshell, when an email is sent with an attachment, some users will get the attachment, some won't. For example, the office administrator lady sends an email to all users, with a basic word document attached, not everyone will get the attachment. As a test, the office admin lady also copied herself into an email that she sent out and she did not get the attachment on the message in her inbox! But here is the kicker. If the office admin lady then logs into her mailbox via Outlook Web App, the attachment is there! Also, the message in her sent items also has the attachment. Most odd. All users have Office 2010 Pro, fully patched. Some users have cached moded enabled (those who have laptops), but majority of users who hot-desk have cached mode disabled. I also have GFI Mailessentials and Mailsecurity running, but I cannot see anything unusual there in the logs. Exchange 2010 SP1 is running as a virtual machine on Server 2008 R2. 4 cores assigned with 12Gb RAM and plenty of disk space remaining. Server also runs the 3 basic roles - Client, Hub and Mailbox. No UM or Edge. Anyone point me in the direction to start looking? Thanks, Jamie

Hi, Please restart exchange Mailbox server to resolve any potential issues. Step 1. If the issue persists, then try to create a new Outlook profile. Step 2: Test the problem in another computer. If you can see the attachment by Outlook 2010, the problem should be in the corrupted windows profile or Outlook client. Gen Lin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Hi Jamie, How troubleshoot is going on?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Sorry - have been abroad at another site. I am implementing some of these changes Feb 4 and will see if this helps. Will keep you posted!

Hello, I have the exact same issue with one user and recently upgraded the Exchange server to Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3 (KB2530488). I have, however, notice this issue occasionally over the years with Outlook and Exchange clients but my current user with the issue is having problems with PDF documents and it's every day. Any other recommendations to try? Rebooting Exchange doesnt help. Thanks in advanced, Gil

Low and behold... the same issue here, tried everything mentioned above and more. Anybody? Bueller? Bueller??

Hi, I have a slightly different problem...I had archived my outlook 2010 emails at work in the "archive" file. I copied this file onto my external portable hard drive. I bought Outlook 2010 (as a part of Office 2010-Home and Business) for my home laptop. I linked the archive file to the Outlook on my home PC. When I tried to open the files with attachment, all I see is the file listed but no attachment (see the example below)! This only happens to the files older than Dec 31, 2011...All the newer emails (newer than Jan 01, 2012) with attachment are perfectly fine! E.g. of the messed up email with word attachment (from Dec 15, 2011): ....It will be great if you can send me your feedback by noon tomorrow. I will then quickly incorporate your thoughts then we can circulate the finalized version. Many thanks xxxx << Important.doc (39.0KB) (39.0KB) >> ----------------------------------------------------- Thanks in advance for your help! I have tried all the suggestions that are given above but nothing has worked. Also, the Outlook tech (from Microsoft) tried SCANPST to repair the archive file. That didn't work either! -KRSN1 krsn1@yahoo.com