FalconView Install Issues
We are working through a number of install issues in various versions of FalconView and TalonView. These pages are a repository of tips and tricks to help. Most of the install problems that we hear about are related to getting Microsoft SQL Server working with appropriate privileges. The verson of SQL server depends on the Version of FalconView:
- FalconView 3.x
These versions of FalconView did not use SQL server. Most 3.3.1 issues are a result of lack of user permission to write to the c:\pfps\ directory. Other issues are listed in the FalconViewWontStart topic.
- FalconView 4.0
This version should no longer be in use but it used MSDE Microsoft SQL Server 2000 Desktop Engine.
- FalconView 4.1.x and 4.2
This version uses Microsoft SQL Server Express 2005.
- TalonView 4.1.1
Uses Microsoft SQL Server Express 2005. TalonViewInstallers are different from FV 4.1.1 installers and can have an issue not directly related to SQL Server if the temp path has too long of a name. The issue is discussed here.
- FalconView 4.2.1 (previously 4.3)
This version uses Microsoft SQL Server Express 2008.
Sql Express 2008 requires the following privileges for the user running the installer (see http://support.microsoft.com/kb/2000257/en-us)
|Local Policy Object Display Name||User Right|
|Backup files and directories||SeBackupPrivilege|
|Manage auditing and security log||SeSecurityPrivilege|
To check to see if you have this privilege, Open Group Policy... Start | Run Type: gpedit.msc OK, Navigate to Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug programs
SQL server install returns error 2147749896 (0x80041008) The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine mymachine.
Problem with permission groups on NonEnglish Versions of Windows
FalconView gives certain Data Base privileges to the "NT Authority\System" group during the install. On non English versions of Windows the group may not exist. A work around is discussed NonEnglish here?
Problem if MSXML 6 sp2 is installed (SQL Express setup failed with exit code 4081458321)
We were recently told that there are problems installing MS SQL Express 2005 SP3 if Microsoft XML 6 service Patch 2 (MSXML 6 SP2) is on the machine. This is likely to happen on versions of Windows XP. This page explains the process to remove MSXML.
Problem with MS SQL Server 2008 on Win 7 32 bit
This problem is only appearing with the 4.3 beta versions under Win 7 32 bit. When you run FalconView it fails to initialize and generates a login failed error. We have a work around LoginFailed here?.
Cannot Generate SSPI context Error
This problem was more prevalent on 4.1 but still may plague some users of FalconView. The underlying error:
“Error code 0x80004005 - Unspecified error - OLE DB Error 0: Cannot generate SSPI context” is reported when the database is unable to authenticate the user attempting to access the data. Information of resolving this issue is SspiContext here?.
Sql Express 2008 setup failed with exit code 2227047362
Sql Express 2008 setup failed with exit code 2226323457
This problem occurs because the Network Service account does not have permissions on the following folder: C:\Documents and Settings\NetworkService?\Application Data\Microsoft\Protect
Note, this error was also seen on an XP machine running as an administrator. In this case, an uninstallation of compact SQL Express 2005 solved this.
Installing PFPS 4.2.1 on Windows Server 2008 R2
There are two steps that must be completed before installing PFPS 4.2.1 on Windows Server 2008 R2:
- Activate .Net 3.5.1. This is already installed on Windows Server 2008 R2, but not activated. This seems to confuse the PFPS installer and it fails on the .Net step. Just go to:
and follow the instructions there.
- The Java installer that comes with PFPS doesn't work correctly. Downloaded the Offline Installer from
and use this to install Java.
At this point you can install PFPS 4.2.1.
Hint for Installing Older Versions on 64 bit Windows 7
See http://www.FalconView.org/trac/FalconView/discussion/topic/181 for a trick to install older versions on Win 7.
Command Line options for installing Sql Express 2008 (used by FV 4.2.1) manually
setup /QS /ACTION=Install /FEATURES=BC,SQLEngine /INSTANCENAME=FV_SQL_SERVER /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /BROWSERSVCSTARTUPTYPE=Automatic /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS
Command Line options for installing Sql Express 2005 (used by FV 4.2.0) manually
MSDE2005\setup DISABLENETWORKPROTOCOLS=0 SQLAccount="NT AUTHORITY\SYSTEM" SAPWD="5F401142-BAFC-49ba-BE1B-EA4CACC0AD09" INSTANCENAME="JMPS_SQL_SERVER" ADDLOCAL=SQL_Data_Files/qb
Note the SAPWD Can be any password (make up your own).
After uninstalling a previous install, you try to install a newer version and get a message, "The Windows Installer Service could not be accessed..."
Issue the commands "msiexec.exe /unregister" then "msiexec.exe /regserver" then restart. See http://support.microsoft.com/kb/315353.
Installing PFPS 4.2.0 SP1 on Windows 7
- Open up SQL Server Configuration Manager
- Go to SQL Native Client Configuration | Aliases
- from the menu, choose Action | New Alias...
- In the Alias Name field, specify "127.0.0.1\JMPS_SQL_SERVER" without the quotes
- In the Server field, specify ".\JMPS_SQL_SERVER" without the quotes
- Click OK
Now that the alias has been setup, the database needs to be initialized using the following steps:
- Open a command prompt window with elevated privileges
- run "cd \Program Files\PFPS\falcon" without the quotes
- run "fvw /REGSERVER" without the quotes