It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

When opening the ArchiveOne Admin console you receive error 'MSG0003'

  • Type: Knowledgebase
  • Date changed: 3 years ago
Solution #00007549


ArchiveOne Enterprise, all versions


When opening the ArchiveOne Admin console the following error is observed:

"MSG0003 - 'Failed to initialize connection to the Exchange Server. This may be due to your current NT user not being allowed to use ArchiveOne Enterprise (Policy). You do not have permission to log into the 'ArchiveOneAdmin' mailbox, or you are not a member of a group who has that permission."

This error occurs when any user attempts to open the ArchiveOne Admin console on the server. Note that for this specific error, opening the console on a different server (or a desktop) might work without any problem. 

Running the Admin console as another user does not resolve the error.


An additional registry key has been created (usually by a Windows Update) that refers to a different MAPI version. The ArchiveOne Admin console will try to connect with this non-Exchange version of MAPI which results in a connection failure. Removing the erroneous registry entry should resolve this specific error.


Note: This involves editing the Windows machine registry. Using the Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Barracuda cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. It is highly recommended that you create a backup of the registry before making any changes.

1. On the machine where you are running the Admin console, open the Registry Editor by running 'regedit'.

2. Browse to: 'HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Microsoft Outlook'.

3. Rename this key to: 'HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\C2CRenamed'.

4. Close the Registry Editor.

Now open the ArchiveOne Admin console to confirm the error is now resolved.

Link to This Page: