An attempt to backup/restore an Exchange Database with Granular Recovery may fail with MAPI logon failures (x80040115, MAPI error 80040115) on Windows 2008.

Article:TECH87068  |  Created: 2008-01-14  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH87068
Article Type
Technical Solution

Product(s)

Environment

Issue



An attempt to backup/restore an Exchange Database with Granular Recovery may fail with MAPI logon failures (x80040115, MAPI error 80040115) on Windows 2008.


Error



MAPI_FAILED - return code 80040115


Solution



When attempting to run a GRT backup of the Information Store to tape for Exchange 2007 running on a Windows 2008 server  the job fails with the above error.

The same job when targeted to backup to disk completes successfully but when trying to run a GRT restore from the successful backup set the job fails with the following error:

-------------------------------------------------------------------------------------------------------------------------------------------------------------
Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again
--------------------------------------------------------------------------------------------------------------------------------------------------------------

Another symptom can be seen in remsrv log (Install_Path\Veritas\NetBackup\logs\beds\*-remsrvMMDDYY) during restores.

 

[4868] 03/04/10 10:58:19 HrCreateProfile():     Profile 'Backup Exec Exchange Agent 04cfe878.00001304' successfully created
 
[4868] 03/04/10 10:58:19 ConfigureMsgService() MAPI_FAILED - return code 80040115. user <nbu_mailbox_on_exchange>
 


The above problem occurs as a result of Windows 2008 using Internet Protocol version 6 (IPv6) as a preferred protocol over Internet Protocol version4 (IPv4).

The Exchange 2007 application while running on a Windows 2008 machine listens on the usual ports 6001, 6002 and 6004 on the IPv4 address, but listens only on ports 6001 and 6002 on its IPv6 address. The DSProxy service (port 6004) is NOT listening on the IPv6 stack.

Because Windows 2008 prefers IPv6 over IPv4, it talks to itself over IPv6. So when the RPC-over-HTTP Proxy tries to connect a user session to port 6004 on the same server, it tries to connect to :::1:6004 and NOT to 127.0.0.1:6004. Because the server is not listening to port 6004 on the IPv6 stack, the connection fails.

For more information about this problem please refer the following article:
http://technet.microsoft.com/en-us/library/cc671176(EXCHG.80).aspx

Workaround:

To resolve the issue, perform one of the following procedures on the Client Access Server. The procedure to implement the workaround depends on whether the Exchange topology is running the Client Access Server role and Mailbox server role on the same Exchange server or on different Exchange servers.

For a single-server topology where the Client Access server role is running on the same Exchange server as the Mailbox server role.
1. Open the hosts file located at %SystemRoot%\system32\drivers\etc\ by using an editor such as Notepad.
%SystemRoot% refers to the drive where the Windows system files are located.

2.  Comment out the line that references the IPv6 address.
# :::1    localhost

3. Add the following lines into the file:
127.0.0.1                    hostname of the computer              FQDN of the computer
<actual IPv4 address>   hostname of the computer             FQDN of the computer

3. Save the changes made to the file and restart the Netbackup Client Service on the Exchange server.

4. Run an Information Store backup/restore and verify the results.

For a multiple-server topology where the Client Access Server role is not running on the same Exchange server as the Mailbox server role

The following changes need to be made on the Client Access Server in the multiple server topology:
1. Under Network Connections, select the network adapter, and then click Properties.

2. In the properties window, uncheck the check box for Internet Protocol Version 6 (IPv6).

Note: Clearing this check box causes the RPCProxy component on the Client Access Server to use TCP/IPv4 to talk to the DSProxy component on the Mailbox server.  

3. Click on the Start menu, and then click Run. Type regedit in the Open box.

4. Using Registry Editor, locate the following registry key:
HKEY_Local_Machine\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

5. Right-click the Parameters key, click New, and then click DWORD (32-bit) Value. For the key, add the following values:
Name: Disabled Components
Data: 0xffffffff

6. Restart the Client Access Server.


7. Run an Information Store backup/restore and verify the results.

The above error message may continue to occur even after having made the changes mentioned above if :
A.) Exchange 2007  is installed on a Windows 2008 machine
AND
B) In the resource order for the backup selection list Information Store is not the first resource to be backed up
AND
C) Backup job is targeted to tape device

Resolution:
To resolve the issue edit the backup selection list such that the Microsoft Information Store is the first resource to be backed up followed by the other local resources on the server.
 

References
http://support.microsoft.com/kb/929852

How to disable certain Internet Protocol version 6 (IPv6) components in Windows Vista, Windows 7 and Windows Server 2008



 




Legacy ID



311611


Article URL http://www.symantec.com/docs/TECH87068


Terms of use for this information are found in Legal Notices