Change default credentials in Tee-clc. MacOS - macos

I installed tee-clc 14.135 using brew install on MacOS Catalina. I set it up with my credentials that were saved and every time I do checkin it uses those credentials.
tf checkin
Access denied connecting to TFS server http:severname:8080/ (authenticating as UserName/DomainName)
I need to substitute cached credentials with the new ones. Any ideas how to do so?
I tried:
export TF_AUTO_SAVE_CREDENTIALS=1 and using different credentials.
Uninstalling tee-clc didn't help. Still picks up old credentials

I need to substitute cached credentials with the new ones.
You could clear mac cached credentials by reference to Password, Credential Manager and Keychain Editing for guidance.
If you use Eclipse, please close all Eclipse instances, clear TFS/DevOps caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache, and restart the Eclipse as Administrator.
If you use Visual Studio, please refer to this thread: Clear stored TFS credentials in Visual Studio for more details.
In addition, if your organization is secured with a firewall or proxy server, please refer to this doc: Allowed address lists and network connections to configure your Network environment.
BYW, this thread talks more about this issue, might be helpful too.

Related

How to give permissions to iis user for printing?

I built an API in .Net Core that integrates with different printers through winspool, when running on visual studio, it works just fine, but when I publish it to the IIS on my local computer it doesn't work. I've read a lot and there are some local users on IIS among them the Local System user that has extensive privileges but it doesn't work, I tried that user on in the application pool that my api is using but no luck, I also tried enabling Impersonation using my user in the computer but nothing works, so I think I have to modify permissions to this IIS users, how can achieve this?
Thanks for your help in advance.

Visual Studio 2017 - How to fix error: We could not refresh the credentials for the account

