Loss of Exchange services due to MSExchangeDSAccess EventID 2103

I had a situation where an Exchange server completely stopped responding even though SMTP, POP3, etc. appeared to all be functional.  Of course, no email was being received and no users were able to check messages through any Exchange interface.  When I looked at the event log, MSExchangeDSAccess had logged EventID 2103:

Process MAD.EXE (PID=1111). All Global Catalog Servers in use are not responding:
server1.mydomain.local

Doing some research led me to determine that this was a Kerberos error.  On a hunch, I checked the clocks of the two systems (the Exchange server is also a domain controller) and determined that they had skewed to the point that each was rejecting the other.  I’m unsure how they got out of sync, I suspect one did an NTP sync and the other didn’t pick up on it.  I set the clock of the lagging server to be the same minute as the other one, rebooted, and presto, everything came back up.

Error moving Exchange mailbox

I was having an error moving a mailbox from Microsoft Exchange 5.5 to 2003:

Unable to move mailbox ‘MyMailbox’.
Error: The MAPI call failed.
MAPI or an unspecified service provider.
ID no: 80004005-0000-00000000

The Move wizard would go through most of the user’s messages before returning the error.  I checked the Active Directory account, and it was valid, with appropriate permissions for SELF.  The cause of the error was that the user’s mailbox size was larger than the storage limit.  I temporarily increased the storage limit, and the mailbox moved with no further difficulties.