PureMessage for Microsoft Exchange: error 0x80040e4d is displayed following installation

  • Article ID: 26548
  • Updated: 06 Oct 2008

Following the installation of PureMessage for Microsoft Exchange, when you try to open the PureMessage administration console, the following error message is displayed:

The administration console is unable to connect to the PureMessage service on the local server. The error code is: 0x80040e4d

If you try again you may see additional error messages.

This issue may be caused by lack of authentication between the domain controller and the SQL server.

For more information, a selection of articles are available on the Microsoft knowledgebase.

What to do

  1. At the computer on which the Microsoft SQL server is installed, open Windows Services.
  2. Right-click the relevant SQL server service, select 'Properties'.
  3. On the 'Log on' tab, check whether 'Local System Account' is selected or 'This account' is selected.
    • if 'Local System Account' is selected, continue with the procedure in the section below called 'Local system Account'.
    • if 'This account' is selected, make a note of the username, and continue with the procedure in the section below called 'This account'.

Local System Account

  1. Go to your domain controller, and from your Windows CD install ADSI Edit onto your domain controller. ADSI Edit can be found on the CD in 'Windows Support Tools'.
  2. It will install by default to C:\Program Files\Support Tools. Browse to this location, and double-click adsiedit.msc.
  3. From the tree that is displayed, select 'Domain', then double-click your domain to expand it.
  4. A number of values are displayed, open 'CN=Computers' and 'OU=Domain Controllers'
  5. Check through each of these lists until you find the name of the computer which is your SQL server. 
  6. When you locate it, right-click the SQL server and choose Properties.
  7. Scroll down to the 'servicePrincipalName' attribute and click the Edit button.
  8. In the editor window, check the list in the 'Values' field for the value
    • MSSQLSvc/<fully qualified SQL computer name>:<port number>
  9. If this value is not displayed there, type it into the 'Value to add' field, using the fully qualified SQL computer name and the default port number on the SQL server (details of how to find the port number are given below).

Restart the PureMessage console. This should now connect correctly.

NOTE: If the error message is still displayed when you try to start the administration console, the issue may have ocurred because the DNS entry is missing from the DNS server. You must check and fix the DNS configuration on the DNS server and/or the remote database computer.

This account

  1. Go to your domain controller, and use your Windows CD to install ADSI Edit onto your domain controller. ADSI Edit can be found on the CD in 'Windows Support Tools'.
  2. It will install by default to C:\Program Files\Support Tools>adsiedit.msc. Browse to this location, and double-click adsiedit.msc.
  3. From the tree that is displayed, select 'Domain', then double-click your domain to expand it.
  4. A number of values are displayed, open 'CN=Users'.
  5. Check through this list until you find the name of the user which you noted above.  
  6. When you locate it, right-click the user and choose 'Properties'.
  7. Scroll down to the 'servicePrincipalName' attribute and click the Edit button.
  8. In the editor window, check the list in the 'Values' field for the value
    • MSSQLSvc/<fully qualified SQL computer name>:<port number>
  9. If this value is not displayed there, type it into the 'Value to add' field, using the fully qualified SQL computer name and the default port number on the SQL server (details of how to find the port number are given below).

Restart the PureMessage console. This should now connect correctly.

NOTE: If the error message is still displayed when you try to start the administration console, the issue may have occurred because the DNS entry is missing from the DNS server. You must check and fix the DNS configuration on the DNS server and/or the remote database computer.

To find out the port number on SQL Server 2000/MSDE (on the SQL server PC)

  1. Run C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe
  2. Select your SQL server instance.
  3. Select 'TCP/IP' and click 'Properties'.
  4. Use the value displayed for the 'Default port'.

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

Rate this article

Very poor Excellent

Comments