EV10: 2243 and 2270 errors - Could not scan user mailbox

Hi all,

for two mailboxes we have the same issue in our EV 10 server:

2243:

Could not scan user mailbox /o=XXXX/ou=First Administrative Group/cn=Recipients/cn=USERNAME, cannot list messages

2270:

A queued operation exceeded the retry count and has been discarded

m_pIBackgroundArchivingAgent->ProcessUserEx(Priority = "false",
  ReportingMode = "false",
  Run Now mode = "3",
  ContinuousMode = "true",
  RollOverLogFile = "false",
  NumMsgsToArchivePerPass = "0",
  legacyMessageStoreDn = "",
  legacyMailboxDn = "/o=XXXX/ou=First Administrative Group/cn=Recipients/cn=Username",
  adMessageStoreDn = "CN=DB22,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=XXXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mercuria,DC=met",
  adMailboxDn = "CN=Username,OU=GazAndPower,OU=Users,OU=GENEVA,OU=SWITZERLAND,OU=PRODUCTION,OU=XXXX,DC=XXXX,DC=met",
  NULL,
  ProcessDisabledSuspended = "false");

HRESULT: 0x800B0001

I ran the DTRACE for one user and, following this KB http://www.symantec.com/docs/TECH50185, I have some difficulty to understand what to do. The DTRACE return thos pathnames:

CFolderHelper::GFSFMO - Using folder pathname to open folder [@PR_IPM_SUBTREE_ENTRYID]

CFolderHelper::GFSFMO - Using folder pathname to open folder [@PR_IPM_SUBTREE_ENTRYIDInbox]

CFolderHelper::GFSFMO - Using folder pathname to open folder [@PR_IPM_SUBTREE_ENTRYIDInboxbbeau]

CFolderHelper::GFSFMO - Using folder pathname to open folder [@PR_IPM_SUBTREE_ENTRYIDInboxb]

Does it mean those folders are causing the problem? Do I need to remove them?

Let me know if you any experience with this kind of error.

Many thanks.

Renaud

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Yup that's exactly right I

Yup that's exactly right I had the same issue in my environment because somehow we had two \System Cleanup folders Removing one resolved the issue
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

1 Reply
Highlighted
Accepted Solution!

Yup that's exactly right I

Yup that's exactly right I had the same issue in my environment because somehow we had two \System Cleanup folders Removing one resolved the issue
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post