MP Installation Failure - The specified domain either does not exist or could not be contacted

Hello,

 

Can you please post or send us your setup.log file from C:\Program Files\F5 Networks\Management Pack\logs ? If you don't feel comfortable posting it on the forum, you can send it to ManagementPack(at)f5.com. We will have a better picture of your deployment and be able to better identify what the problem could be.

 

 

Thanks,

 

-Dave

 

<05-04-2010 09:10:59> Info: Appending to existing Setup Log...

 

 

 

 

<05-04-2010 09:10:59> Info: Found .NET framework installed: 2.0.50727.4927

 

<05-04-2010 09:10:59> Info: Started installation of the F5 Networks Management Pack 2.0.0.516.

 

<05-04-2010 09:10:59> Info: msi logging parameters: /lwecma!

 

<05-04-2010 09:10:59> Info: System Center Operations Manager 2007 R2 (Version 6.1.7221.0) found.

 

<05-04-2010 09:10:59> Info: Extracted msi to a temp directory. Running the F5 Networks Management Pack installation.

 

<05-04-2010 09:11:02> FatalError: An error has occurred during the F5 Networks Management Pack Setup. Please contact the F5 Management Pack team at managementpack@f5.com 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:

 

 

The specified domain either does not exist or could not be contacted.

Is the server you are running setup on actively connected to the domain? I assume that it is since SCOM will not work properly without being connected.

 

 

Also, is your firewall blocking LDAP traffic in any way?

 

 

And lastly, can you grab this script file and email us the results. It was supposed to run and write to the setup log, but either the log is incomplete or something is going wrong with our setup program. Here is the script: SystemInformation.PS1 and our email is

 

 

Thank you and sorry for the troubles,

 

-Dave

 

Hi,

 

 

I was running into this error too. I logged out of the machine and noticed I had logged in as the local administrator on the box. I logged back into the server as an AD account and was able to run the install.