Forum Discussion

cmi_it's avatar
cmi_it
Level 3
11 years ago

Enterprise Vault Admin Console Installation failure

I tried to install the Enterprise Vault Administration Console on a Windows Server 2008 R2 SP1 server however I am stuck in a loop that states:

Installation has checked the software and settings on our computer and has generated a report. The pre-installation scan found problems that you must resolve before you can continue the installation.

The report states that DCOM is enabled but the Windows Firewall is preventing entry on TCP Port 135. This Port must be unblocked in the Windows Firewall settings for DCOM to work correctly. For more information, see http://www.symantec.com/docs/TECH87314.

I tried all steps in TECH87314 and continue getting the same results.

I removed the appData\Local\temp\2 folder, tried installing again, chosing to skip the prescan and get the exact same results.

What am I missing here?

 

 

  • Thank you all for the feedback, I found the issue. Our iSCSI connection was showing as a Public connection, once I disabled the firewall for Public Networks the installation went through successfully.

    Odd that this would cause an installation failure, especially since the routable TCP connection was set to domain connection and the firewall is already set to disable on domain connection through group policy.

  • Sorry, forgot that detail. The firewall is already disabled for domain and private. It makes 0 sense.

  • hmmm, that is a bit strange then.  Do you have any other AV software on the server?

    Also, what happens if you install the Deployment Scanner and run it?  What does it report?

  • I could be wrong but doesn't the installer check the exclusion regardless of whether the FW is enabled or disabled?
  • Yes JesusWept. It does check but as he said that he followed the article TECH87314 thoroughly.

    then it should not give him this error as in the first solution we make exception in the FW for port 135.

    @ cmi_it: I just thought if you want check the article once again and just amke sure that you have not missed any step.

    If not then could you please check the system event log on the EV Server and see if we are getting any DCOM errros.

     

  • Thank you all for the feedback, I found the issue. Our iSCSI connection was showing as a Public connection, once I disabled the firewall for Public Networks the installation went through successfully.

    Odd that this would cause an installation failure, especially since the routable TCP connection was set to domain connection and the firewall is already set to disable on domain connection through group policy.