I am trying to connect to my company's TFS 2010 server from eclipse using Team Explorer Everywhere 2010 SP1.
I have successfully installed the plugin and am attempting to create the connection to our server through the "Add New Server" dialogue. Entering the server https://tfs.<ourServer>.com/tfs along with my Active Directory credentials creates the error:
Access denied connecting to TFS server... <server> (authenticating as <DOMAIN>\<user.name>
I can connect to this same server from Visual Studio 2010 without a problem using the same credentials, and I can also connect to the web client by browsing the the server using IE.
I have also used the command line tool to define a profile which appears in the Eclipse plugin but creates the same error.
Have I missed something obvious? Is there a setting on the TFS server I need to change?
I had the same issue but changing the Eclipse proxy to native solved the issue in my case.
Can you connect successfully if you use the URL of your Team Project Collection, for example:
http://tfs.mydomain.com:8080/tfs/DefaultCollection
Related
How can I add an external TFS Connection to TFS 2017 to allow it to connect to TFS 2013?
I navigated to http://tfsserver:8080/tfs/collection/team_project_name/_admin/_services?_a=resources and clicked New Service Endpoint. I selected External TFS
When I go to verify the connection after entering all the relevant information, I get the below error.
Failed to query service endpoint api: http://tfsserver:8080/tfs/collection/_apis/projects. Error Message: The remote server returned an error: (401) Unauthorized..
Here is a screenshot of the error.
The odd thing is that if I make a GET request to http://tfsserver:8080/tfs/collection/_apis/projects without any authentication I get a 200 OK response back with project information.
I have configured basic authentication per the tfs cli guide. How can I verify that basic authentication is configured correctly? When I try to login with tfx, I get the following screen.
I have the following extensions installed on the TFS 2017 instance.
Package Management
Release Management Utility tasks
TFS artifacts for Release Management
I am using Microsoft Visual Studio Team Foundation Server Version 15.105.25910.0
According to the screenshot, you are using TFS artifacts for Release Management extension to connect to another TFS instance.
Make sure the things below:
Make sure the collection URL you enter is correct. In your screenshot, the URL you enter is ended with "_home".
Make sure Basic Auth is enabled on TFS server.
Seems you are using the extension TFS artifacts for Release Management which provides a service endpoint to connect to an external TFS or VS Team Services Collection.
After test with TFS2013, I could reproduce your issue and got the same error information. The solution please see below:
Since you are connecting to TFS2013, it works with basic
authentication only. You’ll need to enable basic authentication
support for the TFS Server which handling TFS2013.
Also please make sure the username to connect to the external TFS
collection are with Domain in front of. Then will get a green
verfifed status.
I have a problem with the MIcrosoft Feedback Client, and in general the Request feedback option in VSTS.
If I try to open a request from the notification email, the Feedback Client displays the following error:
Cannot connect to Team Foundation Server. Verify the network connection and try again.
However, if I simply launch it as an application, I got a popup first, where I need to pick the server, the team project collection and finally the project I'd like to connect to (it doesn't ask for login). This works just fine and the submitted feedback is displayed in VSTS, it can be queried, etc.
I removed all cookies and cleared browser cache from all browsers I use, also I checked if there's a false entry in Windows Credential Manager.
Any suggestions what I should try next?
update
We use Feedback Client for Microsoft Visual Studio Team Foundation Server 2015 downloaded from here
Make sure the account you use have the permission to access to the project and view the work items.
Feedback client use the credentials stored in Team Explorer. Try to delete the stored credentials from "Visual Studio -> Team -> Manage Connections -> Manage Connections -> Servers -> Remove" and then launch Feedback Client from email. A sign in dialog will pop up after this and you can enter your credential in it.
If it still does not work, clean all the TFS cache from "%LocalAppData%\Microsoft\Team Foundation\x.0\Cache" folder.
And also, check the link in the email to make sure it is correct. The link should like following:
mfbclients://xxxxxx.visualstudio.com/DefaultCollection/p:ProjectName?rid=FeedbackID
What version of the TFS Client are you using 2012, 2013 or 2015? I ran into a similar issue when we were using this on premise and I had to bump down to a lower version of the TFS Feedback Client.
Here is the TFS 2015 client.
https://www.microsoft.com/en-us/download/details.aspx?id=40768
I just tested mine to VSTS and it worked as expected.
(I am very new to deploying in a dedicated server.)
I have access to Windows Server 2012 through as Remote Login.
I have to deploy my html, js files to the server and then access my html page through a URL.
I am not sure where should I keep my files in the server, launch the server and then access my page through a URL.
In my local server in my machine, I kept the files in
C:\inetpub\wwwroot
And I gave access to others to my page through :
http://myIPaddress/mypage.html
Please suggest where should I keep my code and how can I launch the server.
If anyone can point me to a documentation, even that would be great.
Thank you.
First create web app on the server,
then you can choose any destintion folder for the project.
Follow this documentation
https://msdn.microsoft.com/en-us/library/vstudio/dd394698(v=vs.100).aspx
We need to enable IIS first before deploying our files in Windows Server 2012.
I went through the following document I found in Microsoft website. It was very helpful.
https://technet.microsoft.com/en-us/library/hh831515.aspx
I am using Eclipse Juno (Linux) and added TFS plug-in for Eclipse. Server URL https://******ftware.visualstudio.com and added username and password. This is my Microsoft Live ID which got access to Visual Studio online, but it gives an error message Authorization failure connecting to https://******ftware.visualstudio.com using this username and password.
Username and password works well when connecting from browser. Not sure what is going on.
This plug-in works well on a Windows machine.
You may need to use the "alternate credentials" that does not rely on an MSA (Live ID). In the web access you can click on your name in the top right. There should be a settings drop down that lets you enable and set the alternate credentials for Linux.
https://binary-stuff.com/post/how-to-enable-alternate-credentials-in-visual-studio-online-vso
While saving a workflow using SharePoint designer on a SharePoint site, I get the following error:
Server-side activities have been updated. You need to restart SharePoint Designer to use the updated version of activities.
Steps to recreate error:
Login to the WFE server hosting IIS and workflow manager, open SharePoint Designer 2013 and login to a SharePoint site.
Access the list using SharePoint Designer 2013, in the workflow section, click new workflow.
In the new workflow dialog, enter workflow details, click save
Error message is displayed as below:
Server-side activities have been updated. You need to restart SharePoint Designer to use the updated version of activities.
After restarting SharePoint Designer, the saved workflow is not seen in the site/workflows or list/workflow section.
Workaround
When the above steps are repeated while accessing the site via SPD from any other box besides the WFE/Workflow manager host server, the error is not encountered and its possible to save/publish workflows.
Notes
Workflow Manager 1.0 is installed.
The site has been registered with Workflow manager using Register-SPWorkflowService cmdlet.
Any clue on why is this happening?
Copy Microsoft.SharePoint.WorkflowServices.Activities.Proxy.dll assembly to WebsiteCache folder (%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache{Site Name}\15.0.0.4745)
http://www.jrjlee.com/2014/10/server-side-activities-have-been-updated.html
Experienced with Windows 8.1
During setup/configuration of a remote SharePoint Server on Windows Server 2008 R2, I managed to install Workflow Manager on my client Windows 8 machine while following instructions erroneously as I was supposed to do this on the server.
I accomplished what was necessary with Workflow Manager on the server, but never removed this from my workstation client. After searching through google a ton, I kept finding this page and eventually realized the fix:
Since workflow manager is designed for server edition of Windows, this simply shouldn't be on your client that you are attempting to use SharePoint Designer on to create workflows with.
I was using SharePoint Online with SharePoint Designer 2013 and ran in to this issue when trying to create a workflow. I uninstalled the Workflow Manager as recommended and it started working. Workflow Manager was most likely installed when I installed Visual Studio 2015. I am on Windows 10.
Update WorkflowManager and WorkflowManagerClient to CU4
Uninstall Visual Studio
Uninstall SPD
Deactivate Distributed Cache
Delete WebApplications (Except Central Admin)
Run CMD commands:
cd "%APPDATA%\Microsoft\Web Server Extensions\Cache"
del *.web /S /Q "%APPDATA%\Microsoft\Web Server Extensions\Cache"
cd "%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache\"
rmdir /S /Q "%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache."
mkdir "%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache"
dir "%APPDATA%\Microsoft\Web Server Extensions\Cache"
dir "%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache"
Run iisreset
Restart VM
Create Web Application
Install SPD
Execute iisreset
Restart VM
Open SPD
Go to "Options > Application Options > General Tab" and let -only
the following- boxes checked: "Show status bar" and "Show catalog
lists and system objects" > OK > OK
Open the site via SPD
Create new Workflow 2013 via SPD
Thats what I did. Hope it helps.
I faced the same issues. The workarround was to install sharepoint designer on another machine than the host machine where sharepoint, workflow manager and visual studio is installed. That fixed the issue, however i faced other problems later, specially with workflow 2013, specially when trying to save them as workflow templates, or publish them as global workflows. So i tried to fix the original issue in order to avoid differences between both environements and to be sure to have the right permissions. After long days i found another workarround for my problem:
When comparing the folders
user profile\AppData\Local\Microsoft\WebsiteCache\sitename\version of both environements, i figured out that there were a lot of dll's missing on de developement machine. So I have copied them from the working machine, then i was able to edit workflows 2013 on the buggy machine.
By updating the SharePoint designer you can resolve this issue. Click on the link and follow all the steps mentioned on the blog.
1 Install Microsoft sharepoint designer service pack 1
2 install the update for the sharepoint designer
Enjoy it will work.
Your answer is here