devenv.com detects configuration issue, fails
This problem seems to be a Microsoft Visual Studio 2015 and Windows 10 issue. See https://stackoverflow.com/questions/41870361/visual-studio-sometimes-detects-configuration-issue-on-jenkins-ci-server
I get the following error:
We are evaluating TeamCity and hope to use it in production. However, our devenv.com step fails because of the above issue. I know that it is not a TeamCity issue but none of the solutions I found work for us. Has anyone else found a work around?
We are using VS 2015 but must use devenv because the software is a mix of C++ and Intel Fortran. Intel Fortran VS plugin does not support msbuild yet. Intel is working on it but it is not priority. So we are stuck using devenv for now.
TeamCity 2017.1.1 (build 46654), effective release date 2017-Apr-10, currently running in the professional mode.
Thanks
Tim
Please sign in to leave a comment.
Hi Tim,
I followed the link you posted and noticed that one of the user solved the problem by running VS under different user. Is it possible that TeamCIty RunAs plugin (https://github.com/JetBrains/teamcity-runas-plugin) can help you?
Hi Julia
Thanks for the reply. I did not try RunAs plugin. I am trying out TeamCity so installed it on my local machine. The agent is running as me as a service. I don't really understand the stack overflow post. Since agent is running as me, what is the problem?
Instead, I ran Visual Studio 2017 devenv.com on the solution. Even though the solution and projects are for Visual Studio 2015, this worked. devenv.com compiled the code and ran the tests. We hope to move to Visual Studio 2017 in the next few months so this is ok.
As I read it, the problem is between Visual Studio 2015 and a Windows 10 Anniversary patch. the problem doesn't seem to exist with Visual studio 2017.
Regards
Tim