S
Stefan Oude Vrielink
Guest
Hi,
We are building SSIS 2014 and SSAS 2014 projects using devenv.com (VS 2013 / SSDT BI 2013) on a Windows 2016 server with Team Foundation Server 2017 Update 2 RTM.
All builds succeed as long there is a connected Remote Desktop session, NO MATTER what user.
However, if there are no connected Remote Desktop sessions, calling devenv.com fails with message:
-------------------------------------------------------------------------------------------------------------------------
Microsoft Visual Studio 2013 Version 12.0.21005.1.
Copyright (C) Microsoft Corp. All rights reserved.
Microsoft Visual Studio has detected a configuration issue. To correct this, please restart as Administrator. For more information please visit: http://go.microsoft.com/fwlink/?LinkId=320596
-------------------------------------------------------------------------------------------------------------------------
Previously we used Windows 2012 R2 with Team Foundation Server 2015 Update 4 and had no issues at all.
Does anyone know a fix/workaround for this strange issue?
Regards Stefan
Continue reading...
We are building SSIS 2014 and SSAS 2014 projects using devenv.com (VS 2013 / SSDT BI 2013) on a Windows 2016 server with Team Foundation Server 2017 Update 2 RTM.
All builds succeed as long there is a connected Remote Desktop session, NO MATTER what user.
However, if there are no connected Remote Desktop sessions, calling devenv.com fails with message:
-------------------------------------------------------------------------------------------------------------------------
Microsoft Visual Studio 2013 Version 12.0.21005.1.
Copyright (C) Microsoft Corp. All rights reserved.
Microsoft Visual Studio has detected a configuration issue. To correct this, please restart as Administrator. For more information please visit: http://go.microsoft.com/fwlink/?LinkId=320596
-------------------------------------------------------------------------------------------------------------------------
Previously we used Windows 2012 R2 with Team Foundation Server 2015 Update 4 and had no issues at all.
Does anyone know a fix/workaround for this strange issue?
Regards Stefan
Continue reading...