TeamCity Windows Tray Notifier stuck on "logged in"

Question

When I run the Windows Tray Notifier on my Windows 8 virtual machine, it remains stuck on a "logged in" message if I hover over the icon of the program in the system tray, and I can't do anything else other than force the shutdown with the Task Manager. I set the correct address where my TeamCity test server is running but it seems unable to connect to. Any help is appreciated.

Answer 1

Fixed it via the following steps:

• Repaired via installer (this clears saved login data)
• Logged into a different server running Teamcity 6.5.3 - this worked
• logged out again and logged into our main teamcity server (running 7.1) - tray notifier is working again

Very strange! Above workaround would only work if you had access to a second server too.

EDIT: Two further workarounds have been posted on the thread I started on the Jetbrains forum, so I'll repost them here for the benefit of others.

Solution 1:

• Kill running tray notifier in task manager
• Open regedit, in HKEY_CURRENT_USER\Software\JetBrains\TeamCity\WindowsTray\Login, update the “S” property to http://192.168.1.1:8080 (substitute real ip address, without the quotes, trailing / seems to be important)
• Open IE, go to team city site
• Log in, checking “remember me”
• While IE is open and connected to TeamCity, start up tray notifier.
• Takes about 15 sec to change from “logging in” to connected.

Solution 2:

Open IE, select Internet Options, Security Tab, add the TeamCity server address to the trusted list.

Please note, I haven't personally tested either of these methods, just posting them here for information since others have found them to work. Hope this helps!

Since upgrading the server to 7.1.1 this issue hasn't reoccurred for me. Looks like it's been fixed as per Eugene's comment elsewhere on this thread.

Answer 2

This issue is definitely a bug in the tray notifier.

It isn't popping up login credentials, so

1. Log first into IE
2. Check remember me - try to save credentials
3. Close IE/Launch the notifier
4. It should be successful

Henry Wilson posted the answer in their forums. Hopefully it's fixed soon.