"It seems that no FAPService is running..." when using named (non-default) instance of SQL server
User launches the FAP client (e.g. "IBM Cognos FAP" or 'IBM Cognos 8 FAP' for older versions). User enters the password and clicks 'Log in'. User receives error message.
After click "OK" the FAP Client successfully opens, but the functionality will not work correctly (because the FAP Windows service is not functioning correctly).
It seems that no FAPService is running or FAPDb is started/restarted after FAPService.
Start/restart FAPService to make FAP work correctly.
"Error.log" (by default, located here: C:\Program Files (x86)\IBM\cognos\c10\server\FAP).
2013-02-13 16:09:05,671 [schedulerThread] ERROR Scheduler - Connection error to FAP database
com.ibm.cognos.fap.common.exception.ConnectionException: Could not connect to: jdbc:sqlserver://SERVERNAMEinstancename;Database=DATABASENAME
org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (The TCP/IP connection to the host
1433 has failed. Error: "null. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".)
... 9 more
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host vbracontsql4latin1, port 1433 has failed. Error: "null. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".
There are many potential causes for the "It seems that no FAPService is running..." error.
- For more examples, see separate IBM Technote #1424705.
This Technote specifically relates to the scenario where the log file also contains a message "Could not
connect to: jdbc:sqlserver://SQLSERVERNAME instancename;Database=databasename".
- In this scenario, the cause is that the "IBM Cognos FAP Service" Windows service has not started correctly because the settings inside the file "FAPService.properties" are incorrect
- Specifically, this is due to the wrong nomenclature used to configure the FAP service to use a non-default SQL TCP port.
Imagine a scenario where the FAP database is hosted on a SQL server called "SQLSERVERNAME", but *not* on the default instance.
- Instead, the database is hosted on an instance called "instancename".
The administrator (incorrectly) configures the file "FAPService.properties" (by default located on the Controller application server here: C:\Program Files (x86)\IBM\cognos\c10\server\FAP) with the following text:
The above is incorrect. The correct nomenclature should be either:
Customer is hosting the FAP database on a SQL server which is not running on the default instance (e.g. "SQLSERVERNAME").
- Instead, it is running/hosted on a 'named' SQL instance (e.g. "SQLSERVERNAME\instancename")
Resolving the problem
Perform both of the following:
(1) (Most importantly) modify the file "FAPService.properties" to use the correct nomenclature.
- For instructions, see separate IBM Technote #1417314.
(2) Afterwards, when launching FAP client, ensure that value inside "Server" box uses the correct (JAVA compatible) nomenclature.
- See below for instructions.
Steps for (2) - to ensure that value inside "Server" box uses the correct (JAVA compatible) nomenclature:
If using a non-default instance, this would be: <SERVERNAME> ,<TCP_port>
- TIP: If unsure of the TCP port, see section below for instructions on how to locate this value.
For example, if your SQL server name was "SQLSERVERNAME" and your instance was running on TCP port 1434 then the correct syntax would be:
If desired, there is an alternative method where you:
- Create a SQL Native Client "Alias" on the device which is running the FAP client.
- Configure the Alias to use to the instance's TCP port number.
- Finally, use this alias name when using the FAP Client.
Steps for Alternative Method:
TIP: The following is based on SQL 2005. For other versions, the steps may vary slightly.
Part One - Checking the TCP port of the SQL instance.
- Logon to the SQL server as a Windows administrator
- From the Start Menu, launch "SQL Server Configuration Manager"
- Expand the section 'SQL Server 2005 Network Configuration'
- Highlight "Protocols for INSTANCENAME" (where "INSTANCENAME" is the instance name of your server)
- Double-click on the entry "TCP/IP"
- Click the tab "IP Addresses"
- There may be several sections (for example "IP1", "IP2" and "IPAll"). Inside each of these, there is a section for 'TCP Port'. TIP: The default instance is typically set to 1433, but your 'instancename' will be configured to use a different number (for example 1434)
Part Two - Creating the SQL Native Client Alias.
- Logon to the client device (i.e. the device where you are launching the FAP Client) as a Windows administrator
- From the Start Menu, launch "SQL Native Client Configuration (32-bit)"
- Open the section "Aliases"
- Create a new entry (for example called "ControllerSQL")
- Configure the "Port No" to be the value found in part one (e.g. 1434)
- Configure the "Server" to be the name of your SQL server (e.g. "SQLSERVERNAME")
Part Three - Launching the FAP Client
When launching the FAP Client (e.g. FAP Connect), make sure that you use the new 'Alias' name (e.g. "ControllerSQL") inside the section "Server":