Suddenly I'm encountering the dreaded "Your credentials did not work" error connecting to my VM. I've tried several different accounts, I've made sure of the password (I use a password management tool and the password used to work fine). I tried resetting it via the management console and I also tried resetting RDP via the console. Nothing.
The only thing that changed is that I rebooted the VM once.
Any other steps I can take to troubleshoot it? Is my only option to save the VHD and create a new VM?
you can reset you password using the steps given here https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-windows-reset-rdp/
Related
I installed the Azure Tools plugin (version: 0.0.4) for VSCode (version: 1.27.2). I have no proxy setting in my system. I validated it by running the command in cmd : netsh winhttp show proxy and found
Direct access (no proxy server).
I tried to login into Azure using the Azure Tools option present in the side bar, which caused a pop up to open at the bottom right corner. I clicked on the button with Copy and Open option which opened a browser instance where I copied the password details, post which when I came back to the VSCode window and then I see that I am still not logged in. I tried the above process multiple times but see the same again and again.
Can anyone help me to get some guidance on this to fix the issue?
I had a similar problem and for me was the latest Azure Account plugin version 0.9.10. It doesn't work.
I reinstalled the previous version 0.9.9 and now the login works again.
I can't reproduce it with Azure Account extension (0.4.3) for VSCode (version: 1.27.2).
If azure cli is installed, please have a try to use az login to check whether it can login. If you can login with az command then close the VS code and open it to try again.
I had a similar problem.
I am a member of several tenants for various orgs.
By updating my tenant Id in the Azure Account extension settings I was able to sign in.
I suspect I will have to update it when I want to work in a subscription owned by another tenant.
I ran into a similar issue when trying to login and extract an API from API management. Using Azure Sign In or Azure Login would open up the popup but the callback URL would not trigger a sign in VS Code. I tried everything to the point of reinstalling VS Code.
After messing around with the different Azure Sign In options, I finally got an error when trying to sign in to Azure Cloud. The error mentioned that my admin requires the use of a device code. Unfortunately this error is neither shown nor handled when using the default Azure Sign In command.
The fix for me was to expressly sign in using Azure Sign In with Device Code.
I can reproduce, It does not work on Ubuntu,
no matter what I do.
I gave up, and moved to windows.
So 1:0 for Microsoft :-)
If something does not work with Azure:
try with windows
try with Edge
Its painful truth - they only support software they already own. Which make sense business-wise.
I am not able to login my Azure VM. I have reset the password through azure portal but it is still not logging in. Previously, it used to log in and now it is showing following error :
An authentication error has occurred.
The function requested is not supported"
I have other VM which are logging in fine as before. Please help.
Check out the following link.
This is due to a combination of three factors:
You activated NLA on your target computer
The target computer is not patched for CVE-2018-0886
You enforced the Force updated clients or Mitigated parameters on the source computer
https://itluke.online/2018/03/29/solved-authentication-error-function-not-supported/
I have an Windows 8.1 VM on Azure that I've been successfully using for months. I login via the admin account that I originally set up.
Today my RDP sessions keep telling me that the password is incorrect.
So I used the Azure Portal to reset the password, but still can't get in. I've tried waiting for a while (in case updates were being installed) and I've restarted the machine.
I notice that the Portal UI says 'Provide a new user name for the built-in administrator account'. I've tried changing it with no luck.
Help?
Azure must have changed the username requirement.
It works if I login with host\username
Connect Azure RDP, "The logon attempt failed"
SOLUTION: instead of copy-paste, type the password
This solution comes from teh answer of another similar question Connect Azure RDP, “The logon attempt failed”. You can have a try.
I've recently changed the default BackupDirectory for a SQL Server 2008 R2 instane in the registry from I:\ to K:\ and since then whenever I try to backup or restore using SSMS I'll get an error
Cannot access the specified path or file
when I browse for the path.
It happens to the root and all folders in K:\. If I key in I:\ in the path and browse, there's no such issue. I've replicated the permission on I:\ and later added the service account for SQL and MSSQLSERVER to K:\ with Full Access. I've even tried adding Everyone with Full Access and it still shows the same error. I've googled around and find a lot of similar questions but no working solution for me. I've also tested master.sys.xp_dirtree on K:\ and no error. I've even tried procmon.exe but no indication of what went wrong
K:\ is the newly created pool in our SAN allocated for backups only. The SQL Server is part of a Windows 2008 R2 Failover Cluster. Both I:\ and K:\ is configured as SQL Server's cluster resources.
Fyi, I login to SSMS using a SQL Server account, since my machine is not part of the domain. But it was never an issue with I:\ to begin with.
EDIT: There's no error if I backup/restore with T-SQL, meaning the read/write permission for SQL Server for K:\ is correct.
I had this issue but realised that I was logging into the server (in SSMS) using SQL authentication. Once I hoped on the box as a local admin and then logged in with windows authentication to SQL server, I could see the files fine.
I has same issue and found solution on another post from SO. I moved my backup file to other directory and it worked. Solution can be found here.
I tried everything on the web, but none of them successed. Then, I installed some new feature to existing SQL Server (Data Quality and Integration Service) and finally I successed to select backup file from Restore Database menu.
It Because of no (sysadmin) Privilege for your login account to SSMS; mostly.
by this way:
Open Security > Logins > Choose your account "if Windows Administrator, use it"
right click, properties > Server Roles > then check on "sysadmin" or "dbcreator" if this account must have less or specific permissions.
"Take care" you've to use another account has "sysadmin" privileges to do this step because none allowed to give himself more privileges.
I had a similar issue, when new service account has been created for SQL server. To resolve this,Add the new service account to the local Administrator group on the back up server. This can be done by loggin into the server, then computer management->users and groups->Administrator.Double click administor and add the new service account created.
Every time we publish our Azure project (all machines in our team/at home as well) it always asks us to re-enter our RDP password.
This is a bit annoying as it means the files check out and we have to keep entering the password.
The error message is "The existing Remote Desktop credentials could not be loaded in this environment. Re-enter the desired password".
Anyone got any idea what is up? Its a bit frustrating.
Answer was because we were publishing to different instances with the same configuration and not using a fixed RDP cert. It was re-generating the certificate each time.
If you have this problem upload the cert to each cloud service you are deploying to and use the one cert across all deployments.