XADM: ISINTEG Reports Errors on IMC FoldersLast reviewed: April 15, 1997Article ID: Q152931 |
This information applies to:
SYMPTOMSAfter you run the ISINTEG utility in FIX mode, you might see errors for the Microsoft Exchange Internet Mail Connector (IMC), or any other connector based on the Microsoft Exchange Development Kit (EDK), similar to the following:
Error: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": IPM subtree missing. Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": IPM Subtree not in count database Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": Sentmail not in count database Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": Wastebasket not in count database Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": Finder not in count database Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": Views not in count database Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": Common Views not in count database Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": Schedule not in count database Warning: Mailbox 3 (Fid=0001-000000000160) "Mailbox - /O=org/OU=dept1/CN=CONFIGURATION/CN=CONNECTIONS/CN=INTERNET MAIL CONNECTOR (TI486)": Shortcuts not in count database CAUSEThe ISINTEG utility will not automatically recreate or restore folders used by the IMC or any other connector based on the EDK.
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |