Page 1 of 1

Filestreamer fails to install

Posted: 25 Mar 2014, 09:29
by marthorton
I'm trying to install FS to trial with DPM 2012 SP1 on Windows Server 2012 64bit. When I run the installer it just hangs at the "Please wait while the installer prepares to guide you through the installation..." pop up box. I've tried rebooting the server and running the installer in compatibility modes but nothing has worked. I'm installing it as the Admin user.

Any help would be appreciated.

Martin

Re: Filestreamer fails to install

Posted: 25 Mar 2014, 18:33
by jsf
How long did you wait for the installation to complete? Could you create folder c:\temp\, copy the Firestreamer installer there and run the following command from an administrative command prompt:

Code: Select all

msiexec /lvx* c:\temp\log.txt /i c:\temp\Firestreamer-x64.msi
Could you then email resulting c:\temp\log.txt to us?

Thank you.

Re: Filestreamer fails to install

Posted: 26 Mar 2014, 03:56
by jsf
Firestreamer 4.0.0 fully supports Microsoft Windows Server 2012 and 2012 R2. The installation should not be affected by the presence or absence of Microsoft DPM because Firestreamer is not aware of DPM and does not interfere with it in any way. In any event, Firestreamer fully supports Microsoft DPM 2012 and 2012 R2.

Note that Firestreamer requires ".NET Framework 3.5 Features" which can be installed through Server Manager > Add Features. If .NET Framework 3.5 is not present, the Firestreamer installer displays an error message asking to install the framework.

>>When I run the installer it just hangs at the "Please wait while the installer prepares to guide you through the installation..." pop up box

The above message indicates that the Firestreamer package is being prepared for installation by Windows Installer. It can be that the Windows Installer service is disabled on your machine, that the Windows Installer is trying to verify the package's signature but the Internet connection is unavailable, that there is some issue with the custom security policy on your machine, and so on. Please check Windows Event Log for any errors or warnings.