Sophos

Online support

Product maintenance

Contact support

Support services

PureMessage for Microsoft Exchange: Error 0x80070005 The administration console is unable to connect to the local/remote server

Issue
When a user attempts to log on to the PureMessage Administration console, one of the following errors with error code 0x80070005 is returned:

The administration console is unable to connect to the local server
The administration console is unable to connect to the remote server 'servername'

Sophos Product and Version
PureMessage for Microsoft Exchange, version 3.0.x

Operating System
Windows

What to do

Solution 1

 

It is possible that the user is not included in the list of users authorised to manage PureMessage. The list of authorised users is contained in the Sophos PureMessage Administrators Active Directory (AD) user group which is created when PureMessage is installed. Check that the user is contained in the Sophos PureMessage Administrators group by following the instructions below.

  1. Open Active Directory Users and Computers.
  2. Double click on Sophos PureMessage Administrators.
  3. Select the Members tab.
  4. Check if the user's username is included in the list of members.
  5. If it is missing, add the username.

Note: If the problem persists after adding the new username, ensure that the AD changes have propagated to any other AD servers. This can be an issue where the console is not running on the same computer as the Exchange/PureMessage service.

 

Solution 2

  1. Run the following VBS script in a command window:

Dim oPMService
Set oPMService=CreateObject("SavexSrvc.SavexMgr")

  1. You should receive no error and the prompt should be returned to you. If there is an access problem, an error such as:

C:\>pmx-access.vbs
C:\pmx-access.vbs(2, 1)Microsoft VBScript runtime error: Permission denied: 'CreateObject'

would be displayed, indicating the expected access denied.

  1. To check the permissions, ensure that the following DCOM components have the correct settings:

    "PureMessage Service" - Security - Access Permissions: PMX_ADMIN
    "PureMessage Running Object Table" - Security - Access Permissions: PMX_ADMIN

    Once the group has been added, restart the Puremessage service.

Note: Where the PMX service is running on a Windows 2003 SP1 machine, ensure that the PMX_ADMIN group is added to the following PureMessage Service dcomcnfg entries:

'Launch and activation'

'Access Permissions!

For 'Local' and 'Remote'

 

If both of the above fail, stop the PureMessage service, restart IIS services, and start the PureMessage service.

If you need more information or guidance, then please contact technical support.