Since we updated from TFS to Azure DevOps Server 2020 we have a problem with live updates when using the client. I expect pages to automatically update with new information as they come available like it did with TFS, but that doesn't happened anymore. Instead we get an error:
'Live updates for this pull request were temporarily interrupted. Refresh to view the latest.'
I suspect it is a problem with a server setting, but I have no idea where to look.
Azure DevOps Server
Version Dev18.M170.4
Related
i attempt to backup and restore tfs database to a auther server
Any idea about risk ?
and How i can manage TFS Server to change the new location of TFS database ?
You could move Azure DevOps Server/TFS from one machine to another by restoring it to new hardware (called a restoration-based move).
When you move to a new server you do not lose any of your project history.
One risk
In some situations you might want to change the domain of a Azure
DevOps Server deployment as well as its hardware. Changing the domain
is an environment-based move, and you should never combine the two
move types. First complete the hardware move, and then change the
environment.
Besides, another place need to pay attention to. You must have a complete set of data backups for the SQL Server databases. If the data was encrypted, you must also have the encryption key and its password.
For more information, see Back up Azure DevOps Server
You must back up the TFS_Warehouse and TFS_Analysis databases if your deployment is configured to use SQL Server Reporting Services and you want to restore those databases to a different server. You cannot just rebuild the warehouse, as you can when you restore to the same server or instance.
Once the backup completes, verify that the backup is available on the storage device or network share, and that you can access this backup from the new hardware.
Actually, we do have a detail step-by-step official tutorial, you could kindly refer and follow it-- Move or clone from one hardware to another for Azure DevOps on-premises
I'm having issues with self hosted TFS environment in where the performing any action in Visual Studio or the Web Portal can take upwards of 20 to 30 seconds to complete. The issue is intermittent and other developers are seeing the same symptoms. Tracing the slow requests with Wireshark shows 3 REST requests to the TFS Server interface with first two requests returning with a 401 response and the third returning a 200 response.
The difference in the requests seem to be the authentication. The first request appends no explicit authentication method to the POST and returns a standard 401 response. The second request appends NTLMSSP_NEGOTIATE and fails with a 401 NTLMSSP_CHALLENGE response. The third request appends NTLMSSP_AUTH to the request and passes in my AD user name and response with a standard 200.
Symptoms:
First two requests return a 401 failure
Time between the requests seems to vary from a few ms to up to thirty seconds and the time between request and response is less than 100ms
Connecting to TFS within the cloud environment being logged in as the same AD account that is connecting to TFS does yield display the same intermittent issue.
Environment:
Development systems are connecting over a VPN to a cloud environment
TFS accounts are AD based with AD servers existing in the same cloud environment as TFS
Development systems are joined to a different AD system that has no trust relationship with the AD system that TFS is joined to
TFS Server version is 2018 (16.131.27701.1)
TFS Datastore is SQL Server 2016 EE hosted on a separate instance.
Visual Studio version is Pro 2017 (15.4.1)
Seeing the symptoms in two independent environments tells me the issue is on the TFS Server however I'm able to identify any potential bottlenecks or blockers. Also that the issue appears in the Visual Studio and the web interface the issue seems to be in the TFS Server and not the client but the delay in making the requests from the client points it right back to being a client configuration issue.
How can I identify what is causing the client to delay follow up requests when a prior response returns a 401 reply?
I have a TFS plugin as a part of my application that sends out alerts to a web API URL when anything changes on that TFS 2015 instance. The Web API processes those alerts as required.
Now I recently came to know about the
Web Hooks feature in TFS 2015 which essentially accomplishes something similar.
I'm considering getting rid of the TFS Plugin and switching onto the Web Hooks simply because I will need to maintain one less component. However, reliability is most important to me. So, is there a way to find out if the latter is more reliable than the former, or if it's the other way around?
Also, does TFS give preference to either in terms of execution order? I've been told that the web hooks capture the field values (for a WorkItem) when the event is created. Whereas the plugin retrieves the fields after the event is fired so there might be a small lag time.
Is it possible to allow anonymous access to the tfs web portal?
Would be nice to be able to allow users who are not logged inn to access /tfs/DefaultCollection/ProjectName/_dashboards and also preferably the information in the Work tab.
Tried adding the Everyone group in the Access levels tab. In the security tab for the collection and on the security tab for the project and also on the collection on the TFS server aswell as enabling Anonymous authentication on the IIS server but not having any luck.
Still getting a prompt to log on when trying to navigate to the dashboard and if I cancel that I get this error:
Error
The page you are looking for is currently unavailable.
TF400813: Resource not available for anonymous access. Client authentication required.
More information about this error
TF400813: Resource not available for anonymous access. Client authentication required.
Is it possible to fix this?
No, TFS does not support anonymous access for now. Refer to the Q&A in this blog for details: https://blogs.msdn.microsoft.com/bharry/2015/02/23/vs-2015-ctp6-and-tfs-2015-ctp1-shipped-today/
bharry
#Karl, we don't currently have anonymous access in TFS 2015 but it's
been a hot topic lately. We're looking at how we could get it done
before too long.
I have not checked but do not think it is possible to day.
While you can go to IIS and enable Anonymous, TFS is designed in a way that each call to the server is tied to user previously authenticated.
I will not be surprised of a change in the future, because it is a limit for the service offered in VSTS; in fact you can only have private projects in today's VSTS. If this limitation is lifted in VSTS, we will get it for free in TFS.
I am writing a simple custom work item browser and I'd like it to follow the real-time changes happening to work items on my TFS server.
For example, if someone has changed a work item's Title or State, I'd update my work item tree with this new information.
How can I subscribe to such events?
You can use the TFS eventing mechanism to subscribe a web service endpoint to get notified when a work item changes. However this is designed for server->server communication and this push notification mechanism does not work well for client applications.
Instead I would recommend that you use the TFS .NET Api to poll the server periodically for updates. To make the poll operation efficient after you have got a full set of results using your query, you could modify the WIQL to just look for work items where the changed date is greater than the last time that you polled the server.
The reason the "pull" model works better than the "push" model in this case is as follow:
To send a web service push notification to your client machine, the TFS instance needs to be able to talk directly to the port on your client box. That means that you must have the appropriate port open and allow traffic in that direction from you firewall.
Push notifications need Team Foundation Server Administration level user permissions to create which means that only Administration users can use your application
The server will attempt to send notifications to the subscribers until the subscriber removes the event subscription. This means that is your application crashes or doesn't clean up it's subscriptions correctly then the server will be attempting to send messages to machines that are not listening for them. This will use up resources on your TFS server and generate errors in the TFS Server event logs. Your application will need a significant amount of logic to ensure that it records which subscriptions are in place and manage them appropriately.
Hope that makes sense.
For Email Alerts
TFS Client includes a subscribe to alters for any changes to your work items ("project alerts" in the team project node's context menu in team explorer).
To subscribe to work items based other criteria (including all for a team project) the TFS Power Toys includes an alerts editor (the power toys add an alerts node under each team project in team explorer).
For Web Service Calls
These are also possible (e.g. to have a server listening): See the Visual Studio SDK for details.