Knowledgebase

'Failed to Attach to machinename'

Return to Knowledgebase

'Failed to Attach to <machinename>'At the Control Component,  receipt of the messages:

"The service can't be reached from this host at this time E1817 or E1824" and…

"Failed to attach to <machinename>"

… indicate an inability to communicate with the OFM System Component.

These messages may result for several reasons, in descending order of likelihood:

1. Logon Account does not have Administrative privileges for System Component machine, therefore the System Component machine was unable to contact the Domain Controller. Log-on to the Control Component machine using an account that has administrative privileges for the System Component machine.

   
   

2. Remote Registry Service is not started on the machine with the OFM System Component.

   
   

3. Multiple NICs on the machine running the OFM System Component. OFM may not be using the internal IP Address. Try changing the Adapter order so the NIC with the Internal IP Address is at the top of the list. Here is the procedure:

   
   

• Right-click My Network Places, and then click Properties. The Network and Dial-up Connections window opens.

  
  

• Click Advanced and then click "Advanced Settings..." from the drop-down menu.

  
  

• Click "Adapters and Bindings" and then click on the network adapter whose IP Address is the INTERNAL address.

  
  

• Click the up arrow to move this NIC to the top of the list.

  
  

• Reboot the server to re-enumerate the NIC.

  
  

4. IRPStackSize setting is insufficient on the machine running the OFM System Component.

   
   

Check the System Event Log for:

Follow the instructions in the Microsoft article below to increase IRPStackSize so the error does not occur:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;q177078&