Remedy - Server - AR Services don't start after installing AR System 9.1 - Error: "The TCP/IP connection to the host {AR Server Name}, port 1433 has failed..." (Windows)

Version 4
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System


    APPLIES TO:

    Remedy AR System Server v9.1.x



    QUESTION:

    Performing a new installation of AR System 9.1, the AR System service does not start and the installation reports as "failed".

    The errors observed are:

    Installation log:
    ..........
    ...SEVERE,
    com.bmc.smbu.install.common.rule.engine.ar.state.change.WindowsArStateChangeStrategy,
    THROWABLE EVENT
    {Description=[Error received when getting pid of Service],Detail=[BMC Remedy Action Request System Server {AR Server Name}]},
    Throwable=[java.io.IOException: The service is not running.
    ..........


    armonitor.log:
    ..........
    <MNTR> <TNAME: Thread-3 > <INFO >..... */ org.apache.commons.dbcp.SQLNestedException:
    Cannot create PoolableConnectionFactory (The TCP/IP connection to the host {AR Server Name}, port 1433 has failed. Error: "null. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".)
    ..........



     


    ANSWER:

    1.Check and make sure the Database port being used DB port is open/available in the network and we are able to Telnet the SQL Database server and use the Ping command.

    2.  Also please ensure you have Server Name and Server-Connect-Name resolvable over network, if you are able to telnet to server with 1433 port.
    3. Also check if you have TCP/IP enabled on DB side
       1> Open the SQL Server Configuration Manager. This can be found under SQL Server Installation Dir\Configuration Tools
       2> In the Left Panel goto SQL Server Network Configuration -> Click on Protocols for MSSQLServer
        3> In Right Side Panel select the Protocol TCP/IP.  Check if enabled or not.


    4. If you are using Short name or Fully Qualified Domain Name ensure this is resolvable over network.

     


    Article Number:

    000115079


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles