Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
New Contributor

ForticlientEMS install error

I am using a command line to install Forticlient EMS

FortiClientEndpointManagementServer_7.0.0.0042_x64.exe -burn.filehandle.attached=488 -burn.filehandle.self=492 SQLUser=***** SQLUserPassword=***** InstallSQL=0 ScriptDB=1 SQLServerInstance=MSSQLSERVER SQLService=MSSQL13$MSSQLSERVER "SQLCmdlineOptions=/INSTANCENAME=MSSQLSERVER /INSTANCEDIR=D:\Program Files\Microsoft SQL Server" DBInitialSize=31MB DBInitialLogSize=4MB DBGrowth=11MB DBLogGrowth=11% DBLoginTimeout=31 DBQueryTimeout=61'



The installation log shows that the registry key is not found and is looking for Microsoft SQL Server\Instance Names\SQL', Value = 'FCEMS' <--- I don't know what is is this variable. I am not able to find in my server

[2454:37DC][2021-09-27T15:41:54]i000: Registry key not found. Key = 'SOFTWARE\Fortinet\FCEMS' [2454:37DC][2021-09-27T15:41:54]i000: Registry key not found. Key = 'SOFTWARE\Fortinet\FCEMS' [2454:37DC][2021-09-27T15:41:54]i000: Registry value not found. Key = 'SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL', Value = 'FCEMS'


The final error:

[2454:3330][2021-09-27T15:42:28]e000: Code: 0x80004005 Code meaning: Unspecified error Source: Microsoft SQL Server Native Client 11.0 Description: SQL Server Network Interfaces: Connection string is not valid [87].

[2454:3330][2021-09-27T15:42:28]e000: Error 0x81f40001: Bundle condition triggered failure: Connection to database failed. See log for details




New Contributor II



You can attempt the following methods to fix this issue:


1. Verify that your server's Microsoft SQL Server installation and configuration are right. Ensure that the 'MSSQLSERVER' SQL Server instance you provided is installed and operational. Check to see that the required services are available and operational.


2. Verify your command-line inputs for the FortiClient EMS installation again. Verify that the variables SQLUser and SQLUserPassword are accurate and have the necessary access rights to connect to the SQL Server instance.


3. Verify the existence of the registry key "SOFTWAREFortinetFCEMS". If the required registry keys do not already exist, you may need to refer to the FortiClient EMS documentation or get in touch with Fortinet support for instructions on how to generate them.


4. Examine the installation log in greater detail to find any more errors or warning messages that can shed more light on the problem. More detailed information about the unsuccessful database connection should be available in the log file.


I hope that this would enable you to solve your issue.

Vivek Garg
Vivek Garg
Top Kudoed Authors