Active Directory adapter for Atrium Orchestrator fails with error 267

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Atrium Orchestrator Application Adapters


    COMPONENT:

    BMC Atrium Orchestrator Application Adapters


    APPLIES TO:

    BMC Atrium Orchestrator Content 20.xx.xx



    PROBLEM:

    The Microsoft Active Directory (AD) adapter for BMC Atrium Orchestrator is unable to create or get user information. It returns this adapter response:

    <output>
        <line index="1">Copyright 2010 BMC Software Ltd, Version: 1.5  </line>
        <line index="2">Connecting to remote service...</line>
        <line index="3">InstallAndStartRemoteService(): StartService() fails</line>
        <line index="4">The service did not start due to a logon failure.</line>
        <line index="5">InstallAndStartRemoteService(): StartService() fails</line>
        <line index="6">The service did not start due to a logon failure.</line>
        <line index="7">InstallAndStartRemoteService(): StartService() fails</line>
        <line index="8">The service did not start due to a logon failure.</line>
        <line index="9">Connected to remote host.</line>
        <line index="10">Remote command failed to start. Returned error code is 267(0x407053)</line>
        <line index="11">StandartExecution(): SayLaunchExecutable() 0xFFFFFFFF</line>
    </output>


    CAUSE:

    The adapter is missing one or more prerequisites, like an valid user account or access to the files it needs to run commands.


    SOLUTION:

    Verify that you have all of these following prerequisites:

       
    1. The server with the BAO peer running the adapter and the server on which the adapter will execute commands must be on the same domain.
    2.  
    3. The server with the BAO peer must be using a supported version of Microsoft Windows.
    4.  
    5. On peers with the AD adapter, make sure the peer services are running as a domain admin user. For more details please see https://docs.bmc.com/docs/display/public/baoc201502/Post-installation+tasks+for+the+AD+adapter or this equivalent page in your version of the adapter.
    6.  
    7. The user defined in the adapter configuration must have the "Log in as a service" right on the target machine. For more details please see the AC documentation at https://technet.microsoft.com/en-us/library/cc739424%28v=ws.10%29.aspx
    8.  
    9. The user defined in the adapter configuration must be able to access the admin share of the target machine.  To check this go to Start -> Run-> and run the command “\\target machine hostname\C$”. If this fails, switch to a different user or work with your system administrators to get the required access.
    10.  
    11. Make sure "Logon With User Credentials" is checked or set to "true" in the adapter configuration or adapter request.
    12.  
    13. When running an ADAM command, if the AD *.ldf files are stored within the C:\Windows directory the adapter may not be able to access them. Move the *.ldf files to another directory outside the C:\Windows folder.
    14.  
    15. Ensure the "Adapter Files Location" specified in the Adapter configuration does not contain trailing "\"

     


    Article Number:

    000100276


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles