Good to know about the former. On the possiblity of replication issues, it sure doesn't seem like it. "Repadmin /showrepl" is clean on both DCs, dcdiag shows no errors on both DCs, and the event logs are also free of errors.
Perhaps the replication issue is the quick trigger finger on the part of the admin. Maybe I'm expecting things to be done immediately, and need to wait a minute or two after most procedures. On Wed, Mar 23, 2011 at 10:26 AM, Michael B. Smith <[email protected]>wrote: > That is correct. Mailboxes are not actually removed from the source > mailbox database until “deleted mailbox retention” has expired. > > > > This sounds amazingly like you are having AD replication issues. > > > > Regards, > > > > Michael B. Smith > > Consultant and Exchange MVP > > http://TheEssentialExchange.com <http://theessentialexchange.com/> > > > > *From:* Richard Stovall [mailto:[email protected]] > *Sent:* Wednesday, March 23, 2011 10:08 AM > > *To:* MS-Exchange Admin Issues > *Subject:* Re: "MSExchange Assistants" Events 9017, 9042 and 9025 > > > > Well, now things are interesting (and a bit weird). > > > > I moved the mailbox to a second Exchange 2010 mailbox database created for > archive mailboxes, and was then able to open it in OWA. For additional > giggles, I moved it back to the original database and initial attempts to > open it in OWA generated a Microsoft.Mapi.MapiExceptionMailboxSoftDeleted > exception. (I've got the full details if necessary.) The mailbox is also > now visible in "Disconnected Mailbox." After waiting a bit, subsequent > attempts to open it in OWA work just fine. It is also accessible via > Outlook 2007. All of this despite the fact that it shows as disconnected. > > > > It's like a second, viable mailbox was created in the move to the second > Exchange 2010 database, and the original one is orphaned awaiting deletion. > > > > I'll hold off doing anything else in case the current state lends itself to > figuring out what went wrong initially, or any other useful diagnostics. > > > > Thanks for the help, > > RS > > > > > > On Wed, Mar 23, 2011 at 9:15 AM, Missy Koslosky <[email protected]> > wrote: > > I would try moving the mailbox to a different database for giggles. > > > > On Mar 23, 2011, at 8:43 AM, "Richard Stovall" <[email protected]> wrote: > > Good morning, > > > > Yes, the move request reappeared after I restored the account, and the > status was completed. I cleared the request last night, however, thinking > that might help. Perhaps I should have waited. > > > > This morning the status is the same with both OWA and the 9042 warning in > the application log. > > On Wed, Mar 23, 2011 at 8:24 AM, Missy Koslosky <[email protected]> > wrote: > > Can you still see the move request in EMC? > > > > Missy > > > > On Mar 22, 2011, at 9:25 PM, "Richard Stovall" <[email protected]> wrote: > > Thanks. That didn't seem to do anything. The warning was still present > in the Application Log, and the mailbox did not appear in the "Disconnected > Mailbox" area of EMC. > > > > When I upgraded the domain to 2008 R2 I enabled the AD Recycle bin, so I > went and restored the user. It now shows up under Mailbox in EMC with a > Recipient Type of User Mailbox. For grins, I tried to connect to OWA and > got the same error as the other day. "You weren't able to sign in because > the mailbox is being moved. You won't be able to access it until the move > is complete." > > > > I'll leave this as is overnight and see tomorrow if the app log warning is > still there and if the account can login to OWA. > > > > Strange days... > > > > > > On Tue, Mar 22, 2011 at 7:38 PM, Michael B. Smith <[email protected]> > wrote: > > Take a look at “clean-mailboxdatabase”. > > > > Regards, > > > > Michael B. Smith > > Consultant and Exchange MVP > > http://TheEssentialExchange.com <http://theessentialexchange.com/> > > > > *From:* Richard Stovall [mailto:[email protected]] > *Sent:* Tuesday, March 22, 2011 6:58 PM > *To:* MS-Exchange Admin Issues > *Subject:* "MSExchange Assistants" Events 9017, 9042 and 9025 > > > > I installed Exchange 2010 into our existing 2003 organization last weekend. > I've got a strange error in the Application log that I don't know how to > deal with. > > > > When I first got 2010 up and running, I created several users with > mailboxes on the 2003 server to have some accounts and mailboxes for > testing. The first mailbox I moved from the 2003 server to 2010 appeared to > move OK, but I was never able to access the mailbox. Outlook threw all > kinds of errors and OWA would not access the mailbox and gave a message to > the effect that it wasn't available because it was still being moved, which > was inaccurate. I fought with it for a while, but would up deleting the > user and mailbox and working with another of the test users. Everything has > gone fine since the first one, and now I've got 2 production user mailboxes > on 2010. > > > > The warning in the App log I'm writing about refers back to the deleted > user/mailbox, and is in event 9042. The user is specified in 9025, the > third of the events. Here they are, in all their delicious glory. > > > > 1st - 9017 - Information > > Service MSExchangeMailboxAssistants. Calendar Sync Assistant for database > Mailbox Database 2019011809 (f47f1a87-8e13-4e83-a9a4-4f1a666fccad) is > entering a work cycle. There are 1 mailboxes on this database. > > > > 2nd - 9042 - Warning > > Service MSExchangeMailboxAssistants. Calendar Sync Assistant for database > Mailbox Database 2019011809 (f47f1a87-8e13-4e83-a9a4-4f1a666fccad) is > exiting a work cycle. No mailboxes were successfully processed. 1 mailboxes > were skipped due to errors. There are 0 mailboxes in this database. > > > > 3rd - 9025 - Information > > Service MSExchangeMailboxAssistants. Calendar Sync Assistant skipped 1 > mailboxes on database Mailbox Database 2019011809 > (f47f1a87-8e13-4e83-a9a4-4f1a666fccad). Mailboxes: > > Test User(cbaa8fc4-0fb6-4863-8b06-5858c876523d) > > > > "Test User" is the display name of the affected account. > > > > I thought about creating a new DB, moving the live mailboxes, and deleting > the current DB, but it seems like a lot of work when there is probably some > cleanup mechanism available. If it matters, I deleted the user/mailbox 3 > days ago using the EMC GUI. > > > > Any thoughts about how to fix this are appreciated. (Any thoughts about > the mailbox move weirdness are welcome too.) > > > > Thanks, > RS > > > > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
