I have a problem with exporting and customizing work items in Azure DevOps
when I try to export work items I get this error "The feature is disabled. Contact your Azure DevOps Server administrator. process ID x Project ID x."
I'm the only user in azure DevOps
I tried with tftp tools and witadmin command and both errors were the same.
can anyone help me
Notice: I use Azure DevOps On-premise
when I try to export work items I get this error "The feature is
disabled. Contact your Azure DevOps Server administrator. process ID x
Project ID x
To achieve the above requirement ,
As you are user,
First of all you need to have an administrator permissions to your project.
Then we can export the project .
Based on this Prequisite as described on MS DOC well: -
To get those permissions you can refer this MS DOC.
For more information please refer this MICROSOFT DOCUMENTATION
Related
I use Azure DevOps in order to make continuous integration (CI). I would like to push the binaries (artifacts) to a one drive sharepoint folder whose url is like this : https://foo.sharepoint.com/personal/bar/_layouts/15/onedrive.aspx .
Thank you very much for your help !
I make some research and i attempt to do it with microsoft graph. But i don't understand how to make url....
I see also that many of customers like me want to do this : https://developercommunity.visualstudio.com/t/onedrive-support-for-devops-pipeline-release/548731.
I saw that it is possible to do this with a powershell script. But i don't know at all how to manage all this mess !
I suppose that you could follow this document for Continuous Integration and Continuous deployment using Azure DevOps
After you create the artifacts, you could follow the steps below to publish it to share point in a Release Pipeline.
1.Adding a stage.
2.Install the Node.JS tool in your stage with node.js installer with the version 10.x.
If your project is based on SharePoint Framework version 1.7.1 or earlier, use version 8.X.
3.Installing the CLI for Microsoft 365.
Add a npm task, select a Custom command and type install -g #pnp/cli-microsoft365 in the Command and Arguments field. Learn more about the CLI for Microsoft 365
4.Connecting to SharePoint Online
Before using the App Catalog in your deployment environment, you first need to authenticate against the App Catalog of your tenant. To do so, add a Command Line task and paste in the following command into the script field m365 login -t password -u $(username) -p $(password).
note
If you are using CLI for Microsoft 365 to connect to your tenant for the first time, you need to perform an interactive logon with the account first. This is required to grant access to PnP Office 365 Management Shell application which is used by CLI for Microsoft 365 to access your tenant on the account's behalf. Your task will otherwise fail to logon non-interactively. Details available on CLI for Microsoft 365 User Guide.
5.Adding the Solution Package to the App Catalog
Upload the solution package to your App Catalog by adding another Command Line task and pasting the following command line in the Script field m365 spo app add -p $(System.DefaultWorkingDirectory)/SpFxDevOps/drop/SharePoint/solution/sp-fx-devops.sppkg --overwrite
The path of the package depends on your solution name (see your project configuration) as well as the Source Alias you defined earlier, make sure they match.
Note
You can upload a solution to a site collection app catalog by adding --appCatalogUrl https://$(tenant).sharepoint.com/$(catalogsite) --scope sitecollection
6.Deploying the Application
The final step in the setup is to deploy the application to the App Catalog to make it available to all site collections within the tenant as its latest version. Add another Command Line task and paste the following command line in the Script field m365 spo app deploy --name sp-fx-devops.sppkg
Note
You can deploy a solution from a site collection app catalog by adding --appCatalogUrl https://$(tenant).sharepoint.com/$(catalogsite) --scope sitecollection
I am trying to release multiple projects in 1 solution using Azure Release pipeline
They are all connected to the same Azure Subscription, but some do deploy to the given app service while others give an unauthorized error.
Ive looked into it and i read that adding website_webdeploy_use_scm to the app service should help the Unauthorized error, but this didnt help for me.
What else could i look at? I connect through Azure Devops so i just selected the subscription from the list it automatically gathers from Azure because im logged in using the same logins as i use for Azure Portal
the full error is:
Connected to the remote computer ("xxxx.azurewebsites.windows.net") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
Error: The remote server returned an error: (401) Unauthorized.
according to the error I'd suggest you check service principal permissions. it probably lacks the permissions required to manage those webapps.
So after refresh publishing profile in Azure Portal and trying it again it fixed itself so im not sure if that caused it or not but it worked!
another fix is to delete the slot and make it again
I'm trying to create a build in Team Services (Visual Studio Online) but am having a few issues.
My first step is to create a new build and I've selected the template Deployment -> Azure Web App
Then in the build step for Azure Deployment I need to select my Azure subscription. This list is currently empty so I select Manage to add a new one.
Following the instructions here I try to add a new endpoint but it says to select the one called 'Azure' but in my list I've got 'Azure Classic' and 'Azure Resource Manager'. Which one should I use?
I've tried 'Azure Resource Manager' and used the details to generate service key etc using the Powershell script as said in the previous link. Now the status just stay at 'Connecting to service using Service Principal' and is not selectable in the list.
How do I get Team Services to see my Azure subscription?
I must say, I've found the documentation for this a bit lacking in that a lot of the Microsoft sites still use the classic portal or older versions for the sites.
Starting from the end of your question, one of the reasons of that is that some functionality is not available yet on the new portal. As far as i know, all of the functionality should migrate to the new portal in a future.
For Azure Web App, please add the New Service Endpoint using classic mode (and i prefer to do that using certificate - very simple). Then, when adding the web site as the build step (for example), select your added subscription and you should be good to go.
I am new to azure and i am trying to create a team project on portal.azure.com and its failing with below error.
The resource group is getting created but team project creation fails
Error:
{"Code":"InvalidRequestValue","Message":"TF400902: There was a failure executing the job. Job Id for the failed creation:b055035e-1b17-480d-a577-abce5d9aff75","Target":"GetProjectJobStatus"}
Reproduce your issue successful with my azure account.
It is not related to the free trail account. If your steps are accurate. (Please refer this blog: Create a VS Online Team Project from the new Azure Portal)
This may coursed by azure. Suggest you try again after several hours.
Update
Even though with this error, I received a successful email from Azure. Please also check whether did you get this email.
Does anyone know how I go about setting the Direct Reports of a Windows Azure Active Directory ( WAAD ) from the Azure Management Console.
I can create the accounts easily enough but there doesn't appear to be any tools to set anything other than very basic details.
Ideally I'd like to set the direct reports and manager, office and other details.
There isn't a quick tool available to do this. However, if you don't mind writing some code, you could spin up a comsole app that updates these properties using the Azure AD Graph API.
Update user's properties: http://msdn.microsoft.com/en-us/library/azure/dn151671.aspx
Update user's manager: http://msdn.microsoft.com/en-us/library/azure/dn151673.aspx
A sample .Net console app using Azure AD Graph API is here: https://github.com/AzureADSamples/ConsoleApp-GraphAPI-DotNet
Hope this helps.