Forum Discussion

Julian_Balog_34's avatar
Historic F5 Account
Feb 12, 2011

Setup fails due to Domain list error (COMException)

[Posting on behalf of R.S.]
I have a working installation of System Center Operations manager 2007 R2 running on Windows 2008 R2 and am attempting to install the F5 management pack.
I keep getting the following error.
<02-11-2011 09:36:18> FatalError: An error has occurred during the F5 Networks
Management Pack Setup. Please contact the F5 Management Pack team at with the following information: There was a problem
trying to retrieve the list of accessible domains.  Please verify your firewall
settings, user permissions and group policies to resolve the issue and then try
setup again.  Related error message:
A local error has occurred.
Is there a work around for this?

2 Replies

  • Julian_Balog_34's avatar
    Historic F5 Account
    Apparently the request made by the F5 Management Pack UI to query the Active Directory domains fails. This could be caused by multiple reasons, ranging from issues related to firewall, group policy, DCOM configuration settings, etc. To isolate the problem from the F5 Management Pack / Setup, please open up a Powershell command window on your management server (RMS) and run the following script / command (copy/paste):

    $domains = New-Object 'System.DirectoryServices.DirectorySearcher' 'objectCategory=Domain'; $domains.FindAll();

    You should be getting an output similar to:

    Path                                                        Properties
    ----                                                        ----------
    LDAP://DC=mgmt,DC=pdsea,DC=f5net,DC=com                     {systemflags, dc, adspath, iscriticalsystemobject...}

    Try also to open the Powershell command prompt as 'Administrator' and run the script above. If you actually get this type of response back, your issue is resolved and it should also work from within the F5 MP setup. But if you don’t than you’ll have to figure out the reason why the Active Directory query fails. The command described above would be almost equivalent to trying to open the Active Directory Users and Computers MMC snap-in from the given management server and try to browse the existing Active Directory locations and objects. You may not have this server feature enabled on the management server, but might help you in troubleshooting.


    (F5 Management Pack)

  • This turned out to be an issue with joining a Windows 2008 R2 server to a Windows 2003 mixed mode AD structure. I was able to add the server to another domain and the installs went without a hitch. Thanks for your help!