My email address has changed and now I can't log into Visual Studio 2017.
The error is "We could not refresh the credentials for the account. Failed to refresh the access token".
How can I fix this?
This bug will be fixed in a future version.
For now:
Close down VS2017
Go to "C:\Users\{username}\AppData\Local\.IdentityService"
Rename "IdentityServiceAdalCache.cache" as shown below. (for example just add an underscore to it)
Restart VS2017 and log in.
NOTE: There are similar issues that this won't resolve, but this worked for me.
Open Visual Studio. Click Help, Send Feedback, Report a Problem...
This brings you to a login screen. If you log in from there, it will log you into Visual Studio.
What worked for me was to rename .identityservice and then restart VS and log in to your VSTS account. It then recreates a new .identityservice that it can access.
I tried by deleting only the IdentityServiceAdalCache.cache as in the accepted answer but it did not fix the problem.
For the record, I managed to fix it by deleting every files within the .IdentityService folder (located in C:\Users{username}\AppData\Local.IdentityService).
I have read dozens of posts on this topic discussing clearing out .IdentityService. I tried every variation of this solution that one might think of. None worked.
I ended up poking around and trying to manually login to my Microsoft account using Internet Explorer, but I could not connect to https://login.microsoftonline.com. I added the https://login.microsoftonline.com address to my Trusted Sites in Internet Options. Once I had done this, Visual Studio was able to connect to Microsoft and validate my account.
When an error occurs, Visual studio will log it's error messages in the following folder. Please check the logs located at
%Temp%\servicehub\logs
This can also be caused by network restrictions. Please disable your virus guard or firewall and check.
This issue can also be caused by running VS "As Administrator" and the administrator is a different user. Just some FYI.
None of these answers will resolve that issue unfortunately.
Very old thread but if someone is still having this issue, then try following in my footsteps:
I just deleted the entire .IdentityService folder, and launched visual studio again... It asks you to log in and works normally. (for me)
Make sure you can access https://login.microsoftonline.com
If your network is blocking that (perhaps to block Microsoft webmail), then the above solutions will not pertain to you. Either unrestrict access, or you will need some off-line version.
In case someone is still looking for an answer. What worked for me was checking that the AppData folder and Local folder were not on 'read only mode' in the path "C:\Users{username}\AppData\Local.IdentityService" and it just worked!
Check to make sure that your PC no limit(IP-Firewall) to Internet connection access.
Disable or turn off VPN
It happened to me when using an account that uses my organization's email-domain, and I guess it tried to verify it and it couldn't find it in their database, and as soon as I used an account with a onmicrosoft.com domain, it worked.
The interesting part is that it allowed me to create the Microsoft account with this organization email and I still use it for DevOps, and it just stopped me when signing in with Visual Studio, I don't understand why this difference is.
I hope this can help someone..
I have VS 2017 and had this exact issue. Simply deleting
C:\Users\{username}\AppData\Local.IdentityService did not work for me.
Follow the steps 1-2 below to see if you might have and identical cause of the problem, and the rest how to solved it if so.
Go to C:\Users\{user}\AppData\Local\Temp\servicehub\logs and open the latest error logs from VS.
IF you see "Retrieved tenant memberships, found '2' owned tenants", then follow the rest of the steps.
Go to azure portal then login under the username you are
trying to use.
The following steps may change by the time you read this, but you
want to get to step 6. Go to Manage Azure Directory.
Click "Switch Tenants"
I was linked to 2 tenants, one of which I did not need. This is what had been causing my issues. Select the useless tenants, and click "leave tenant".
Once this is completed, close all instances of VS.
Delete C:\Users\{username}\AppData\Local.IdentityService.
Open VS and login to your account.
I found the same behavior when using Administrator user.
Any other user can login and activate the license only for himself.
I don't think there is a way to activate for Administrator, which makes using this licensing awkward for usage in a shared resource (i.e. build server).
The one solution which worked for me was resetting the domain password and restarting the system.
I just wanted to share this because i was struggling with the same problem since 8 days tried everything on net and this worked.
Hope it helps someone :)
I updated Visual Studio with latest package and after rebooting my PC issue was solved. I was able to log-in
Opening VS as admin worked for me, none of the above did
I was getting this error from our proxy having restrictive rules in place, I was able to add the sites to a whitelist that were being blocked while trying to login.
Some of the sites I whitelisted in Webmarshal were:
*.windows.net
*.msocsp.com
*.ws.symantec.com
*.digicert.com
*.clicktale.net
app.vssps.visualstudio.com
demdex.net
For me it was due wrong system time, after setting correct time it got fixed automatically
I had the problem of not being able to sign in to VS after not using unity for a long time and then updating everything. The way I solved it was to open VS and then click help. This opened the sign in box with 'Personalization Account'. I clicked 'Account options' under the afore mentioned heading, and changed the 'Embedded web browser' to 'System web browser' in the right window. This enabled me to log in via my Edge browser and everything worked fine.
I just fixed it by changing folder to be public.
folder files: "C:\Users{username}\AppData\Local.IdentityService"
right click and choose property and uncheck the hidden and apply it.
If you are under a domain network there is a workaround (quick fix),
Adding or changing the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
ProtectionPolicy = 1 (DWORD)
Check the most recent modified files at %temp%\servicehub\logs.
Check StorageUtilitiesSingleton-10788-lqnuymos-1.log
For an error like this: The computer must be trusted for delegation and the current user account must be configured to allow delegation.
If that is the case this might help you.
I has this issue recently.
Tried all the options above, none worked.
Get it sorted, after repairing Visual Studio, doing all the updates, restart and updated again, restart, another repair and bang! Worked like a charm.
Instead of doing all this, change embedded broswer to system browser so it will works normally in default browser and gets updated in VS.
In VS 2019 enabling System Web Browser instead of Embedded web browser fixed it for me,
Hope this helps someone
https://learn.microsoft.com/en-us/visualstudio/ide/work-with-multi-factor-authentication?view=vs-2019
I tried multiple things above such as
Renaming c:\users[user]\appdata\local.IdentityService
Logging directly in https://login.microsoftonline.com (noticed certificate issues)
Adding https://login.microsoftonline.com to the Trust Sites list in Internet Options
Opening VS as non-admin as well as admin
Reviewed the logs here: %Temp%\servicehub\logs
I also installed Chrome, setting it to the default browser, because many features were saying IE is no longer supported
Reviewing the logs gave me the clue I needed to solve my particular issue. The log stated there was an issue with SSL trust.
Consequently, I ran our local version of rootsupd.exe and installed any related Microsoft root certificates such as the DigiCert Global Root G2 to the Trusted Root Authorities. After rebooting my machine, I noticed VS began recognizing my account and was actually already signed in.

Hyperion Retrieve for Excel - Citrix Environment Profile Corruption

We have an intermittent issue where sometimes when users are trying to access Hyperion Retrieve for Excel, via Citrix, they are not being prompted to provide credentials upon opening the application. We can tell that the authentication process is being overlooked because the data is not able to be viewed. Once we delete the user's profile that is created on the Terminal Server, the problem is resolved once the user launches the application again via Citrix (A new windows profile is created on the TS). I am unable to pinpoint the root cause of these user's profiles becoming "corrupted". Any suggestions here?
Environment:
citrix Xenapp 6.5
Windows Server 2008 R2
Roaming Profiles option is disabled
Timezone Redirection Policy has successfully resolved this issue.

"We couldn't get your developer license for Windows 8", error 0xC03F1014

