What a BUG ! Lot of messages got corrupted after .pst import to Exchange 2003 via Outlook 2000. Messages can't be viewable in any way. The subject is fine but messages can't be displayed and I get an error "Can't open this item. The operation failed" Message(s) displays fine within pst file, only after importing it via Outlook 2000 it can't be displayed. Looks like Exchange 2003 does not recognize certain format of Outlook 2000. Is there anything I can do to fix Exchange 2003. Are trhere any fixes or patches? NEED HELP because some pst messages have been moved to a mailbox and can't displayed and there is no backup pst file to restore these messages from. Please, HELP
Where were these .PST files imported from into Outlook? Are all the users have this issue?
I am not sure what is causing this ... but check the ISINTEG and ESEUTIL command line tools... these are used to check, defrag, repair and so on of Exchange Server Database.
Try stopping and restarting all the services. Did you restart the server?
Always have a backup before performing these kinds of tasks - remember.
All messages were pulled by MS Outlook 2000 sr3 from Exchange 5.5 POP3 accounts and are residing on each workstation as .pst file. Most pst messages were moved or copied to MS Exchange 2003 mailboxes using MS Outlook 2000 and lot of messages will not display on all workstations. I even tried copying same message that displays fine from pst file to different mailboxes on different workstations and same thing happens. Some users moved their messages from pst files to their mailboxes and about 30% messages will not open. At the same time Backup Exec fails to backup these messages saying that they are corrupted. I ran eseutil.exe but no luck. I did not try isinteg.exe yet. There must be some sort of incompatibility between MS Outlook 2000 and MS Exchange 2003. I never had this problem with other Exchange versions (5.5/2000). I've seen this issue on other posts but so far I have not seen a solution to this. I will appreciate any tips to help to recover these messages.
RE: Lot of messages got corrupted after .pst import to ... - 29.Apr.2004 11:47:00 PM
Guest
I have the exact same ploblem after implementing an Exchange 2003 Server. I have approx. 15000 of 38000 piece of mail that have this problem. They are all HTML emails. I can still open them in the old PST's but when I drag these message to the exchange mailbox it then become corrupt. Scanpst does not pick up any issues with the old PST's.
Patiently waiting for a solution. Someone please post if they find one.
How are you guys creating the PST file. We just migrated 50 mailboxes from 5.5 to 2003 and I used exmerge to do the movement and it worked great. I didn't get 1 piece of corrupted mail and some of the users had over a gig of mail.
RE: Lot of messages got corrupted after .pst import to ... - 14.May2004 8:04:00 PM
Guest
Same problem here. I exported from a Linux Qmail box.
Same exact issues as stated above. So it's not just a MS to MS issue. Exchange is messing up some emails (seems to be HTTP specifically) on import. My guess is it is somehow losing or pulling in incorrect PERMISSIONS to the email.
nothing I have tried will fix the broken emails. And whats worse is everyone has already manually imported their PST into exchange, leaving the old PST file empty. So now I am trying to find a recovery util to restore those PST's.
A fix from MS would be a much faster and cheaper solution though.
I can't believe this problem was not seen in beta testing for SBS2003, especially now considering I see clearly I am not the only one with this problem.
I though I was stuck and alone with this being a Linux tranfser in my case. Whats also bad is i POP'd the old server on the import into the new exchange box, also emptying the mailbox as it went so I cant even go back that route. And I am unfamiliar with that old system and have no idea how or even if i can restore a backup from another time to rebuild it.
Posts: 3
Joined: 14.May2004
From: Springfield Va
Status: offline
Same problem here. I exported from a Linux Qmail box.
Same exact issues as stated above. So it's not just a MS to MS issue. Exchange is messing up some emails (seems to be HTTP specifically) on import. My guess is it is somehow losing or pulling in incorrect PERMISSIONS to the email.
nothing I have tried will fix the broken emails. And whats worse is everyone has already manually imported their PST into exchange, leaving the old PST file empty. So now I am trying to find a recovery util to restore those PST's.
A fix from MS would be a much faster and cheaper solution though.
I can't believe this problem was not seen in beta testing for SBS2003, especially now considering I see clearly I am not the only one with this problem.
I though I was stuck and alone with this being a Linux tranfser in my case. Whats also bad is i POP'd the old server on the import into the new exchange box, also emptying the mailbox as it went so I cant even go back that route. And I am unfamiliar with that old system and have no idea how or even if i can restore a backup from another time to rebuild it.
Posts: 3
Joined: 14.May2004
From: Springfield Va
Status: offline
Same problem here. I exported from a Linux Qmail box.
Same exact issues as stated above. So it's not just a MS to MS issue. Exchange is messing up some emails (seems to be HTTP specifically) on import. My guess is it is somehow losing or pulling in incorrect PERMISSIONS to the email.
nothing I have tried will fix the broken emails. And whats worse is everyone has already manually imported their PST into exchange, leaving the old PST file empty. So now I am trying to find a recovery util to restore those PST's.
A fix from MS would be a much faster and cheaper solution though.
I can't believe this problem was not seen in beta testing for SBS2003, especially now considering I see clearly I am not the only one with this problem.
I though I was stuck and alone with this being a Linux tranfser in my case. Whats also bad is i POP'd the old server on the import into the new exchange box, also emptying the mailbox as it went so I cant even go back that route. And I am unfamiliar with that old system and have no idea how or even if i can restore a backup from another time to rebuild it.
Posts: 3
Joined: 14.May2004
From: Springfield Va
Status: offline
sorry, dont know how that posted 3 times. I do not recall sending it 3 times.
Does anyone with MS ties read this site? MS tech site seems to be missing any kind of talk about this problem.
But then again I've also seen MS's website return ZERO documents for a search of the word "error" before, so i never can trust the searching is complete any more.
RE: Lot of messages got corrupted after .pst import to ... - 1.Jun.2004 5:24:00 PM
Guest
I'm having this issue as well.
Employees in my office have started reporting that they cannot read emails from external sources prior to our switch from Qmail to Exchange 2003.
I tried accessing the email using exchange/exchange in IE, and I still cannot gain access to these emails.
Another test I tried was re-importing email from the old pst file into a test folder within the user's Exchange folder and IT WAS SUCCESSFUL.
The same emails that were imported from the same pst months ago when we changed to Exchange 2003 are now accessible within the test folder. I asked the user to keep an eye on the folder and to try accessing the email now and again to see if and when it prevents access again. Time will tell...
Based on this, I would recommend re-importing from the original pst file - but for those of you with large offices, I'd hold off until I can confirm that it won't block access to these emails again in a week or two.
RE: Lot of messages got corrupted after .pst import to ... - 9.Jun.2004 12:39:00 PM
Guest
This is typically seen in conjunction with Exchange aware virus protection. It's been seen the most in conjunction with Symantec. Apply SP1 and it should be fixed.
Posts: 67
Joined: 9.Jul.2004
From: London
Status: offline
We have just completed a company merger and merged email systems from Exchange 5.5 (50 user) and Mercury/Pegasus (200 user) onto a new Exchange 2003 system.
For the Exchange 5.5 users, I used MailMig and did not experience this problem.
For the Pegasus users, we used Transcend Migrator v3.3 to convert Pegasus Mail to a .PST and then import that into the Exchange mailbox. We did notice this issue (it appeared to affect HTML formatted emails with attachments) and changed our procedure to;
Convert Pegasus folder to PST Run ScanPST against the PST on a workstation with Outlook 2003 installed using ScanPST (The 42Kb 11.0.5510.0 version installed into "C:\Program Files\Common Files\System\MSMAPI\1033\SCANPST.EXE" on the Workstation). The version of ScanPST was important. The PST was then opened and the Pegasus folders "dragged" to the mailbox rather than doing a File/Import.
This process appears to have eliminated the problem.
Posts: 23
Joined: 20.Jul.2004
From: Bedford UK
Status: offline
I have had this problem on 2 different sites where we have recently migrated from pop3 based systems with each user having individual PST files. I must admit i had thought it was a symantec related problem, but have not yet had a chance to properly look into it. I am going to both sites in the next couple of days and will apply service pack 1 .. then we will see what the backup logs say.
It's a really annoying problem as it means the veritas reports that the backups failed even if only 1 message is corrupted so the clients start to panic.
Posts: 1
Joined: 5.Jan.2005
From: Oslo Norway
Status: offline
I had a MS outlook vs.11.0.5510.0 on my c: drive. Continously backing up the pst file on another disk. Then C:/ crashed, and I reinstalled a newer version of MS office. And it now seems that the old pst files are not compatible with the new version. I don't have the old Outlook version anymore. Anyway to import the mail into my newer versjon of Microsoft Outlook? Please help!
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Server Security >> Lot of messages got corrupted after .pst import to Exchange 2003 
Lot of messages got corrupted after .pst import to Exch... - 
![[Mad]](/image/smiles/mad.gif)
RE: Lot of messages got corrupted after .pst import to ... - ![[Frown]](/image/smiles/frown.gif)
RE: Lot of messages got corrupted after .pst import to ... - 
RE: Lot of messages got corrupted after .pst import to ... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
