An attempt to a restore Mailbox/Public Folder on an Exchange 2007 server running on a Windows 2008 from a Granular Recovery Technology (GRT) enabled Backup-To-Disk set fails with the error "Unable to attach to a resource."

Article:TECH86155  |  Created: 2009-01-03  |  Updated: 2012-04-23  |  Article URL http://www.symantec.com/docs/TECH86155
Article Type
Technical Solution

Product(s)

Languages

Problem



An attempt to a restore Mailbox/Public Folder on an Exchange 2007 server running on a Windows 2008 from a Granular Recovery Technology (GRT) enabled Backup-To-Disk set fails with the error "Unable to attach to a resource."


Error



Error in Job Log :

Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.
If the Information Store backup job is targeted to tape it fails with the following error:
Backup- \\Exchange2007\Microsoft Information Store\First Storage Group 
V-79-57344-33928 - Access Denied. Cannot backup directory ?Mailbox Database and its subdirectories. 

Error in Debug Log :

Example debug from a Single Exchange 2007 Server Topology :

Logon: m_lpMAPISession->Logon returned 80040115
m2chgdir: Logon failed without Last error set
MB2_Chgdir:Logon returned e000fea9
 
If the Information Store backup job is targeted to a Disk it fails with the following error(Remote Agent debug log):
 [BESocket]           - BETCPConnection::CreateConnectionFromHostAndPort: Remote Host: "EXCHANGESERVER": There were no addresses returned, belonging to family: IPv6
 [BESocket]           - BETCPConnection::CreateConnectionFromHostAndPort: Could not create a connection to "EXCHANGESERVER" because attempts with both IPv4 and IPv6 protocols failed
 [nrds]               - Could not create a BETCPConnection object from address: EXCHANGESERVER = error=An error occurred during a socket connect operation: Error Code: 10061, System Error Message: No connection could be made because the target machine actively refused it.
 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: connect to target=EXCHANGESERVER port=6101 failed
 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Retrying in 60 seconds

 


Cause



  • 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.

NOTE:
           This issue can also occur if the Media Server is on a Windows 2008 server and Exchange 2007 is installed on a Windows 2003 64bit.
 


Solution



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
    127.0.0.1                   FQDN of the computer actual
    IPv4 address    hostname of the computer actual
    IPv4 address    FQDN of the computer
     
  4. Save the changes made to the file and restart the Backup Exec services on the Exchange server.
     
  5. Run an Information Store backup/restore and verify the results.
NOTE:
If restore fails even after following above steps,disable IPv6 completely on exchange server if there is no other application using it.
 
For a multiple-server topology where the Client Access server role is not running on the same Exchange server as the Mailbox server role. So 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 will cause RPCProxy component on the CAS Server to use IPv4 to talk to the DSProxy component on the Mailbox Server. 
  1. Click on the Start menu, and then click Run. Type regedit in the Open box.
     
  2. 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.

  1. Right-click the Parameters key, click New, and then click DWORD (32-bit) Value. For the key, add the following values: Name: DisabledComponents Data: 0xffffffff 
     
  2. Restart the Client Access server (CAS).
     
  3. Run an Information Store backup/restore and verify the results.
NOTE:
The above issue will also occur if the Backup Exec is installed on Windows 2008 and the host file is modified on the Exchange Server only as per above steps.To resolve this , the host file need to be modified on the Media Server as well if its a Windows 2008 server as per the above steps.

 

Supplemental Materials

SourceETrack
Value1317846
Description

EXCH2K7: GRT Tape backup or B2D restores for E2K7 on Windows 2008 machines fail with MAPI errors.

SourceError Code
Value0xe000848c
Description

Final error: - 0xe000848c Unable to attach to a resource.

SourceUMI
ValueV-79-57344-33932
Description

Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again. If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource

Related Articles



Legacy ID



306689


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


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support