I am getting the following error
You cannot delete vault BuildServerBackup because it contains registered servers. Delete the servers and the restore points for the server data, and then delete the vault."
But when i click the Register tab this is what it says
You haven't registered any servers yet. To get started, download the appropriate agent and use it to register your server with the recovery service."
So how do i find out and delete all the associated server ?
You need to remove the registered Windows server before you can delete the backup vault. Here are the instructions to delete registered server(s)
Goto Azure Portal and select your backup vault
Select "Registered Items" from top menu Select the server type.
In the Drop down item next to the word TYPE Select Windows Server for Windows client machines and click the tick button on the right
Select the server and click Delete button in the bottom action bar.
Hope that helps :)
Related
I have an on-prem machine for DB2 connectivity to ADF where SHIR is installed, and I have been provided with the certificate zip file.
How to use SSL certificate for linked service of DB2 in data factory and how to get that certificate common name for linked service.
enter image description here
https://learn.microsoft.com/en-us/azure/data-factory/connector-db2?tabs=data-factory#create-a-linked-service-to-db2-using-ui - following this but nothing in detail has been shared on how to setup SSL for source machine.
The procedures below must be followed in order to utilise an SSL certificate for a DB2 connected service in Azure Data Factory:
You should extract the.pem file from the given certificate file by unzipping it.
Go to the "Author & Monitor" area of the Azure Data Factory, and then click the "Author" button.
Click the "Author & Monitor" button on the left-hand menu.
Click the "Linked services" button in the "Author" section before selecting "New."
As the type of connected service you wish to build, select "DB21."
Fill out the appropriate data on the "New Linked Service" form, including the server name, port number, and username/password.
Select the "Certificate" button after selecting the "Enable SSL" checkbox in the "Advanced" section.
Click the "Add" button in the "Certificate" dialogue box and then navigate to the location of the.pem file that you retrieved in step 1 before clicking.
The Common Name (CN) of the certificate will be automatically filled in once you've chosen the file.
To build the associated service, click "Finish" after clicking "OK" to exit the dialogue box.
The SSL certificate should now work with your Azure Data Factory linked service to connect to your DB2 source machine.
In the last 6 months I have been releasing with a pipeline in Azure DevOps, but today I receive the following error:
2019-09-25T14:24:38.4296875Z ##[section]Starting: Azure App Service Deploy: AS-ServiciosNegocio-API-UAT
2019-09-25T14:24:38.4419797Z ==============================================================================
2019-09-25T14:24:38.4419900Z Task : Azure App Service deploy
2019-09-25T14:24:38.4419986Z Description : Deploy to Azure App Service a web, mobile, or API app using Docker, Java, .NET, .NET Core, Node.js, PHP, Python, or Ruby
2019-09-25T14:24:38.4420053Z Version : 3.4.31
2019-09-25T14:24:38.4420117Z Author : Microsoft Corporation
2019-09-25T14:24:38.4420182Z Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-rm-web-app-deployment
2019-09-25T14:24:38.4420291Z ==============================================================================
2019-09-25T14:24:39.1630446Z Got connection details for Azure App Service:'AS-ServiciosNegocio-API-UAT'
2019-09-25T14:24:39.3091141Z ##[error]Error: Failed to get resource ID for resource type 'Microsoft.Web/Sites' and resource name 'AS-ServiciosNegocio-API-UAT'. Error: Could not fetch access token for Azure. Verify if the Service Principal used is valid and not expired.
2019-09-25T14:24:39.3140156Z ##[section]Finishing: Azure App Service Deploy: AS-ServiciosNegocio-API-UAT
If your existing service connection is the "Azure Resource Manager using service principal (automatic)" type (not manual), there's a simple but non-obvious way to renew the token.
Go to the service connection's settings page in Azure Devops as described in the other answers. (<YourDevAzureProject> Bottom Left → ⚙️ Project Settings → Pipelines subhead → Service Connections)
Click Edit and then Save without making any other changes. Assuming you have the right permissions, it will automatically get a new token.
NB: for some browsers you must enable pop-ups on dev.azure.com as it attempts to login to your azure account to get a list of resource groups.
(Figured this out from this forum comment.)
From reading others' comments/posts on this thread, the Azure UI might have changed so I'm posting the steps here for the later comers. I did what ecraig12345 suggested and it worked great!
Go to the deployment pipeline where the error occurs and click on Edit
Go to "Run on agent" task > Deploy Azure App Service
Click on the Manage hyperlink next to Azure Subscription label (see screenshot below)
Click on Edit
Click Save
Steps 1 - 3
Step 4
Step 5
If you look at the error message: "Verify if the Service Principal used is valid and not expired"
While I would have preferred more information, purely based on the above the likely scenario is the Key Used for the Service Connection has expired.
Visit you Azure DevOps org. and open the related Project and click on "Project
Settings" at the bottom left of the screen.
Click edit on the service connection in Azure DevOps and Click on the
link >> "To update using an existing service principal, use the full
version of the service connection dialog."
Copy the "Service principal client ID"
Now in the Azure Portal, Clic on Azure Active Directory and then Click on "App Registrations" to search for your application with the "client ID"
Go to "Certificate and Secrets" and check if your client certificate has expired.
If the cert is expired generate a new one and copy the key.
Go back to Azure DevOps "Service Connections", Click edit on the service connection in Azure DevOps and Click on the link >> "To update using an existing service principal, use the full version of the service connection dialog."
Update Service Principal Key with the copied value, Verify connection and click ok.
This should solve your issue
Although the route to the problem wasn't exactly the same (because devops changed so much again, probably), the answer from Venura was the root cause of my issue, and I was able to solve it thanks to this info.
steps I had to take:
In devops: go to releases
click correct project
edit
click on the stage that was failing
open the run agent task to deploy (should be an azure app service deploy)
click manage azure subscription
click manage service principal
in azure portal click on the expired registration
click on the red error that is has expired
click + new client secret
copy that new key
go back to devops
click edit on the screen of service connections (where we left at step 7) - (the subscript of the title here is Azure Resource Manager using service principal (manual))
paste that copied key in the field 'Service principal key'
click 'Verify and save'
That solved the issue, to confirm it was solved I just triggered a new release, which finally got through.
I followed JamesD's answer but when I got to step 13, there was nowhere for me to put the Service Principle Key that was generated. So I went back to square one and approached it a different way. Instead of trying to reuse the existing service connection that had exired, I created a new service connection and then changed my release pipelines to use that new service connection and things worked fine.
Here were my steps:
click on Project Settings in the lower left corner
On the left nav under the "Pipelines" section, click on "Service connections"
in the upper right corner, click on the button "New service connection"
select "Azure Resource Manager" and then "Next"
select "Service principle (automatic)" (this is the recommended option)
select the subscription from the drop down.
select the resource group from the drop down
give it a good name and hit save
then authenticate with your azure portal creds
Now you have a service connection created, lets go change the pipeline to use it
Go to your pipeline for the release and edit it
click on the Stage you want to edit (aim for the # tasks link)
click on Deploy Azure App Service
under the azure subscription drop down, select your new subscription entry you created above
then you will select the App Service name in that drop down
hit save and you are good to go
Now repeat for any other stages of the pipeline or any other failing release pipelines
Windows Server 2016, ADFS, Certification Authority
I tried to create duplicate web server template, but it says that it's not an accessible. see below snap.
Now, My client is not technical, he provide me an account with most of the access, account is not an administrator, but I can assign many access to my self using AD Administrative service.
My only question is which access DO I need to provide to this account for creating duplicate web server certificate template?
In a multi-domain environment, I have had the same issue, if I did not select a domain controller in the root domain, respectively in the domain that hosts the CA. In my case, another domain was chosen by the console, because my computer for remote administration is in another domain (child domain).
Try the following:
Open "Certificate Template Console"
Right-click "Certificate Templates" in the left pane
Click "Connect to another writable domain controller ..."
Change the domain
click "Ok"
Try to duplicate once again. :)
I know this is an old thread, but thought I might add a fix that could help others. The account you use to login to the CA server should have Enterprise admin rights and should also be a member of local IIS_IUSRS group. If you have verified both, just logout and login to the box again and you should be able to duplicate a template.
I am currently using Tableau for my reporting module. However, I have several issues I need answered. I tried the following; please comment if I am on the right track.
I want to embed Tableau generated report to my website, so I used Javascript API. My data may come from Tableau Online (Cloud Server), or Tableau Server, for now I used Tableau Online.
Now, I have to create my report so I used Tableau Desktop to create how my report would look like. Tableau Desktop can connect to my local DB for get data.
Then, I published my workbook to my server . However, in Tableau Online, I need to data connection which fails since I don't have a live server.
I downloaded Tableau Server but I can't proceed since in configuration it want an Active Directory credentials.
I haven't done any output, I think I am stuck. I would welcome some input.
Tableau supports both Active Directory and Local Authentication Mode. We have tableau server running in local authentication mode but however its not highly advisable to run the server in local authentication.
If you have installed tableau server in active directory mode, reinstall the server. During your reinstall select local authentication as the default authentication. Once you have installed it, you need to add on Administrator Account.
Another workaround is go to All Programs > Tableau Server > Configure Tableau Server. In General Tab, you will be having the User Authentication. Try changing it if its enabled. If its disabled you need to reinstall tableau.
below are the steps to reinstall tableau server
Back up and remove Tableau Server
When Tableau Server has been uninstalled, open Windows Explorer and navigate to C:\Program Files\Tableau.
Delete the Tableau Server folder.
Navigate to the C:\ProgramData\Tableau.
Delete the Tableau Server folder.
Reinstall Tableau Server and restore the backup
Install Tableau Server. This step will allow you to set a new authentication method.
After installing Tableau Server, a browser window will display and you will be prompted to create a new administrator account. Ignore this, and close the browser window.
After restoring your backup file, a browser window will display and you will be prompted to create a new administrator account again. Ignore this, and close the browser window. If you are prompted to type in the Run As user password, type the password and continue with the next step. You will not see a password confirmation.
In the Command Prompt window, from the Tableau Server bin directory, type the following command to reset Tableau Server back to a state that requires an administrator account to be set up:
tabadmin reset
Open a browser window, and type http://localhost in the address bar to set up the administrator account for Tableau Server.
I may have assumed that when you say Tableau Online, you dont mean the Tableau Public..
I assume your tableau online is your local or let's say company hosted tableau server...
for the answers to your questions in sequence
1 - 3 it can be done.
tableau supports a lot of datasources even the classic text based data it can read..
did you tried installing your database drivers?
If the server is configured to use local authentication, when you add
a user identity, you specify a username, a password and a site role.
In that case, the Tableau Server repository is used exclusively to
authenticate the user.
http://onlinehelp.tableau.com/current/server/en-us/security_auth.htm
My build agents are not starting after I change the properties credentials to the domain account from the network service. I done this because the network service account cannot write to my drop folder.
Each time I add the network service to the drop folder share, it appears then disappears.
http://msdn.microsoft.com/en-us/library/bb778394.aspx I followed this but some steps are different, i have xp and it doesn't show the share tab so i go through security tab
So I guess I'm asking two questions here;
Agents are not starting after changing credentials.
Network service not able to write to the drop folder.
Thanks in advance
Yes, Network Service won't have permissions to write to a drop location. That's pretty standard. You need to be using a domain account.
The TFS Build Service will need to run as a domain user so it can write to the drop location.
The domain account for the build agent will need to be in the TFS Project Collection group for build service accounts (internal to TFS). I can't remember what it's actually called but you need to be a collection administrator to update it.
The domain account will also need some login as batch/service permissions but that should be done automatically when you reconfigure the service. Do you use the TFS Admin console to reconfigure the agent or did you just set the credentials on the service? (You should use the TFS Admin console).