Link to home
Start Free TrialLog in
Avatar of carotomp
carotomp

asked on

Exchange 2010 and outlook 2010 "can't open this item" error and reading pain not working.

All-
I have just implemeted an Exchange 2010/ Server 2008 R2 domain.  everything worked fine the first couple of days, now on a few of the clients, when outlook 2010 open, the emial is there, but it doesn't show up on the readin pain, and if I click on it it displays, "can't open this item" error box.

Background:
We were running a 2003 32bit enviroment with exchange 2003.  We upgraded this weekend to a 2008 R2 64bit with exchange 2010 running with all of the updates and SPs installed.  When we moved the mail boxes, we just exported out the PST.  We then removed the computers from the domain,  built the clean 2008 R2 domain, with same name and exchange server name...i.e server name and exchange name stayed the same, along with static IP.  

We then brought the computers back into the domain and then imported the PST files back in to exchange.  We have 10 win 7 clients running office 2007 and 2010, and 40 clients running XP and office 2003 and 2007.  

All clinet worked fine for 3 days.  now one of the win 7 machines with office 2010 is having the "can't open this item" when it gets new email.
We also have a XP machine with office 2003 exibiting the same issues.
It also can't display the emial in the reading pain.  If i go back two days to when it was working, it does open those e-mails and display them properly.  Just won't work on any new email.

I have rebuilt the domain profile on the computer from scratch.  repaired office, fixed the error logs, only one saying it could not index properly, nothing works.  

Can't find any thing on the KB that helps,  not sure if it is a exchange issue or a local profile issue.
Thanks for your help.
Avatar of setasoujiro
setasoujiro
Flag of Belgium image

did you try and remove the docs&settings folder ( because the domain name is the same) also try and delete their outlook profile , but be sure to delete/rename the username.domain folder as well from docs& settings , just to be sure.
and back up any data in there ofcourse
Avatar of carotomp
carotomp

ASKER

Follow up-  The Exchange server is running ForeFront virus protection.

Also, the user that use the XP machine logs into two different computers (one in another site) and the error is the same on both PCs.  They are both XP machines with office 2003.
check the things i said, because it is really not best practice to have a new domain with the same name...
i'm fairly sure that you are dealing with a corrupt outlook profile
Also, can they check the new mails properly using webmail?
if so then this really is an outlook issue
Yes, OWA works fine,  I have renamed, deleted and reconfigutred the outlook profile on the computers, Deleted the entire user profile, went into the Reg. and removed the reg keys that pointed to the profile and rebuilt it, still no joy.  I have not removed and reinstalled office yet, may try that.  
I'm assuming that if OWA works that the excahnge server is fine, there are no errors that i see on the win 7 box in the app log, it did have error that pointed to the indexing and MAPI issues, but i fixed them.  The XP client has MAPI issues as well.   I signed in to the computer with another domain user and set up their email and it worked fine.  Not sure why the Profile rebuilt would not fix the issue.  

I have not removed the entire Docs & settings folder (XP) or the Users Folder (WIN 7).  I can try on one of the computers tomorrow, it is strange that if that is the problem, that it would effect two computers in different site for the same user.

I will let you know tomorrow morn.  Any other suggestions?
ASKER CERTIFIED SOLUTION
Avatar of setasoujiro
setasoujiro
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Very strange..... When i got to the office the computers are now working.  Still can't get into the2 days of e-mails that are locked out, but everything sicne Friday morning is now working great.  I did restart the server, that was the only thing I did.  
Anyhow, it is working now.  Thanks for all your advice and help.