TeamCity 7.1.x Windows Server 2012 compatibility and netframework_x86 build requirement

Avatar
Permanently deleted user
Created
I have a Windows Server 2012 instance that is x64 and installed TeamCity 7.1.  The initial configuration of TeamCity is flawless, but when I attempt to create a build configuration with a .NET Visual Studio 2012 solution, the agent is shown as incompatible where the netframework_x86 cannot be met.1) Does this require that I install the x86 version of the 4.x framework onto the teamcity server?2) Can the workaround that is discribed in other posts in this forum for Windows 2008 R2 be applied successfully?Thanks,

Votes

0

Share

5 comments
Avatar
Michael Kuzmin
Created

Hi

Could you please post teamcity-agent.log file from this build agent.

0
Avatar
Permanently deleted user
Created
Here the teamcity agent log as a series of screenshots (we couldn't gain access to the server --network issues). I hope this can help you out.

Attachment(s):
teamcity-agent-logscreenshot.docx
0
Avatar
Michael Kuzmin
Created

Hi

In the log I see Access denied errors.
TeamCity build agent is designed to dynamically download components from a server and upgrade its plugins on the fly.

Please update file permissions to allow an account used by agent process to modify files inside D:\TeamCity\buildAgent directory.

0
Avatar
Permanently deleted user
Created
With regards to the "Access Denied" found in the logs, I went and put the account as a local admin, restarted the service and the agent started to work. After that I removed the account as a local admin and restarted the service and the agent has since continued to work with no problems.Question I have is:  Does the account that is running the services have to be a local admin on the TC server? Or can it be given local admin privileges temporarily as I proved out? Are there specific permissions that need to be documented for TC Agent to work correctly?  Can this be done during the installation of TC and initial configuration?Thanks,
0
Avatar
Michael Kuzmin
Created

We do not require administrative rights over whole machine.
The account should have Run as a service previlege, and have Modify permissions over its directory in the file system.

0

Please sign in to leave a comment.