April patches for Azure DevOps Server and Team Foundation Server
Gloridel Morales
Update: We’ve fixed the issues with the patch, thank you for your patience while we fixed these issues. You can follow the instructions and validations steps in this blog to install.
This month, we are releasing patches that impact our self-hosted product, Azure DevOps Server 2019, as well as Team Foundation Server 2018. There are no security fixes with this patch; these patches include functional changes.
The following has been fixed with this patch:
- SVN commits do not trigger pipeline
- Adding support for SHA2 in SSH on Azure DevOps
Azure DevOps Server 2019.1.1 Patch 2
If you have Azure DevOps Server 2019 Update 1.1, you should install Azure DevOps Server 2019 Update 1.1 Patch 2.
Verifying Installation
-
Option 1: Run
devops2019.1.1patch2.exe CheckInstall.devops2019.1.1patch2.exeis the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed. -
Option 2: Check the version of the following file:
[INSTALL_DIR]\Azure DevOps Server 2019\Application Tier\Web Services\bin\Microsoft.VisualStudio.Services.Feed.Server.dll. Azure DevOps Server 2019 is installed toc:\Program Files\Azure DevOps Server 2019by default. After installing Azure DevOps Server 2019.1.1 Patch 2, the version will be 17.153.30017.2.
TFS 2018 Update 3.2 Patch 10
If you have TFS 2018 Update 2 or Update 3, you should first update to TFS 2018 Update 3.2. Once on Update 3.2, install TFS 2018 Update 3.2 Patch 10.
Verifying Installation
-
Option 1: Run
tfs2018.3.2patch10.exe CheckInstall.tfs2018.3.2patch10.exeis the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed. -
Option 2: Check the version of the following file:
[TFS_INSTALL_DIR]\Application Tier\Web Services\bin\Microsoft.TeamFoundation.WorkItemTracking.Web.dll. TFS 2018 is installed toc:\Program Files\Microsoft Team Foundation Server 2018by default. After installing TFS 2018 Update 3.2 Patch 10, the version will be 16.131.30020.3.
Light
Dark
21 comments
After updating to Azure DevOps Server 2019.1.1 Patch 2 I get a Runtime error on the web interface and I see exceptions in the Application Event Viewer:
Could not load file or assembly ‘SharpSvn.DLL’ or one of its dependencies. The specified module could not be found.
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
at System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory()
at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai)
at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
at System.Web.Compilation.BuildManager.GetPreStartInitMethodsFromReferencedAssemblies()
at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
at System.Web.Compilation.BuildManager.ExecutePreAppStart()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
Could not load file or assembly ‘SharpSvn.DLL’ or one of its dependencies. The specified module could not be found.
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
I fixed the error by reverting to the previous version (copied files from backup zip and manually removed new files added by the patch)
The patch log is without any error and I can send it for research.
Hi Michael,
Please send me the log to glmorale@microsoft.com so I can forward to the engineering team.
Hi Michael, the fix is live now. You can follow instructions in this blog to install.
I just applied patch 2 and am seeing the same error.
Hi Blake,
We are working on a fix and expect to publish it tomorrow.
this comment has been deleted.
Hi Blake, the fix is live now. You can follow instructions in this blog to install.
We had the same issue with the Patch 2. Is it possible to get patch 1 that came out in March 2020?
If i follow the link for patch 1, it still downloads patch2.
Please help.
Sarita .
Hi Sarita,
You can find the Azure DevOps Server 2019 Update 1.1 Patch 1 in the release notes.
I applied the March patch and it went well. I also checked the version of the dll file and it is correct.
However, the console version is not the same. Console version reads – 17.153.295522.3.
Should they match? Is this a bug?
Sarita.
Hi Sarita, the fix is live now. You can follow instructions in this blog to install.
The version number specified above under Azure DevOps Server 2019.1.1 Patch 2 is listed as “17.153.3000.4.”, it should state 17.153.30002.4.
Thank you Jonathan for reporting this, I fixed the version.
Is the April patch good now? Can we apply?
Hi Sarita,
We are currently conducting additional testing and will update this blog once the patch is available. Thank you for your patience.
It looks like the patch for 2018 will reopen an older problem
The case number we had: [REG: 119041626001204]
Again we have problems changing the inheritance from XAML builds.
I know that these are all outdated things, but still important to my company
Hi Gloridel,
currently we are in the DevOps server on level 17.153.29522.3. there we have the problem that when queuing a release, the application tiers try to reach the endpoint stored in the service connection. In most cases only the release agents and not the application tiers can do this. After a 90 second timeout the build is queued. This happens in a pipeline for each environment. Then it takes a while. Is this included in the current Patch 2 or not yet?
This updated patch still has some issues.
It was failing to update certain files, because those files didn’t exist in those language folders.
I added dummy files in each spot it reported and it was able to proceed through the install.
Here are the files it complained about:
Microsoft.VisualStudio.Services.ReleaseManagement2.Artifact.Extensions.resources.dll
Microsoft.VisualStudio.Services.ReleaseManagement2.Server.resources.dll
Microsoft.TeamFoundation.Build2.Server.Extensions.resources.dll
I had applied devops2019.1.1patch1.exe last month, so the server was as current as it could be.
I am sorry you have having issues with the patch. In order to diagnose the problem, we need the patch logs. Could you please email the patch logs to mahoover at microsoft dot com. You can find the logs at C:\ProgramData\Microsoft\Azure DevOps\Server Configuration\Logs.
Thanks for your help tracking this issue down.
You should get them shortly. Sorry for the delay. I must have turned off notifications.
I also needed to get my security department’s blessing.
;?)