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.
I'm setting up an asp.net server for school and I am getting ERROR_USER_UNAUTHORIZED.
I have looked over the internet and everyone says that it has to do with not being administrator or not having access to the site. I am just getting confused. I added the user to the local administrator group. added him to iis manager permissions and to IIS manager users in like 3 different ways (same user different type of name, with server/name, name, iis manager user name).
Man I am just trying to publish to this server and I've been at it for like 5 hours (not that much but still I havent gotten any further at all).
To give some more detail:
I setup a publish profile in visual studio, correct host, username,password,site name and I think correct url (we have no dns setup yet so its just the ip of the server). INTERESTING PART HERE (I Think) when I click validate connection it works correctly (in edit) but when I publish it gives the error stated above. Also when I change https to http in the url it makes the error ERROR_USER_NOT_ADMIN, which the user is... .
To summarize, I have no clue what I am doing please help me god.
Take as long as you want to, I just want to get this done.
Check if you open VS with administrative right?
I forgot to mark this as solved and post the solution.
Apparently the solution was that I didn't mark the folder(inside the site in iis manager) as an application.
Solution is simply, open iis, select the server, select the site, right click the main folder with all your stuff, click mark as application.
I couldn't find this anywhere on the internet or on the help page it shows but it solved the problem. (litterally just started to turn insane a bit after trying stuff for 5 hours so stopped and went at it again next day and solved it in 5 minutes).
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.
I'm trying to access to TFS but it doesn't let me.
In my personal PC I open the Remote Desktop, then I proceed to connect to the server where is located the Team Foundation Server. Then inside the server, I go to the Google Chrome and try to sign in to TFS but it just asks me my credentials over and over again saying that I have to provide valid credentials to have access to the TFS.
This is the same if I try to log on from Visual Studio so, I don't know what is going on...
But if I try to access from my local machine, I mean, not from the server, I can properly enter with my TF credentials. Do any body knows whay is this happening?
I hope you can help me.
Thank you!
Thanks everyone for answering my question.
I've found the issue.
The problem was that I tried to access specifying the tfs like this
tfs.site.com:8080/tfs/collection
but it was wrong. Been at server I just had to specify the url like this:
tfs:8080/tfs and that's it.
I can now access correctly to my tfs from server.
Again thank you everybody for our time.
Cheers.
I would try to disable the Loopback check (see this page for an example).
When I am making changes on my localhost, it is not working. I am on windows 7 but when I copy the file in which the changes were made, and try to execute them in Windows XP, its working. I as I asked someone who has a lot of knowledge on this and they said it is a configuration issue.
Someone else told me it was because of output caching, so I disabled everything and tried, even then there was no response. Can anyone tell me how do I go about it?
This was because of caching issue.
Navigate to Control Panel\All Control Panel Items\Administrative Tools\IIS Configuration Manager, select Output caching, then add new rule with follow parameters:
Insert types of files, you are changing(.aspx,.php) in File name extension field and simply unselect all types of caching. Then restart server and it should work now
I could hardly understand your word, so I think your very first task is to make sure you understand IIS and how to start troubleshooting.
Without a clearer description on the problem, nobody can provide you useful information on how to resolve it.
If you like, open a support case with Microsoft support team and talk to the support engineer about your issue.
http://support.microsoft.com