Console fails to connect

Usage and Config Platform
1

(imported topic written by TheCaptain)

Hi,

When I attempt to login to the Console, I receive the message below:

“Failed to connect to http://localhost:52311: The Adminisrtation Tool needs to be run on the server before you can login”. What task needs to be performed? I tried activating the Masthead, but I get the same message. When I type http://localhost:52311/ into the browser, I get a Page not Found error. I have restarted the machine and check that the BES services are running.

Version = TEM 8.2

What am I missing?

Thanks,

Rob

2

(imported comment written by SystemAdmin)

You’ll need to run the TEM Administration Tool and connect to the your server’s database. This is installed by default in C:\Program Files (x86)\BigFix Enterprise\BES Server\BESAdmin.exe

Once you log in with that it should give you more information on what you need to do next.

3

(imported comment written by TheCaptain)

I opened the TEM Administration Tool and was able to perform a server login. I performed an Activate Masthead, and then pressed ok to exit. I still get the same message. Is there something else I can try?

Thanks,

Rob

4

(imported comment written by SystemAdmin)

After activating the masthead you might want to try restarting the server process. If that doesn’t help I’d recommend giving support a call.

5

(imported comment written by TheCaptain)

I have restarted the server, but the problem still exist. Is it possible that there is a conflict with the SCA server that was previously installed?

Thanks,

Rob

6

(imported comment written by SystemAdmin)

Hey, Rob. I think calling IBM support would be good, but before you do, you might want to enable debug logging for the TEM console application to capture in detail the connection problem:

Enterprise Console

HKCU\Software\BigFix\Enterprise Console

“DebugOut”

REG_SZ

If this key exists and is non-empty, it is taken to be a filename which the console will write a debug log to. This log is fairly detailed, and is designed to help developers diagnose problems. If a user sees an intermittent problem that is not a crash, hitting F12 in the console will leave a ‘debug mark’ in the log, which can be used to help identify what the console was doing at the time the problem occurred. See also Enterprise Console Debug Dialog which is opened by pressing CTRL, Shift, ALT and D.

“EnabledLogs”

REG_SZ

If this key exists and is non-empty, and the “DebugOut” key is set, this key controls which types of messages get written to the log. The string should consist of a semicolon-delimited list of log stream names. If not set, the critical and debug streams are enabled. Some of the possible log stream names:

  • critical
  • debug
  • memory
  • performance
  • timing
  • database
  • all

If “EnabledLogs” is set to “all”, then all log messages will be written.