I am trying to import a process config to an existing project via commandline power-tools, but everytime I try importing I get an access denied error, but i surely have access to the path.
Does anyone know, what I could be doing wrong?
Unfortunately you can't download all of Process Template in one go.
Although you are looking to achieve this through WITAdmin utility, however,
you can also download them by using the following screenshot.
There are couple of things we need to check here.
Run your Application as "Run as Administrator" and see if this resolves this issue.
Check if you belong to TFS Administrator Group to ensure that you have valid permissions.
I am currently running WITAdmin utility from the following location (VS 2015 + TFS 2015 Power Tools) and never came across any issue.
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\witadmin.exe
Additionally, you can post some code to understand how you are doing it.
Related
I got an issue with the tfs.
Firstly after my tfs server database got full.
So in order to solve it i cleared the table of logs from tfs server.
Now at time of clearing data one of my workspace had checkout of one file. As soon i finished my clearing data, it is giving me this error TF30063: You are not authorized to access Microsoft-IIS/8.5. at every time i try to get latest version.
Thats how i am unable to take latest.
Any help would be appritiable.
Right-click solution
Get Latest Version
Try commit again
Issue started for me when I upgraded to VS2017
For me it helps if i just click the Refresh button at the top of the Team Explorer.
After that, the message disappears and i can normally check in.
For me, it helped just to restart Visual Studio.
Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache.
Clean the Cache folder on Server machine. The folder path is: C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services_tfs_data
After cleaned, on Server machine, click Start and select Run… to open the dialog box, then input iisreset.exe and click OK, wait it run completely.
I just reconnected to the team project in the Team Explorer and my commit went through, didn't have to restart anything.
I had the same issue. When I closed an open Source Control Explorer window and all the files in Visual Studio, I was able to check in.
I think i got solution, exactly got that how to do.
Do checkout that file and check in an old version of that file
and
than do take latest.
It will not generate this error again.
If you can get a copy of the file that is on TFS you can add it as a new file to TFS, and then do get latest version of the file, and then select keep local when you get the conflict error, and then you can check in the file. After that you can then get latest with no errors.
For me, Run as Administrator from Visual, It will never make this error again.
1 : Open TFS window.
2 : Click on Refresh(F5).
3: Try again to Check-in.
CLick here see Solution (Image):
I have faced same issue while check-in on TFS : You are not authorized to access Microsoft-IIS/10.0.
Using Visual Studio 2017 Enterprise with the latest update installed v15.2 (26430.4) on Windows 10 64-bit. The issue has been happening for awhile, it is not new with the latest VS update. We're using a TFS repository hosted on Visual Studio Online, i.e. our TFS repository is at COMPANY.visualstudio.com.
Frequently, when checking in, or attempting to shelve changes from the Team Explorer window in VS, I'll get an error message indicating I'm not authorized to access Microsoft-IIS/10.0. I've had reports of other developers experiencing this as well.
We've discovered the following workarounds.
Clicking the refresh button on the top of the Team Explorer window and then trying the operation again
If you have multiple workspaces, changing to a different one, then back to the original, then trying the operation again
It appears something is "stale" perhaps with the TFS connection and that refreshing it prevents the error message.
Hitting the refresh button over the Team explorer, resolved the issue.
I had a locked item. When I excluded/undo the locked item it went through.
Refresh TFS not worked for me
In my case the error disappear restarting Visual Studio
or me, it helped just to restart Visual Studio.
I am using Microsoft Visual Studio Installer Projects to make a setup file for my C# app and when I install my app it says:
Failed to update database because the database is read-only
Here is screenshot of my database in Microsoft SQL Management Studio that shows read-only is false.
Here is screenshot of my database file in installer that shows read-only is false.
Yet after installing my app I get error above.
Any idea?
Solved
While comments above were helpful but easiest solution for me that didn't require lots of editing and coding was to change Application Folder path to outside of Program Files (86) folder something like this
C:\[Manufacturer]\[ProductName]
Here is screenshot of where to change that path and everything works fine now
Now it will install on path like C:\My_Company\App_Name where there is no permission restrict for system to access database file.
I have a new .net Core 2.0 Web API project (In Visual Studio 2017 Version 15.3.5) where I can´t build the solution if I add a new database project.
error MSB4019: The imported project "C:\Program Files\dotnet\sdk\2.0.0\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I have tried all kinds of solutions
Installed almost everything missing from the Visual Studio Installer
Installed Visual Studio Build Tools 2017
Repaired Visual Studio
Without luck I tried to find Microsoft.Data.Tools.Schema.SqlTasks.targets file on C:\ to the add reference to it in the project file (I then don´t know if that works while building the solution in VSTS).
So why can I add a database project to a normal API project and everything works just fine but not to a .net core one?
Do database projects not work with .net Core? I have searched for information on this but sorry I just can´t find it.
I´m not sure what to do. Hope somebody can help.
Ok I managed to find the Microsoft.Data.Tools.Schema.SqlTasks.targets file on my computer.
I then needed to unload the project and edit it
There I changed this line
<SSDTExists Condition="Exists('$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets')">True</SSDTExists>
to the hardcoded path of my file
<SSDTExists Condition="Exists('C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets')">True</SSDTExists>
And now it builds on my computer and on VSTS.
But why this is like this I don´t know.
I was having the exact same issue building a SQL Server project on an Azure DevOps CI/CD pipeline, and locally on VS Code. On Azure DevOps none of the pre-built build tasks would work for me, and locally I could only compile the SQL Server project on Visual Studio, which was annoying. Your solution didn't work for me, after doing what you suggest, I would get a .dll missing error, related with the first error.
I solved this by avoiding to add a SQL Server project to the solution.
I achieved this by using an MSBuild SDK, capable of producing a SQL Server Data-Tier Application package (.dacpac) from the set of SQL scripts. By adding this second project to the solution, I managed to continue taking advantage of linking the project to a live database through SQL Server Object Explorer on Visual Studio. I gave a more detailed explanation about my implementation in this answer.
Please pardon a newbie's question about MS TFS and Visual Studio 2012, I hope I'm using the correct vocabulary.
Our shop has recently moved to MS TFS and Visual Studio 2012 to build internal web services for integration. Currently we have a TFS 2010 Server running on Server2008R2 and a Build server on a Windows 7 box, our dev application server is also running Server2008R2. I have been given the job of getting a nightly build and deployment running. I have the build definition working but the deployment portion is not functioning. I have installed Web Deploy on both the dev application server and the build server as per these articles:
http://www.kevingao.net/version-control/how-to-auto-deploy-web-application-with-tfs-build-server.html
and
http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
We have configured an user, web_deploy_dev in active director and that user is a local admin on the dev app server.
The parameters added to the build definition are:
/p:DeployOnBuild=True
/p:DeployTarget=MsDeployPublish
/p:MSDeployServiceURL="https://PA-APPSRV1-DEV:8172/msdeploy.axd" /* double quotes not in original code */
/p:DeployIISAppPath="DW/DWServices" /* E:\Webroot\DW\DWServices */
/p:CreatePackageOnPublish=True
/p:MsDeployPublishMethod=WMSVC
/p:AllowUntrustedCertificate=True
/p:UserName=migp\web_deploy_dev
/p:Password=******
I suspect that MSBUILD is not even calling msdeploy.exe as I see no errors in the windows event and application logs, but I do not know all the places to look. I can use a web browser and connect to the service on the dev app server as the web_deploy_dev user from the build server, I receive a web page not found error after inputting user name and PW, but I assume that is to be expected.
I am at a loss as to where to look next, I've tried searching the web but nothing I try seems to work.
Thank you in advance for your help and input.
Roy
It sounds like you are experiencing a problem where your build completes and claims success, but you aren't getting any error and nothing is actually deployed. When I've experienced this with my TeamCity build server, the problem was that MSBuild was not set up on the machine that would do the building and deploying. These are my steps to resolve the problem I think you might be having:
Make sure that at least Visual Studio Express is installed. you can tell if a full enough version of Visual Studio is installed by navigating to the
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\ directory. If you see folders like 10.0, 11.0, or '12.0', look inside them and verify that there is a Microsoft.WebApplications.targets file. Note the versions that pass that check.
In your Build Configuration, add a /p:VisualStudioVersion=12.0 or whatever version of Visual Studio is appropriate.
Let me know if this gets you anywhere or not. I'm really curious to hear if you are finding any errors or logs anywhere. Basically, in my experience using Web Deploy and MSBuild with TeamCity, if the machine that is building and deploying doesn't have the MSBuild installed with the Microsoft.WebApplication.targets file, it silently fails.
I created a new work item type, i'm trying to import it in my tfs 2012 project but i'm getting an error TF237090: Does not exist or access is denied. I can succesfully import an existing workitem after changes but not a new one.
I tried this in VS2012 by importing WIT via the Dev Studio Tools->Process Editor->Work Item Types->Import WIT. If I recall when I ran into this issue before it was because someone had the a work item open (in this case it was a test case).
Summary
Ensure that the version of witadmin being used for import & export of WITDs corresponds with the TFS Server version
Ensure that the version of the MS VS TFS Power Tools being used corresponds to the TFS Server version
Background
I have multiple versions of Visual Studio installed, including versions 2012 (v11.0), and 2013 (v12.0). However, our TFS Server version is 2012.
I had this problem when running witadmin importwitd from the command line. It seems that the tools used to export and import the Work Item Type Definitions (WITDs) need to be the same as the TFS server version. Hence, when running from the command line, for running with TFS 2012, the witadmin command should be run from the C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE directory, not the v12.0 or any other version.
Once I realized that I may have been trying to import a WITD XML file that had been exported from a different witadmin version, I re-exported (from the server) in the correct version - use witadmin exportwitd - then made my changes, and re-imported.
One annoyance is that the Work Item Type Editor for 2012 didn't seem to care that the XML WITD file that I imported came from a different version.
Insight gained from here: http://social.msdn.microsoft.com/Forums/en-US/399b4c50-fbaa-43f6-a0f5-88129f9b2ed8/tf237090-does-not-exist-or-access-is-denied-when-usint-witadmin-importwitd?forum=tfsgeneral
In my case, I was able to change the Task WIT template of a particular project using TFS Process Template Editor Extension in Visual Studio 2017, but when attempting to change another project it was failing with message:
Microsoft Visual Studio Failed to save the 'Task' Work Item Type to the server.TF237090: Does not exist or access is denied.
I am a member Project Collection Administrators (at higher level - collection) and I had most of the permissions needed to perform most of the changes required, including Team Admin ('Team Project Name' Team - Administrators).
Turns out that I was not part of the 'Project Administrators' within that particular team project. All I had to do was to navigate to the Admin area, under Security tab of that particular project and add my username to the Project Administrators group.