Whenever I try to get my developer's license in Windows 8 Professional with WMC for Visual Studio Ultimate with Blend, I get this error:
We couldn't get your developer license for Windows 8. (Error 0xC03F1014)
How do I fix this error to get my developer's license?
If your copy of Windows 8 is cracked or activated illegitimately then you'll get this error.
If for whatever reason you don't want to / can't get a legitimate copy, then deactivating the crack to go back to the trial period, acquiring the license then re-activating it should fix this issue.
Try to follow these steps:
Create a temporary user account in windows 8
Install a fresh copy of VS 2012
Now try again. It should work now, then log out again and go back to your normal account. Now develop apps and deploy it. Hopefully it works for you.
You need not re-install the OS or the Visual Studio
Start the Task Scheduler service. This is usually disabled in enterprises/large organizations via Group Policy.
This situation happened to me after installing Windows 8 Pro Upgrade as a CLEAN installation. The problem was that the valid License Key failed to activate because a previous version of windows was not upgraded. Because it wasn't activated properly, the Developer License would also not register.
The following steps enabled me to activate the clean install:
Run the registry editor (regedit)
Find the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE
Change the value for 'MediaBootInstall' from 1 to 0
Open an elevated command prompt (run as admin)
Run the following command: slmgr -rearm
Reboot
Open an elevated command prompt (run as admin)
Run the following command: slui 3
Activate your valid Window 8 Pro Upgrade License Key
After my Windows 8 was properly activated, the Developer License renewed with no problems!
I was facing same issue. Error was due to Proxy Server. I was using internet by setting proxy server. U should have open internet to get the developer license.
See these type off error occurred to me . The scenario was I was connected to a proxy server and my proxy server was not allowing popup logins .
Check your internet connection and If the problem is not solved, reinstall VS
Run Visual Studio 2012 as administrator. It should prompt you automatically for the license. I had to login to my MSDN account at this time. If it doesn't come up, then go to Project -> Store -> Acquire Developmer License. This is what did it for me.
I had the same issue, with the additional information that there was a problem with the network (even though my network was fine).
For me, the problem was that my own user is a limited/normal user and doesn't have administrator rights. I did get a UAC prompt when I tried to get a license and I elevated the process to use my separate administrator account, but it didn't work.
What did work however was logging out from my normal user, signing in as my administrator account and try to get a developer license that way.
So apparently running under a non-privileged user is not something that VS2013 appreciates in scenarios like this. I'm not sure why there is a difference between elevating a process' rights through UAC and actually logging in as an elevated user.
Make sure you have all Windows Updates installed. If you can't update:
Install KB2913270 (x86/x64) (original info by Ahmad Wahid, thanks :))
Other tips:
Check the system date and time (it must not be ahead on their systems)
Try to disable NlaSvc service (Network Location Awareness)

Team Foundation Server asking for Logon Credentials

Everytime I open VS2010 and or attempt to connect to Team Foundation Server it asks for my credentials. I've done some extensive searching for this problem and its solutions (including this website) and none of the solutions work. Upon attempting to connect to Team Foundation Server in VS2010 I get the following error:
"TF31003: Either you have not entered the necessary credentials or your user account does not have permission to connect to the Team Foundation Server at ... Click the Use different credentials link below, or ask your server administrator to add the appropriate permissions to your account..."
I've done the follow:
Added a Windows Credential with the TFS Server name, user name, and password. Added logon credentials in "Stored User Names and Passwords" with the TFS Server name, user name, and password. Gone to the TFS Web Access URL, entered my logon credentials and clicked the remember my logon information (which stores it in "Stored User Names and Passwords"
So far, I can get into my TFS server via Internet Explorer without having to re-enter the logon credentials, but visual studio still keeps asking me for them.
I use Visual Studio 2010 Ultimate Edition on Windows 7.
Anyone have any other possible solutions?
Thanks.
I'm not entirely sure why you're getting the error, although I suspect there is a configuration issue on the machine hosting the TFS server. I'd verify that your user settings are correct.
As far as Visual Studio constantly asking your for credentials, I've had success with the method outlined in this blog post:
http://coolsubhash-tech.blogspot.com/2010/02/how-to-avoid-recurring-tfs-login-from.html
Make sure to add the domain part to the user as well as Visual Studio can be quite strict when it comes to these user names. If the domain is not there, you may see these issues.
I had exactly the same problem and the following link gave me the clues how to fix the damn thing.
You need to absolutely get rid of this abomination called "enchanced IE security". In 2008R2 this is done in server manager ("Configure IE ESC")
Go to IE and make sure your TFS server is in "local intranet" zone. If necessary, alter the defaults. I personally added my company's default domain (*.mycompany.local) to the list of intranet hosts. This also will help you with step 3
This step is crucial: many organizations put an alias to TFS server to point to something else, such as you are supposed to connect to tfs.mycompany.local, but really it goes to tfs99xyz50.domain.something.something.local. Easiest way to save creds for this kind of configuration is to open the TFS server URL in IE. IE will prompt you for creds and allow saving them, and you're done.
3a. If you are accessing TFS via proxy, also repeat the step 3 with proxy address.
What helped for me was to clear the IE cache and then connect to TFS again

Resources