Solution:

Right-click the agent pool and choose "Update all agents", it will upgrade the agents to the version of the on-premise TFS server

Links:

Team Services: https://<account>.visualstudio.com/_admin/_buildQueue

TFS 2017: http://<TFS Server>/tfs/<Collection Name>/_admin/_buildQueue

TFS 2015 Update 3: http://<TFS Server>:8080/tfs/<Collection Name>/_admin/_buildQueue

TFS 2015 RTM: http://<TFS Server>:8080/tfs/<Collection Name>/_admin/_buildQueue#_a=settings

Explanation:

The “Powershell to rollback” task in Release Management Utility tasks from Visual Studio Marketplace was working fine in TFS 2015 instance but stopped working after upgrading TFS 2017 instance.

Exception:

2017-06-27T11:57:58.0160646Z ##[debug]inlineScripe = Write-Host 'Rollback logic goes here as a powershell script'
2017-06-27T11:58:58.0327321Z ##[debug]Getting Personal Access Token for the Run
2017-06-27T11:58:58.2046532Z ##[debug]Calling http://TFSServer:8080/tfs/Collection/Team project/_apis/release/releases/213/environments/641/tasks?api-version=2.1-preview.1 using obtained PAT token
2017-06-27T11:58:58.2983878Z ##[debug]Could not obtain release tasks status
2017-06-27T11:58:58.2983878Z ##[debug]Error
2017-06-27T11:58:58.2983878Z The page you are looking for is currently unavailable.
2017-06-27T11:58:58.2983878Z Page not found.
2017-06-27T11:58:58.2983878Z More information about this error
2017-06-27T11:58:58.2983878Z Page not found.
2017-06-27T11:58:58.2983878Z Things you can try:
2017-06-27T11:58:58.2983878Z Refresh the current page
2017-06-27T11:58:58.2983878Z Go back to the previous page
2017-06-27T11:58:58.2983878Z Sign in as a different user
2017-06-27T11:58:58.2983878Z Submit feedback to Microsoft about this error
2017-06-27T11:58:58.2983878Z Microsoft Visual Studio Team Foundation Server
2017-06-27T11:58:58.2983878Z © Microsoft Corporation. All rights reserved.

Solution:

The API version in the script Runpowershellwithtaskcontext.ps1 located at “<Agent Directory>\tasks\Rollback\1.1.2\” related to “Powershell to rollback” task, must be updated with the corresponding TFS 2017 API version after the upgrade.

Change the api-version from api-version=2.1-preview.1 to api-version=3.0-preview.2 in the script Runpowershellwithtaskcontext.ps1 located at “<Agent Directory>\tasks\Rollback\1.1.2\”

Exception:

Access to the registry key "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\15.0\TeamFoundation\Instances\<TFS Server Name>\Collections\<Team Project>" is denied.

Solution:

Clear the Visual Studio cache at "%LocalAppData%/Microsoft/VisualStudio/15.0" to resolve the error

Exception:

TF254078: No attachable databases were found on the following instance of SQL Server: <Server Name>. Verify that both the name of the server and the name of the instance are correct and that the database was properly detached using the detach command in the Team Foundation Administration Console.

Explanation:

You may need to check whether the project collection is detached from the other TFS instance properly.

Execute the following query on the problematic project collection database where it is restored

USE <project collection database name>
GO
SELECT name, value FROM   sys.extended_properties 

Check whether the TFS_SNAPSHOT_STATE property with the Complete value is available in the query output.

If you don’t see the TFS_SNAPSHOT_STATE property then the project collection is not detached completely from the other TFS instance properly

Solution:

• Login to your Team Foundation Server web portal (https://<server Name>:8080/tfs/).
• Navigate to home page -> profile -> security menu
• Click on personal access token menu
• Click on Add button
• Enter the Description, Expires In (lifespan) and Accounts details for your token
• Click on Create button

Exception:

An error occurred during download: System.IO.FileNotFoundException: Unable to find the specified file

Explanation:

This exception may occur while the release trying to download the build artifacts which has long path.

Workaround:

Reduce the length of the path and try again

Explanation:

• Install Release Management Utility tasks extension
• Write a PS script to capture the tasks execution result in a XML file

Note: Sample script to get the tasks execution result is available at Release Management Utility tasks extension site.

• Add “Deploy: PowerShell for rollback” task and configure the task to execute the above mentioned PS script.
  Add "Deploy: Windows Machine File Copy" task and configure the task to copy the generated XML file to deployment\target server(s)
• Write a PowerShell script to parse the generated XML file and perform the rollback activates based on the tasks execution result.
• Add "Deploy: PowerShell on Target Machines" task and configure the task to execute the above mentioned PS script on deployment\target server(s)

Note: Make sure you enable “Run Always” control option for the mentioned tasks.

Exception:

PS D:\> Start-ScheduledTask -TaskName SynchronizeTime

Start-ScheduledTask : The system cannot find the file specified.
At line:1 char:1
+ Start-ScheduledTask Update-MyHelp -Starttings $s
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (PS_ScheduledTask:Root/Microsoft/…S_ScheduledTask) [Start-ScheduledTask]
   , CimException
    + FullyQualifiedErrorId : HRESULT 0x80070002,Start-ScheduledTask

Explanation:

I got the above exception while working with Scheduled Task Cmdlets in Windows PowerShell.

Solution:

Adding TaskPath parameter resolved the issue.

PS D:\> $path = (Get-ScheduledTask SynchronizeTime).TaskPath
PS D:\> Start-ScheduledTask -TaskName SynchronizeTime -TaskPath $path 

Solution:

1. Open PowerShell console window

2. Execute test-wsman -ComputerName <Remote Computer Name>