The last couple of days Azure Backup has been failing jobs with error 100023.
The encryption passphrase stored for this computer is not correctly configured. The encryption passphrase can be configured from the Windows Azure Backup Agent MMC snap-in. In the Action pane, click Properties and then click the Encryption
settings tab. Type the passphrase used for encryption of backups in the space provided.
I haven't changed the encryption password or location lately, so this is a bit unexpected.
At first I tought It may be an outage with Azure Backup itself but it's been a couple of days and still I'm getting the same issue.
I have since accessed the Backup Vault panel on manage.windowsazure.com and allowed re-registration for the affected server. However during the re-registration process I'm getting the same error.
Any ideas?
Download and update to the latest Azure Backup Agent (MARSAgentInstaller.exe) from the management portal at https://manage.windowsazure.com/
After doing so, try again.
This article can be used as a reference: https://azure.microsoft.com/en-us/documentation/articles/backup-configure-vault/#download-install-and-register-the-azure-backup-agent
The download page should look something like this (Windows Server agent highlighted in red):
Install the new agent from the Azure Site.
Delete the backup Jobs
De-register the server from the Azure Site
Uninstall Agent from the server
Download new registration certificate
Install Agent and point it to the new certificate.
Create a backup job and test it.
Related
We are using Azure Devops 2019 (App and data tiers are on different servers),We have done a domain migration due to which we had to change Devops URL from https:\Devops.OldDomain.com to https:\Devops.NewDomain.com
Below are the steps followed
Changed URL on IIS Devops Site and applied a third party certificate for https ( made sure certificates are added to trusted Root Cert)
Changed Public URL (changed the url to new Devops Url) from Devops admin console ( verified the access point from tbl_AccessMapping and updated it to new url)
Restarted the Devops server
Below are the issues identified
1)I have noticed build agents stopped working\offline and when I try to setup new agents, I see below
"An error occurred while sending the request.Failed to connect. Try again or ctrl-c to quit"
tried changing agent file to correct url (yet no luck)
2)When I launch Azure devops admin console I see below error
When I try to add Devops url from visual studio (Visual studio is installed inside Devops server) I see below error
"TF400324:Azure Devops services are not available from server, The underlying connection was closed"
Am I missing anything? I understand that some communication is missing between Application and Data tire, but I could not identify whats going wrong
Try to clear the following caches:
Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache
Delete the contents of the Cache directory, including all subfolders.
Regarding VS, close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService.
Reset IIS by pressing Win+R, and input iisreset in the Run.
We are evaluating Azure ASR for cloud Backup and Site Recovery.
Started a month ago with Backup services to backup files, folders and SQL servers and everything worked fine, MABS is installed in server A.
We have also added a physical server to Site recovery, installing the Azure site recovery on the same server A. Since then, every dashboard referring to Backup information has not been updated though its clear that GRS Storage is used for backups.
Tried to uninstall/re-install MABS without any success, any ideas? there are no errors in the MABS MMC console.
It is not recommended to install backup (MABS) and site recovery on the same machine since both Services are using similar tasks there will be lot of conflicts.
I have 2 web applications in azure on a Standard App Service Plan (S1 Standard).
After I finish a scheduled backup configuration, it returns to the backup blade and show the following message:
"Backup and Restore feature requires your App Service plan to be Standard or higher. Click here to upgrade your App Service plan and access this feature."
Also all the backup options are grey out.
But I have a standard service plan already...
Is there other requirement that I'm missing?
Sometimes if I keep refreshing I can access the backup configuration again, but when I try to configure the backup it never finishes loading the backup options (Storage account/Schedule/Database).
Is there a problem with the backup system?
I just created a Azure Web App in South Central US location and tested its backup feature. It worked fine on my side.
Is there other requirement that I'm missing?
No, what you did is right. The issue maybe a temporary problem of Azure backup service or caused by the cache of your browser. Please clear the cache or history of your browser and try your steps again.
I configured Windows Azure Backup on my VM hosted on Azure. I did manage to create and upload a certificate following this tutorial and this tutorial.
I downloaded the server agent to the VM and configured it, I then managed to perform a manual backup and it worked fine.
However I scheduled it to run every day at 3am using the wizard provided and it's not running. I check every day, and the last backup that is listed is the one I did manually. The dashboard in the Backup Server Agent shows it's scheduled, but it's not running.
I tried leaving the agent open overnight, and it didn't help.
Any insight on the situation will be helpful.
Thanks,
After checking my VM's event log, I figured out that the backup wasn't running as expected due to limited space in the HD. After I cleared some space it started running as expected.
So I setup TFS continuous deployment and I'm running into a situation where my build compiles just alright but fails in the deployment phase when communicating with Azure. My log looks like
Get Default Azure Cloud Service Publish Profile
Set Project to build CSPack
Run MSBuild for Project
Run Visual Studio Test Runner for Test Sources
Publish Output
Deploy application to Azure
8/23/2012 7:20:04 AM - Preparing deployment for rcfoapi with SubscriptionID: mysubscriptionidhere.veryverylong.andkeepsgoing...
8/23/2012 7:20:04 AM - Connecting...
An attempted http request against URI https://management.core.windows.net:8443/mysubscriptionidhere.veryverylong.andkeepsgoing
/services/hostedservices/myrolenamehere?embed-detail=true
returned an error: (403) Forbidden.
Additional Exception Information:
Error Code: AuthenticationFailed
Message: The server failed to authenticate the request. Verify that the
certificate is valid and is associated with this subscription.
Typically, a response of (403) Forbidden from a Windows Azure
Management API means that the X509 certificate used to
authenticate the call is not valid. The certificate may have
been revoked or expired. Reconnect your Windows Azure
subscription to your Team Foundation account.
I tried the 'Disconnect from TFS' link in the Azure portal, then verified that the certificate in the 'certificates' section of the Azure portal. I confirmed using the fingerprint hash that the same certificate is also in my local computers' certificate store ('my' store). Then I relinked TFS back via the Azure portal.
But I still get the same error. Any idea?
Update:
I also tried a few additional steps, nothing seems to be working :(
Deleted the entire cloud service
Created a new cloud service (with same name)
VS2012 deployed to the cloud service on both production and staging (because I need to service operational for front use and back testing)
Verified the Windows Azure Tools certificate in the portal's cloud service 'certificate' section (which matches my local copy). I understand this will be different from the one between TFS and Azure
Went to TFSPreview.com => top left gear => project administration => services => no linked services seen
Went to user profiles => connections => OAuth connection listed (MANAGE-PROD CLOUDAPP by Windows Azure) => removed it
Within the Azure portal, linked the newly setup cloud service back to TFSPreview.com
Locally in VS2012, disconnected TFS ('team' => 'disconnect')
Locally in VS2012, logged out of TFS ('team' => 'connect' => 'sign out' at the bottom)
Signed back into TFS, connected to the team project
Made a trivial change => check in => triggered continuous deploy
=> Same error as before :?
Thanks
TFS Preview is not using the same cert you have on your local dev box. When you connect the accounts Azure gives TFS a different cert and it is possible that is the one that has expired or is no longer there. If you have multiple projects connected to Azure the only option is to go into the admin site on TFSPreview (the gear in the upper right) and disconnect all projects that are connected to that subscription and then rerun the connection wizard. This will ensure we get a new valid certificate for your azure subscription. When you reconnect the subscription to the project we will find the existing build definitions and not create new ones.
I had the same issue and for me the solution was to renew the certificate. See here: http://support.microsoft.com/kb/2780289
This can happen if your certificate needs to be renewed in the Azure control panel.
It can also happen if you don't have a staging or production environment deployed first. I'm not entirely sure why since it deploys a new one, but this fixed the issue for me just now.