Under what circumstances build agent is not MSBuild compatible?

Hi,

I'm using TeamCity 4.5.5 (build 9103) and ran into very strange problem. I have 2 very similar machines (hardware and software wise) and installed TeamCity Server and Build Agent on both of them. Builds are performed using MSBuild.
First machine is absolutely fine. However, second machine is causing issues - TeamCity itself is working fine, but the build agent is marked as not compatible with MSBuild (and thus cannot perform builds). I have checked System Properties of the build agent, and noticed that these properties are NOT listed on the problematic machine:

DotNetFramework1.1       
DotNetFramework1.1_Path
DotNetFramework1.1_x86      
DotNetFramework1.1_x86_Path
DotNetFramework2.0      
DotNetFramework2.0_Path
DotNetFramework2.0_x86      
DotNetFramework2.0_x86_Path
DotNetFramework3.0      
DotNetFramework3.0_Path
DotNetFramework3.0_x86      
DotNetFramework3.0_x86_Path
DotNetFramework3.5      
DotNetFramework3.5_Path
DotNetFramework3.5_x86      
DotNetFramework3.5_x86_Path

I have checked C:\WINDOWS\Microsoft.NET\Framework directory and can see that .NET frameworks 1.1, 2.0, 3.0 and 3.5 ARE installed.
My question is - why build agent is marked as not compatible with MSBuild and how TeamCity build agent check what .NET versions are installed?
Additionally, could someone briefly explain where the build agent properties I mentioned earlier are comming from?

Thanks in advance,
vytas

2 comments
Comment actions Permalink

Sorry for long time to reply.

Please check second machine is not running under x64 jvm.
Attach agent logs as described at http://www.jetbrains.net/confluence/display/TCD5/Reporting+Issues


Please do the following:
- stop build agent
- enable debug logging
- clean up <agent>/logs folder
- start build agent
- wait agent to connect to TeamCity server
Attach created build agent log files from <agent>/logs folder.

0

Please sign in to leave a comment.