Thanks Pitch:) Unfortunately neither solution is the cause:( Everything installs OK and even after the dependency errors appear, I can still get a successful test connection to the SQL database from ePO4.
As I said, everything installs OK - the first update of the repository from NAIHTTP downloads and installs OK...all the policy settings I create work OK and the group creation and domain sync works properly. The dependency initialisation errors occur after: Installation of SQL 2005 SP3 OR Adding McAfee Agent 4 to the repository OR Rebooting the server for the first time after Installation and setup of ePO4
Am getting bald patches tearing my hair out over this one<G> regards W:)
Oh dear...not on a DC:( I hope the customer has another server they can add to their network to use as an ePO server. I was advised, by McAfee tech support to to rebuild my sick server via kc.mcafee.com using KB51438. I will try this tomorrow, but I doubt it will solve the problem, as I have reinstalled (clean installs) and installed on a brand new server ( fully installed and configured and completely error free and yet the problem still occurs after a certain time...ie either after rebooting the new server for the first time or installing sql2005 sp3. W:)
We had this problem recently. It turned out that the path to our repository had changed. The repository should be in C:\Program Files\Mcafee\ePolicy Orchestrator\server\extensions\installed\RepositoryMgmt but for some very strange reason ours was now within a sub directory of the RespositoryMgmt called RepositoryMgmt ie. C:\Program Files\Mcafee\ePolicy Orchestrator\server\extensions\installed\RepositoryMgmt\RepositoryMgmt We just copied the contents of that directory back up one level and then everything worked again. It definitely was not any of my colleges or myself that did this. Hope this helps some sad admins out.