Unmet requirements: DotNetFramework3.5_x86 exists

Running on Windows Server 2003

With:

  • .Net upto v4.0
  • SDKs
  • Visual Studio 2010

Incompatible runner: MSBuild
Unmet requirements:
  • DotNetFramework3.5_x86 exists

Any ideas?

7 comments
Comment actions Permalink

Could you post upgrade.log from this agent please.
We got a few simillar reports, but were unable to reproduce the issue.

Go to Build runners page for this agent. Is there MSBuild runner there?

Other customers told us they make the agents work by uninstalling them and installing again.

Michael

0
Comment actions Permalink

Hi,

I have the same issue, but I have just done a fresh build on a windows 2008 server.

Incompatible runner: MSBuild
Unmet requirements:
  • DotNetFramework3.5_x86 exists


I've installed the windows SDK, but I have not installed visual studio as I did not want that on our build server.

Thanks

0
Comment actions Permalink

Hi,

Ok I fixed this by re-installed the dot net framework.

0
Comment actions Permalink

I ran into this same issue. I too ran the installer for .NET 3.5 SP1, but this did not fix the issue for me.

0
Comment actions Permalink

Dan

Please post teamcity-agent.log and upgrade.log from your problem agent. We have this issue reported for several times, but cannot reprocude and localize it yet.

As workaround you can reinstall the agent completely, or by instructions in this thread.

Thanks
Michael

0
Comment actions Permalink

Hi Michael,

I did e-mail you one of the logs you requested.Hopefully it was of some value to you.

I saw that v6.5.3 of TeamCity was released this morning. I uninstalled v6.5.2, installed v6.5.3, and at first, the main build agent was showing as disconnected from TeamCity. Restarting the build agent service resolved this issue. The build agent also now contains an extensive list of build runners, whereas in the previous version (when I was running into the unmet requirements issue), it only contained a command line runner.

Thanks!
Dan

0
Comment actions Permalink

Thanks for the logs!
We cannot reproduce this issue in house yet, but are going to implement related fixes in 6.5.4 release.

Michael

0

Please sign in to leave a comment.