Issue with connecting a mail box to be exported to a PST file
Hello Everyone, I spent some time trying to export a mailbox that I had to reconnect to a profile. I found that after connecting the mailbox to a AD user, I then needed to run the clean-mailboxdatabase command. Then I was able to export the mailbox to a PST file Here was the error I was getting before I did the clean up. Couldn't connect to the source mailbox. + CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemoteTransientException + FullyQualifiedErrorId : 106E5EF6,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportReques I just wanted to post this and see if anyone else had this issue. Exchange INfo Version: 14.2 (build 247.5) Single server install. Brett
August 13th, 2012 1:58pm

Yes actually my last export attempt I experienced it, after you reconnect you can't perform any tasks against it, log into owa it will report as Microsoft.Exchange.Data.Storage.AccountDisabledException until you run a post clean-mailboxdatabase again. I'm pretty sure it didnt use to be the case before and worked right away when reconnecting. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2012 2:08pm

Microsoft.Exchange.Data.Storage.AccountDisabledException until you run a post clean-mailboxdatabase again. That was fixed in RU3. See: You cannot access a mailbox for several hours after you disconnect and then reconnect the mailbox in an Exchange Server 2010 SP2 environmentMartina Miskovic
August 13th, 2012 2:12pm

Microsoft.Exchange.Data.Storage.AccountDisabledException until you run a post clean-mailboxdatabase again. That was fixed in RU3. See: You cannot access a mailbox for several hours after you disconnect and then reconnect the mailbox in an Exchange Server 2010 SP2 environmentMartina Miskovic
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2012 2:20pm

That was the first article I checked and assumed it was dscache as well when I ran into it last month but no luck. The systems were on RU3.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
August 13th, 2012 2:24pm

Interesting! Guess that it always a good idea to run Clean-Mailboxdatabase regardless of Exchange version (2007/2010) and SP+RU installed.Martina Miskovic
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2012 2:27pm

Ahhh darnit I forgot to update it on my tools box!James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
August 13th, 2012 2:29pm

Over the next 2 weeks we will be upgrading to RU3 on the servers. Brett
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2012 2:30pm

Hmm it still appears to be the case for me running on the server itself, I think I tested on the server back then as well just to eliminate if it was an issue on the tools box. Just verified all systems are on sp2 ru3 just as sanity check. See if you can reproduce the issue. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
August 13th, 2012 2:57pm

Hi, Tested it, I was able to log on right away. I must add that that my test was made in a small lab environment so no AD Replication to think of here.Martina Miskovic
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2012 3:06pm

Thanks for checking, looks like I need to do some more digging on my issue.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
August 13th, 2012 4:01pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics