Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
10752 Views 55 Replies Latest reply: Nov 22, 2013 9:58 AM by gdavid RSS 1 2 3 ... 6 Previous Next
bostjanc Champion 301 posts since
Feb 12, 2009
Currently Being Moderated

Aug 29, 2013 4:08 AM

Epo 5.0.1 - Synchronization point My Organization failed to connect to active directory server

When upgraded EPO from 4.6 to 5.0.1 now Sync AD ain't working anymore.

The error message is:

Synchronization point My Organization failed to connect to active directory server

 

but there's no extra information what's the reason for it. How to get some more log error details?

  • Manish KS The Place at McAfee Member 37 posts since
    Dec 25, 2012

    Hi,

     

    can you enable the debug logging for orion.log and get the this log after reproducing the issue? you may refer the steps below to enable the orion debug level:

     

    1 Using a text editor, open the Log‑Config.xml file, located at:

    C:\PROGRAMFILES\McAfee\ePolicyOrchestrator\Server\conf\orion

    2 In the following line of text, replace “warn” with “info” or “debug”:

    <root><priority value ="warn"/><appender‑ref

    ref="ROLLING" /><appender‑ref ref="STDOUT/></root>

    Use debug only when troubleshooting for a short time. Setting the priority value to debug causes

    the old log files to be deleted frequently.

    3 Save and close the file.

    Tomcat automatically adjusts the log level when the ePolicy Orchestrator Application Server services

    restart.


    Thanks,

    Manish





  • Manish KS The Place at McAfee Member 37 posts since
    Dec 25, 2012

    1. Stop ePO Application server serivice

    2. Open Log‑Config.xml file using notepad

    3. Replace the warn and make it as debug in the following line:

    <root><priority value ="warn"/><appender‑ref

    ref="ROLLING" /><appender‑ref ref="STDOUT/></root>

     

    4. Start the ePO Application server service

     

    5. Log into ePO console

    6. Run AD Sync task, if it fails collect orion.log

     

    the default location of orion.log is : C:\PROGRAMFILES\McAfee\ePolicyOrchestrator\Server\Logs



    Thanks,

    Manish





  • Manish KS The Place at McAfee Member 37 posts since
    Dec 25, 2012

    Thanks for sharing the log.

     

    This is the error I can see from the log:

     

    2013-09-03 10:46:40,426 DEBUG [mfs:pool-2-thread-4] services.EPOMultiPointADServices  - Failed to connect to AD

    2013-09-03 10:46:40,426 DEBUG [mfs:pool-2-thread-4] services.EPOMultiPointADServices  - Failed to connect to AD, exception: com.mcafee.epo.core.EpoConnectException: Failed to connect to active directory server SERVERNAME.DOMAIN.local on port 389, user: DOMAIN\administrator, possible bad server name, user name, or password

    com.mcafee.epo.core.EpoConnectException: Failed to connect to active directory server SERVERNAME.DOMAIN.local on port 389, user: DOMAIN\administrator, possible bad server name, user name, or password

     

     

    According to above error it seems the ePO server is not able to connect to registered AD server, it might be due to incorrect credentials or due to the port 389. So you can go as per below:

     

    1. Log into ePO console

    2. Go to Menu>Configuration>Registered Server

    3. Select the registered AD server and click on Actions>Edit>Next

    4. Check if the configuration is correct if yes, check the box "Change password" provide the correct credentials

    5. Test the connection if it is successful save it

    6. Try with running the ADSync task if still fails go to Registered Server setting page and try with check/uncheck "Use SSL" option

     

     

    Even if issue persist there could be some issue with the LDAP port configured and you can log a ticket with McAfee support.

     

    you may also refer article KB68012 : http://kc.mcafee.com/corporate/index?page=content&id=KB68012

     

     



    Thanks,

    Manish





  • deveras Newcomer 4 posts since
    Sep 17, 2013

    I have the exact same problem. Currently working with support to find out what is the issue.

1 2 3 ... 6 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 5 points
  • Helpful Answers - 3 points