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.
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.
This issue is definitely a bug in the tray notifier.
It isn't popping up login credentials, so
Log first into IE
Check remember me - try to save credentials
Close IE/Launch the notifier
It should be successful
Henry Wilson posted the answer in their forums. Hopefully it's fixed soon.
I had a similar problem, the only difference is that it was stuck in "Loading..." and not in "Logging in...".
I added a trailing slash to the URL in "HKEY_CURRENT_USER\Software\JetBrains\TeamCity\WindowsTray\Login" but it didn't help, so I deleted the whole tree "HKEY_CURRENT_USER\Software\JetBrains\TeamCity". After a restart of the application, it asked again for the URL.
I use 8.0.5 on the server. The tray notification reports "build NA" in the about window...
I have had this on:
Windows 7 - 64 bit,
TeamCity Pro 7.1 (build 23907)
All other effects are identical as above.
The suggestions above didn't work for me, but it did allow me to re-enter the server address.. still the problem persisted.
What worked for me was to remove then re-install in "Program Files" instead of the default "Program Files (x86)". There are a few reasons why this as-a-fix should be unnecessary, but it worked and I'm happy.
This worked for me:
Open the CI-Server URL in Internet Explorer
Log out from the CI-Server
Restart the Tray Notifier (maybe kill via Taskamanger)
Log in again
p.s. not sure if it is relevant, but for completeness:
I also added the CI-Server URL in the trusted sites in Internet Explorer → Internet Options (as mentioned in this answer: https://stackoverflow.com/a/12001721/1520422)
Related
I make sure all of processes of VS Code have exited, but I can’t delete the bin directory.
I tried many tools to find which process is using the directory, but none of them reported.
The problem occurs on all of my Windows devices and I need to manually update each time.
This link suggests a workaround might be to stop Skype for Business:
https://github.com/Microsoft/vscode/issues/60697
Notes:
Different users had to close Skype for Business, SkypeBridge, or even f.lux (?)
Per the link, you can use Windows Process Explorer to determine which apps are holding "bin" open
In my case it was Teams, and found that by searching for Skype in Windows Process Explorer. Killed it and the update went smoothly.
I'm trying to install mongo DB on my local machine with the installer from the official website. But I'm continuously getting this message, can someone help?
I've tried the solution provided here but didn't help.
I suggest doing the following:
Hit Win+R to open up you run.exe then inside of it enter services.msc to open up services. Try locating the service under the name of MongoDB Server and set the Startup Type manually to Automatic - [In addition to that, you could set the username and password manually. If you get a message saying the user was granted login as a service right, try hitting retry on the MSI dialog and see if it starts].
Important:
Don't forget to save and close everything (services.msc) before continuing.
Also very important, you should (must) check your .NET framework version and update it to version 4.5 and above. You could download a software like eg Driver Booster to update all of your drivers and additional components that are outdated.
I ran into the same issue. My problem was the installation location. I was trying to install under C:\MongoDB. I resolved it by installing in the default MongoDb location which is C:\Program Files\MongoDB.
For me this is usually an issue with the configuration file %ProgramFiles%\MongoDB\Server\x.x\bin\mongod.cfg
At some time there was an invalid option "snmp" enabled (only valid in enterprise version).
Nowadays, although the installer asks for directories for data and logs it doesn't ALWAYS seem to use these, but defaults to %MONGO_DATA_PATH% or %MONGO_LOG_PATH%, respectively. I don't know where these should be defined, but the server fails at accessing c:\data\db (which doesn't exist). So you have to correct the paths.
I also faced this kind of error. But I just change the Network service to Local system in Log On As tab.
Follow my step-by-step below to resolve it:
Press Win+R, type: services.msc, then looking for MongoDB Server (MongoDB)
Double click on MongoDB Server (MongoDB).
Then it will open properties tab. On that tab click on Log On
After that check two items i.e. Local System account and Allow service to interact with desktop
After that press Apply and OK button. That's it, cheers!!
Open command prompt and copy the following command:-
"C:\Program Files\MongoDB\Server\4.2\bin\mongo.exe"
NOTE: This Tricks is work on my Windows 8.1 PC.
Comment out string with mp: in configuration file: %ProgramFiles%\MongoDB\Server\x.x\bin\mongod.cfg
Like this:
...
#snmp:
#mp:
Click Windows+r, type lusemgr.msc , Go to Groups and double click Administrators, Click Add, Click Advanced and click Find Now. Double click in Network Service (in bottom list) and click OK.
It worked for me.
Installing in the other locations other than the windows directory caused me this error. Reinstalling the setup with the recommended method of "complete" fixed it.
The problem occurs if you have Windows version previous to Windows 10.
Install the following update before installing MongoDB. Click on the link below.
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows
It worked for me.
The problem occurs if you have Windows version previous to Windows 7. Install the following update by going to below link you have to download
Windows6.1-KB2999226-x64.msu
#You have to download and install then go to servies.msu and start MongoDB server by Start also go into log on and set to #local machine
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows
I'm using install4j 6.0.3, everything works exactly like it should, however if the user tries to change the installation location by using the "Browse" button, the installer locks up completely, and you need to use task manager to kill the process.
This happens on Windows 7 & Windows 8(.1)
Does anyone have any idea of how to fix this issue?
Ok, this is extremely weird, as I was debugging according to Ingo, I checked the option "Allow new folder creation" on, made a build, then checked it off again and made another build.
That build now works for the affected users, I guess there was a latent weird option in the config file or something.
I have installed SQLSERVER2k8r2 (with ssrs) on a win 7pro virtual machine, but every time i try to go to the report manager page though IE , firefox, chrome , all i get is only a blank page no header bar or anything just a blank page.
Every time i try it by running as admin in IE, have set http://Win7VM as a trusted site, i get no error codes or messages like access denied, turned off the windows firewall cause this is a test VM have no anti-virus installed on it.
I have been on google for the last whole day trying to find out why this is happening , have not been able to find anything.
Luckily I haven't had this issue but I have heard of others having it and it was due to some permissions issue.
Check out to see if it helps:
http://dobrzanski.net/2008/03/28/reporting-services-blank-report-manager-screen/
https://social.msdn.microsoft.com/forums/sqlserver/en-US/fffa4d0d-6cc9-4385-8a30-8a1b8243f619/report-manager-blank-page
My Google Chrome developer tools are disabled. I'm not sure how it happened. I was using them in the morning then went to use them in the afternoon and the F12 button wouldn't do anything. Same with ctrl+shift+i.
If I navigate the 'Tools' menu, I can see the 'developer tools' link, but it is grayed out and disabled. Does anyone have any idea how to re-enable them? I uninstalled/re-installed chrome twice but no help.
Delete the DeveloperToolsDisabled registry key in Software\Policies\Chromium\DeveloperToolsDisabled
https://chromeenterprise.google/policies/#DeveloperToolsAvailability
I found it named slightly differently (Win7):
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\DeveloperToolsDisabled
I set it to zero and restarted Chrome --> all is well. No idea how it got set.
Update 5/30/2014: This value was set again, there must be some security policy against this flag where I work. I deleted the key completely and will report back if it appears again.
Update 6/13/2014: Definitely we've got a security policy that is setting this key daily. As a workaround I've created a file, "fix_developer_options.reg" with the following contents and put it on my Desktop:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"DeveloperToolsDisabled"=dword:00000000
This file, when double-clicked, will automatically make this setting in the registry. After that, you need to restart Chrome to get the change. (One step better would be to have this executed when you log in.)
Update 3/4/2018:
In Windows 10 this setting has moved under HKEY_CURRENT_USER as #DGinzberg mentions below in the comments. I found it here on a new computer:
[HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome]
check policies - type chrome://policy/ in url bar. if DeveloperToolsDisabled is set to true, update the registry entry
I just came across a similar issue on my university's website where I could not open the dev tools. Dev tools were opening on other websites in adjacent tabs but not on this site.
Solution:
What worked for me was that I clicked on the address bar of the browser and pressed F12. And it worked. It did not work afterward when I un-selected the address bar and tried again. But worked again when I did it by selecting the address bar.
Hope it would help someone.
Found another issue with the Dev Tools not opening/ working
If the Block access to a list of URLs Enabled
and "file", "" is in it
or
file:// is not in the whitlist of url, the DEV Tools wont open either :)
Maybe that helps someone
Open regedit (Registry Editor) and find the DeveloperToolsAvailability key by first going to this path:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\
... then click Chrome and select DeveloperToolsAvailability from the list on the right. Double click it and change it from 2 to either 1 or 0. Click OK and close regedit, then close Chrome and re-open it. Chrome dev tools should now be enabled.
However, depending on your system, you may instead have the DeveloperToolsDisabled key in that same path. If so, delete that.
If you are using a Google Workspace account and have Google Admin Console permissions, you can follow the below steps to enable the Developer mode of Chrome browser for the entire organization or just an OU.
Log into the Google Admin console (admin.google.com).
Navigate to Device>Chrome>Settings (https://admin.google.com/ac/chrome/settings/user).
On the left, select the proper organization unit which contains the user/s you want to change the configuration for.
Update the "Developer Tool" settings with “Always allow use of built-in developer tools”.
SAVE changes.