Of course my PowerShell script failed on the first attempt- but at least the error was with my script and not with the environment.
Beware of a restart at the end of installation (especially if the Release Management server is in production)! On the RM server and this fixed my assembly load error. The load failure was on the Release Management server and not on the agent machines. I checked and confirmed that on the 2008 R2 server I had installed the latest framework and on the 2012 R2 machine it comes pre-loaded.Īfter some searching and troubleshooting with logs I found that I had missed installing the Windows Management framework on the Release Management server. The missing assembly is a part of Windows Management Framework. This was irrespective of the OS of the deployment machine selected. I got this exception whenever I tried a release. TFS 2013.4 (applies to all version of TFS compatible with RM server).
Install the pre-requisites (Windows Management Framework 4.0 and winRM configuration etc) as mentioned in this Release Management 2013.4 (applies to 2013.3 above) on Windows 2008 R2 OS or Windows 2012.End of stack trace from previous location where exception was thrown The system cannot find the file specified.Īt .()Īt .()Īt ._11.MoveNext()
> System.IO.FileNotFoundException: Could not load file or assembly ', Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. > System.AggregateException: One or more errors occurred. : Exception has been thrown by the target of an invocation. Unable to deploy to a machine using vNext Release management template to a standard machine.
0 kommentar(er)
