Follow

arcserve-KB : Microsoft Exchange Server - Document Level browse and backup does not work with MS Exchange Server 2007 installed on Windows 2008

Last Update: 2016-11-23 15:28:48 UTC

CA ARCserve Backup for Windows ENGLISH: 12.0
CA ARCserve Backup for Windows ENGLISH: 12.0
CA ARCserve Backup for Windows ENGLISH: 12.0
Last Modified Date:    01/22/2009
Document ID:    TEC465897

Tech Document
Title:  Microsoft Exchange Server - Document Level browse and backup does not work with MS Exchange Server 2007 installed on Windows 2008

Description:

This document provides recommendations on resolving Exchange Document Level browsing and backup problems with Exchange 2007 installed on Windows 2008+SP1

IMPORTANT:

This article contains information about modifying the registry.

Before you modify the registry, make sure to create a back up of the registry and ensure that you understand how to restore the registry if a problem may occur.

For more information about how to back up, restore, and edit the registry, please review the relevant Microsoft Knowledge Base articles on support.microsoft.com.

Solution:

Please follow the recommendations below:

  1. Document Level Agent Browsing and Backup using Exchange 2007 SP1 on a Windows 2008 SP1 server is only supported with ARCserve r12.0 SP1 and higher. It is not supported with ARCserve r12.0 with no service pack.
  2. The Messaging API (MAPI) Client and Collaboration Data Objects (CDO) must be at a minimum level of Version 1.2.1 (8022.0). Earlier versions of the MAPI CDO are not supported.
  3. Verify that the user account designated as the Document Level backup accounts meets all of the prerequisites described in Technical document TEC436398
  4. There are two methods for resolving this problem. Method 1 involves editing the hosts file for windows so that the lines in the host file are in the exact order shown. Method 2 involves disabling IPv6. Either Method 1 or Method 2 must be used.

    Method 1

    1. Open the hosts file located at %SystemRoot%\system32\drivers\etc\ by using an editor such as Notepad
    2. Search for the line that contains the term '::1' and comment out the line by putting a number sign (#) at the beginning
    3. Add the following two lines to provide the TCP/IPv4 address, hostname, and FQDN name for the Exchange 2007 server
      <TCP/IPv4 address> <host name of the computer>
      <TCP/IPv4 address> <FQDN of the computer>
    4. Click Save, and then close the file
      Example of what the host file should look like after making above changes:

      127.0.0.1 localhost
      #::1 localhost
      192.168.1.100 EX2007Server
      192.168.1.100 EX2007Server.ca.com

    Method 2

    1. In the Network Connections folder, obtain properties on all of your connections and adapters and clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under This connection uses the following items.
    2. This method disables IPv6 on your LAN interfaces and connections, but does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface.
    3. Add the following registry value (DWORD 32 Bit) set to 0xFFFFFFFF:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
      This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface.

      You must restart the computer for this registry value to take effect.

    For more information please see the following links:
    http://technet.microsoft.com/en-us/library/cc671176(EXCHG.80).aspx
    http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx

  5. The account used for security [Option A] must be THE Domain Administrator account in the form <domain name>\administrator, or [Option B] a Domain Administrator equivalent account may be used provided the User Access Control feature is turned off on the Exchange Server. The UAC feature restricts access for admin group accounts.

    For Option A you may use THE <domain name>\administrator account. In order to use this option please follow the procedure:

    1. Make sure the ARCserve Manager is CLOSED on the Backup Server.
    2. On the Exchange Server, or on all Exchange Servers in an Exchange Cluster, open Windows services applet (services.msc) and C. RESTART the CA ARCserve Universal Agent service.
    3. On the Backup Server, open the ARCserve Manager.
    4. In the Backup Manager, on the Source Tab expand 'Windows Systems'.
    5. Right-click the Exchange Server and select Security and then enter the <domain name>\administrator account and the correct password and click OK.
    6. Expand the Exchange server and Right-click on the Exchange Document Level and select Security and then enter the <domain name>\administrator account and the correct password and click OK.
    7. N ow you should be able to browse the Exchange Document Level.
    8. When running a backup job, make sure both the Exchange Server and the Exchange Document Level use the <domain name>\administrator account for security in the Security and Agents window when packaging the job.
    For Option B you may use any Domain Administrator equivalent with full Domain Administrator privileges but will require the following workaround. The workaround for this option is to turn off User Access Control on the Exchange server if has not already been done by following the steps below.
    1. Click Start, and then click Control Panel .
    2. In Control Panel, click User Accounts.
    3. In the User Accounts window, click User Accounts.
    4. In the User Accounts tasks window, click Turn User Account Control on or off.
    5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
    6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.
    7. Click Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window.

      For more information please see the following link:
      http://technet.microsoft.com/en-us/library/cc709691.aspx

NOTE: If this problem is not resolve with above recommendations it may indicate a more serious problem requiring CA Technical Support Assistance

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments