I have problem with deleting Sync Agent in Azure.
My approach was trying to delete first Sync Agent on on-premise DB and then in Azure. However when I tried delete it, it failed with error ”Please enter a valid agent key to proceed. The key must be generated from SQL Data Sync web portal” For solution I tried (duo to help from stack) set same timezone on Azure and on on-premise DB, but without success.
Any advice please?
Thanks
Related
I am getting this error. How I going to solve this. Some configurations are disabled and inactive. Please help me. Thank you.
Also when connecting the Microsoft Azure Active Directory Connect Provisioning Agent Configuration. Its say that error. Please see images.
Provisioning Agent cloud sync keeps track of the condition of your configuration and quarantines any unhealthy components. Whenever calls sent to the target system continually fail on invalid credentials.
To resolve this issue:
You can clear the quarantine and restart the provisioning job like below:
You can view additional details regarding the quarantine by selecting the status and the error code message also will display.
To restart provisioning job, click on your domain -> edit cloud sync configuration and -> Restart sync.
we encountered an unexpected error when registering the agent please try again
When you deploy the cloud provisioning agent, you may receive an error message. Generally, the agent's unable to implement the PowerShell registration scripts is what causes this issue.
Try to change PowerShell execution policies make sure local machine and user policy should be RemoteSigned or Undefined
If still error persists you can repair the cloud sync service account using below cmd:
Install AADCloudSyncTool Connect-AADCloudSyncTools , Enter credentials
Run Repair-AADCloudSyncToolsAccount
Reference:
Azure AD Cloud Sync Highlights and Deployment (misconfig.io)
I want to download ADLGen2 file to my local server using ADF.
I tried to set up self hosted integration run-time, but I am getting below error
the integration runtime (self-hosted) node has encountered an error during registration
The account through which I have logged into my azure portal and the account which has access on my local machine are completely different.
Azure Portal login : xyz_abc#gmail.com
Local machine login: officiallogin#companyname
Is the issue because of 2 completely different logins
Can you please let me know how to resolve this issue.
Thanks,
Raksha
When you say "The account through which I have logged into my azure portal and the account which has access on my local machine are completely different", make sure to uninstall and re-install the self-hosted integration runtime manually choosing the option2.
OR
You may try to uninstall the current self-hosted integration runtime. Maybe you can try the Option1. It will install and register the integration runtime automatically.
Reference: Create and configure a self-hosted integration runtime.
Background: We have an azure DevOps pipeline that we use to automatically deploy a webapp we maintain to an azure test instance.
This suddenly stopped running today with the following error.
TF24668: The following team project collection is stopped: ***********. Start the collection and then try again. Administrator Reason: abuse
where *********** is our project name.
It fails instantly when this happens. It doesn't appear to do anything else other than throw this error.
The developer who initially got the pipeline set up is no longer with the company.
I've looked through the DevOps interface, and I can't find what it means by this "project collection", and I can't find out how to start it.
Any ideas where I should look?
If you are using Azure DevOps Service. This is a known issue on Azure DevOps, Microsoft Product Team has fixed it and all hosts have reboot, you could try it again and then kindly share the result here.
If you are using Azure DevOps Server, you should open Azure DevOps Server Administration Console->click the tab Team Project Collections->check the collection and ensure the state is Online, then try it again.
Note: If you do not have enough permission to do this, please contact the collection administrator to check it.
I faced the same and reported an issue on Microsoft Developer Community and got the following response
We had some bad actors using our MS-HOSTED pipelines pools in ways they should not have been, and we blocked them in order to maintain the stability of Azure Pipelines.
Full response can be found here
This ended up being a bug with azure that they fixed within a few days
See https://developercommunity.visualstudio.com/t/Azure-Pipelines:-errorTF24668:-The-f/1239940
As stupid as it might sound there is an Azure DevOps Dashboard that states health of Azure DevOps services. I got his error on Wednesday where status of pipeline service in my region was marked as degraded. On Thursday status changed to healthy and my pipeline works!
I have the next error when I deploy a Sql Database Project with Appveyor to Azure:
Error publishing database: Could not deploy package. Unable to connect to master or target server 'ods'. You must have a user with the same password in master or target server 'ods
So, in this article Can't deploy Sql Database Project to Azure recommend add to Azure SQL Firewalls all the ip address allowed for Appveyor, but I still received the same error , what other thing may cause this issue?
I hope you have created your Azure SQL Database logical server as explained here, please use the "Server Admin Login" credentials on your connection string. It seems Appveyor requires access to the master database and the Server Admin Login has all required permissions.
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.