This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SM5 for AD starts then stops

I'm setting up SM5 for AD on Server2012R2. I've gone through the setup, and the install, DB, license, etc are all working, but the service won't start. The smengine.log tail looks like this:

01 2016-11-08 10:33:09 -18000 5 8003 1368 5708 GetServerDSCapabilityFlags() - This system has Microsoft Active Directory capability.01 2016-11-08 10:33:09 -18000 5 8003 1368 5708 GetServerDSCapabilityFlags() - The Novell XPLAT API Libraries are *NOT* loaded.
01 2016-11-08 10:33:09 -18000 5 0001 1368 5708 ML: Engine completed waiting for AD to be ready for use, bOK = 1, Result = 0.
01 2016-11-08 10:33:09 -18000 4 0001 1368 5708 ML: The Novell XPLAT API libraries are *NOT* loaded
  • 0
    adrockk,

    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.

    These forums are peer-to-peer, best effort, volunteer run and that if your issue
    is urgent or not getting a response, you might try one of the following options:

    - Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
    all the other self support options and support programs available.
    - Open a service request: https://www.microfocus.com/support
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.microfocus.com)
    - You might consider hiring a local partner to assist you.
    https://www.partnernetprogram.com/partnerfinder/find.html

    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.microfocus.com/faq.php

    Sometimes this automatic posting will alert someone that can respond.

    If this is a reply to a duplicate posting or otherwise posted in error, please
    ignore and accept our apologies and rest assured we will issue a stern reprimand
    to our posting bot.

    Good luck!

    Your Micro Focus Forums Team
    http://forums.microfocus.com


  • 0
    On 11/8/2016 11:06 AM, adrockk wrote:
    >
    > I'm setting up SM5 for AD on Server2012R2. I've gone through the setup,
    > and the install, DB, license, etc are all working, but the service won't
    > start. The smengine.log tail looks like this:
    >
    >> 01 2016-11-08 10:33:09 -18000 3 8003 1368 5708 GetTrustedDomainInfo() -
    >> Called DsEnumerateDomainTrusts(L"jcschools.stier.org", 0x00000004 (4),
    >> ...), dwResult = 0x00000005 (5), Result = 54.
    >> 01 2016-11-08 10:33:09 -18000 2 0001 1368 5708 ML: Called
    >> xDSContext.ImpersonationBegin(), Result = 54.
    >> 01 2016-11-08 10:33:09 -18000 1 0001 1368 5708 ML: Failed to initialize
    >> 1 or more components and/or services. Engine is switching to
    >> stop-pending state.

    >
    > I originally installed this on another server, and got the same exact
    > problem. I thought it was becuase the other server was a DC, so I moved
    > it to a member server. Still getting the same thing. Can anyone shed any
    > light on the problem for me?
    >
    > Thanks,
    > Adam
    >
    >


    Adam,

    Error '54' is an "Access denied" error. Could you please verify that the
    Storage Manager proxy rights group has all required AD permissions for
    this 'jcschools.stier.org' forest, as described in the "Security
    Specifications" section of the Storage Manager 5.x documentation? (See
    https://www.novell.com/documentation/storagemanager5/storagemanager_ad_admin/data/br0r3lv.html)

    -- NFMS Support Team
  • 0
    Could you also tell us if NTLM Authentication is enabled or disabled in
    this environment?

    -- NFMS Support Team
  • 0 in reply to 
    NFMS Support Team;2444186 wrote:
    Could you also tell us if NTLM Authentication is enabled or disabled in
    this environment?

    -- NFMS Support Team


    NTLM Is enabled
  • 0 in reply to 
    I uninstalled SM 5, and installed SM4 for AD, and everything worked fine. I used the same proxy accounts and groups, so I'm assuming all of the rights were correct.
    Either way, SM4 is working for me now, so I'll leave that running until SM5 matures.
  • 0
    I know this is an old thread, but this turned out to be a very odd issue. After watching log files with support, it stalled on the same object in AD. The object was a user that was created for an attept at implementing adfs, that we didn't end up using. That user object was broken, somehow, as once it was removed everything started working fine.