Tips: What are common errors when Folder GUID permissions are insufficient?

Here are the most common errors and what they actually mean in "plain English":

1. MAPI_E_NO_ACCESS (0x80070005)

• What it means: This is the most common "Access Denied" error. It indicates that the MAPI subsystem successfully found the folder GUID, but the account running the scan does not have the rights to open it.
• Common Cause: The scanning account (user or service account) lacks "Read" or "Full Access" permissions on that specific folder.

2. MAPI_E_NOT_FOUND (0x8004010F)

• What it means: The Agent is asking for a specific GUID, but the mailbox provider says, "I don't see anything with that ID here."
• Why it's a permission issue: While this sounds like a "missing file" error, it often happens because the scanning account lacks "Folder Visible" permissions on the parent folder. If the agent can't see the parent, it is blocked from even "seeing" that the child GUID exists.

3. MAPI_E_NOT_INITIALIZED

• What it means: The Agent tried to talk to Outlook to check the GUID, but the conversation never started.
• Common Cause: This often points to a Bitness Mismatch or the Outlook profile not being loaded. If the Agent can't initialize the MAPI session, it can't verify permissions or GUIDs.

4. MAPI_E_FAILONEPROVIDER

• What it means: This usually occurs when scanning multiple GUIDs or accounts. It means one of the "providers" (like an attached PST or a shared mailbox) rejected the connection.
• Common Cause: This frequently happens when a user has a Shared Mailbox attached to their profile, but the Spirion Agent only has permission to scan the primary mailbox.

5. "0 Items Scanned" (with no explicit error)

• What it means: The scan completes successfully and "Green," but shows that nothing was actually searched.
• Why it happens: If the GUIDs provided are incorrect or the account has zero visibility into those folders, the Agent may simply conclude there is "nothing to do" and finish the task without throwing a hard error.

6. MAPI_E_NETWORK_ERROR

• What it means: The Agent tried to verify permissions against the Exchange server, but the connection timed out.
• Common Cause: This often happens when trying to scan Online (Non-Cached) folders over a slow VPN or when the Exchange server is under heavy load.

How to distinguish these in the Logs

When you open the IdentityFinder.log on the endpoint, look for the hexadecimal codes. They are the "smoking gun" for permission issues:

Troubleshooting Tip

• If you see these errors, the fastest way to confirm if it's a Spirion problem or an Exchange problem is to log into that machine as the scanning account and try to open those folders manually in Outlook.
• If the folders don't appear or won't open in the Outlook UI, Spirion will never be able to scan them.

Summary: Most GUID permission errors boil down to MAPI_E_NO_ACCESS (you can see it but can't enter) or MAPI_E_NOT_FOUND (you don't even have permission to know it exists). Always check the Bitness and Folder Visible rights first.