Video Screencast Help
Search Video Help Close Back
to help

Problem Installing the FSA Agent

Created: 06 Jul 2012 | 1 comment
Rob.Wilcox's picture
Rob.Wilcox Partner
0 0 Votes
Login to vote

 

This morning I was installing the FSA Agent on to a freshly installed Windows 2003 SP 2 server. It was failing near the end and rolling back. The only error was that it said "The installation was interrupted".

I read a few forum posts which suggested running NewSID, if the machine was a cloned/vm-image. Well, mine wasn't. It was a nice fresh install from the DVD.

I ran :

msiexec /i name-of-msi.msi /l*V c:\install.log

I started to browse up from the bottom to where the rollback was started, and spotted this :

DIFXAPP: 'CustomActionData' property 'ProductName' is Symantec Enterprise Vault - FSA Agent.
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Symantec Corporation.
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: INFO: evmf.inf: checking signature with catalog 'C:\Program Files\Enterprise Vault\drivers\evmf.cat' ...
DIFXAPP: ERROR: Signature verification failed while checking integrity of driver package 'evmf.inf' ('C:\Program Files\Enterprise Vault\drivers\evmf.inf'). (Error code 0x800B0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.)
DIFXAPP: INFO: Successfully removed {9BBEE86F-666A-4735-A1CF-2847669D3CEE} from reference list of driver store entry 
DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x800B0100)
DIFXAPP: ERROR encountered while installing driver package C:\Program Files\Enterprise Vault\drivers\evmf.inf
DIFXAPP: InstallDriverPackages failed with error 0x800B0100
Action ended 12:06:40: InstallFinalize. Return value 3.

My machine was literally Windows 2003 SP 2.. no other updates, and the NIC is hostonly. I can only imagine that this operation requires a connection out to the internet to validate the signature, and it's failing, and therefore failing the install overall.

I powered off the virtual machine, added a NAT network (to go along side the host only one), and powered it back up.
Bingo the installation runs through with no problems!

 

Blog Entry Filed Under:
, ,

Comments 1 Comment • Jump to latest comment

EV007's picture
EV007
Problem Installing the FSA Agent - Comment:02 Oct 2012 : Link

Yes FSA agent installation does need connection to internet if the verisign root certificate is not up to date.

FSA Agent installation requires an up-to-date VeriSign root certificate on the target computer. Certificate updates usually happen automatically over the Internet. If the certificate is out-of-date, for example because the computer has no Internet connection, the FSA Agent installation fails with a ‘Signature verification failed’ error in the FSA Agent installation log. For more details and for instructions on how to update the root certificate, see the following technical note on the Symantec Support Web site: http://www.symantec.com/docs/TECH179712

 

 

Download PCA-3G5.pem following technote above

 

  1. On the target computer, run the Microsoft Management Console, mmc.exe.
  1. From the File menu, select Add/Remove Snap-In.
  2. Add the Certificates snap in, using the following options:

           •Select "Computer account" as the account to be managed.

           •Select "Local computer" as the computer to be managed.

  1. In the left pane of the MMC, expand Certificates > Trusted Root Certification Authorities > Certificates.
  2. Right click Certificates and select All Tasks > Import.
  3. In the Certificate Import wizard, specify the path to the PCA-3G5.pem file, and complete the wizard to install the certificate.
0
Login to vote