TrueSight Server Automation (TSSA): Error when attempting to login to TSSA Console -  "Could not connect to "service:authsvc.bladelogic:blauth://appserver:port"

Version 5
    Share This:

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


    TrueSight Server Automation Suite


    BMC BladeLogic Server Automation Suite



    Error when attempting to login to TSSA Console -  "Could not connect to "service:authsvc.bladelogic:blauth://appserver:port"





    Problem accessing the TSSA Application Server on port 9840 (by default) for authentication



    1) Verify whether the TSSA Appserver is up and running by checking the appserver log. If it is not up and running, resolve that issue and retest.


    2) If the TSSA Appserver is up and running, verify the Authentication Server port is listening. This is port 9840 by default but depends on the Base Port selected for the Application Server:

    netstat -an | grep 9840

    2) If the TSSA Appserver is up and running and listening in port 9840, test connectivity to port 9840 from the TSSA console machine (using telnet or some other tool) in case there is a firewall rule blocking access to the port.





    Listening port for the Authentication Service associated with an Application Server. If this value is set to 0, the Application Server does not run an Authentication Service. By default the Authentication Service runs and listens on port 9840. This port is used for TrueSight Server Automation Console to Application Server communication, and is used in conjunction with the Java Management Extensions (JMX) port 9838 (by default) to authenticate the client AppSvcPort (port 9841 by default)




    Article Number:


    Article Type:

    Solutions to a Product Problem

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