dotnetPlugin folder missing

Avatar
Permanently deleted user
Created

I don't get it! I'm trying to run a TeamCity build on my new TeamCity installation, never used TeamCity before, but all I get is a "file not found" error. And yes, the file does not exits, I don't even have a dotnetPlugin folder. What am I missing? Do I have to have Visual Studio installed on the server? And the Visual Studio addin?

Cannot run process C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.MsBuildBootstrap.exe /workdir:C:\TeamCity\buildAgent\work\c1c60ffef74a986e /msbuildPath:C:\WINDOWS\Microsoft.NET\Framework\v3.5\MSBuild.exe : file not found

Votes

0

Share

5 comments
Avatar
Permanently deleted user
Created

I think you need to check if ASP.NET 3.5 framework is intalled on your host machine - if this is not the case then you need to change the build runner to use ASP.NET 2.0

thanks

paul

0
Avatar
Permanently deleted user
Created

Thank you Paul. Unfortunately framework 3.5 is installed, the file C:\WINDOWS\Microsoft.NET\Framework\v3.5\MSBuild.exe does exist, but not C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.MsBuildBootstrap.exe. We also have framework 2.0, 3.0 and 4.0 installed. It's a Windows Server 2003. I downloaded the latest version of TeamCity, 6.0.3, just the other day. Isn't the dotnetPlugin folder/files included in the latest installation of TeamCity?

0
Avatar
Michael Kuzmin
Created

Hi Markus

could you please post C:\TeamCity\buildAgent\logs\teamcity-agent.log and C:\TeamCity\buildAgent\logs\upgrade.log
TeamCity should unpack this plugin automatically at first start, but seems it failed for some reason.

Thanks
Michael

0
Avatar
Permanently deleted user
Created

Here are the requested logs. Thank you Michael!

// Markus



Attachment(s):
logs.zip
0
Avatar
Michael Kuzmin
Created

Hi Marcus

I'm sorry for late response.

When you start the agent it connects to the server, and checks for updates. If new versions of agent binaries or plugins are detected, the agent service downloads them. Then the service is stopped, and special upgrade process is launched to unpack and update the files. Finally the agent service is started again.

From the log I see the service was re-launched manually while upgrade was being performed. The processes had a conflict due to locked files, so dotnetPlugin was not installed correctly.

To reinstall the agent you'll need:

  1. Reboot the build agent machine to make sure there are no hanging processes which lock agent binaries
  2. Delete \BuildAgent\plugins folder
  3. Start agent service
  4. Wait till the agent finishes upgrade procedure. It may take several minutes.


In version 6.5 we improved this part of the code, so the agent should recover from such kind of issues automatically.

Michael

0

Please sign in to leave a comment.