Did the latest Windows 10 upgrade on 8/27/2019. That broke Outlook 2016, but an Office Repair tool fixed that.
Now my VS Community 2017 can't run a Web project because IIS Express won't start. Says some other app is using the port, but SysInternals and netstat -ano say otherwise. In the Windows application log, an error for Clr4IntegratedAppPool always fires before the IIS error.
I have tried all of the following:
Repair VS 2017 (took hours to download gigs of stuff; what was this, an entire reinstall?)
Uninstall/reinstall IIS Express and reboot, reboot, reboot.
Delete the folder My Documents/IIS Express.
Delete the hidden project file .vs/config/applicationhost.config.
Changed the port number in the VS project properties, on the Web tab.
Ran this command: netsh http add iplisten ipaddress=::
I created a new web project and it ran fine with IIS Express. But after that, the old project still could not keep IIS Express running.
Suggestions?
When I compared the csproj files for the new project that worked and the old one that had stopped working, I found that the new one had a lot of IIS-related stuff that was absent from the old one. I copied it from the old to the new, and it worked. However, it only worked with the new port number. Haven't gotten the old one to work, but I'll gladly settle for that!
<WebProjectProperties>
<UseIIS>True</UseIIS>
<AutoAssignPort>True</AutoAssignPort>
<DevelopmentServerPort>57919</DevelopmentServerPort>
<DevelopmentServerVPath>/</DevelopmentServerVPath>
<IISUrl>http://localhost:57919/</IISUrl>
<NTLMAuthentication>False</NTLMAuthentication>
<UseCustomServer>False</UseCustomServer>
<CustomServerUrl>
</CustomServerUrl>
<SaveServerSettingsInUserFile>False</SaveServerSettingsInUserFile>
</WebProjectProperties>
I want to utilize TFS and MSTest for regression testing. I have a few long running unit tests (10+ minutes). The unit tests can be run successfully locally on developer's machine inside VS2017. The unit test were shown as passed on TFS2017. However the build was marked as failed. This problem looks like a timeout to me between the executor and the unit test. Is there a way to increase the timeout setting in TFS? Any other ideas to fix the build?
2017-11-28T14:01:00.8504854Z ##[error]Error: An exception occurred while invoking executor 'executor://mstestadapter/v2': Object '/fe158daa_975c_4c26_818d_b79d26604456/ekqkfvms170qdx3bql9dzzy2_318.rem' has been disconnected or does not exist at the server.
Check what's exact version of Visual Studio 2017 do you installed on the build agent machine. Seems there's an issue on the MSTest.TestAdapter and MSTest.TestFramework on earlier version. Based on this thread the issue has been fixed and it's available in v1.1.13.
See the github bug: Run tests fail intermittently with a disconnected from server exception.
Please try below items to fix that:
Enable Clean option for Get Sources and Build step, then try it again.
Just try upgrading to the latest version of
VS 2017, then try it again.
Update the MSTest.TestAdapter and MSTest.TestFramework
to the latest version on the build agent machine.
Check if all the test projects refer to the same version of the test
adapter. If not just try moving all test projects in a solution to
refer the same version of the adapter.
Also below related issues for your reference:
https://github.com/Microsoft/testfx/issues/177
https://github.com/Microsoft/testfx/issues/194
I am having an issue with the SSDT installation for VS2017.
I have ran the installer three times, once basic, once following VS update and the last following some minor windows updates.
All 3 times the logs stumble at the same point, anyone know what this .exe it is trying to run is (I am running the installer with Admin...). I read somewhere for a similar error that it might be the SDK but I am able to run this locally, any nice workarounds to having this installed out there?
[29BC:A138][2017-09-26T09:28:00]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 4
[1EC4:6DB0][2017-09-26T09:28:00]e000: Error 0x800703e9: Process returned error: 0x3e9
[1EC4:6DB0][2017-09-26T09:28:00]e000: Error 0x800703e9: Failed to execute EXE package.
[29BC:A138][2017-09-26T09:28:00]e000: Error 0x800703e9: Failed to configure per-machine EXE package.
[29BC:A138][2017-09-26T09:28:00]i000: MainViewModel.OnPackageAction: Install Completed for package SQL Server Analysis Services (id: Microsoft.DataTools.AnalysisServices)
[29BC:A138][2017-09-26T09:28:00]i319: Applied execute package: Microsoft.DataTools.AnalysisServices, result: 0x800703e9, restart: None
[29BC:A138][2017-09-26T09:28:00]e000: Error 0x800703e9: Failed to execute EXE package.
[1EC4:6DB0][2017-09-26T09:28:00]i351: Removing cached package: Microsoft.DataTools.AnalysisServices, from path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\
[29BC:A138][2017-09-26T09:28:00]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
[1EC4:6DB0][2017-09-26T09:28:00]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5d5d6235-5c8c-4377-9a75-1b6368850657}, resume: None, restart: None, disable resume: No
[1EC4:6DB0][2017-09-26T09:28:00]i330: Removed bundle dependency provider: {5d5d6235-5c8c-4377-9a75-1b6368850657}
[1EC4:6DB0][2017-09-26T09:28:00]i352: Removing cached bundle: {5d5d6235-5c8c-4377-9a75-1b6368850657}, from path: C:\ProgramData\Package Cache\{5d5d6235-5c8c-4377-9a75-1b6368850657}\
[1EC4:6DB0][2017-09-26T09:28:00]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5d5d6235-5c8c-4377-9a75-1b6368850657}, resume: None, restart initiated: No, disable resume: No
[29BC:A138][2017-09-26T09:28:00]e000: MainViewModel.OnBundleAction: Bundle action failed: Recursion too deep; the stack overflowed (0x800703E9)
[29BC:A138][2017-09-26T09:28:00]i399: Apply complete, result: 0x800703e9, restart: None, ba requested restart: No
[29BC:6724][2017-09-26T09:28:04]i000: MainViewModel.OpenUrl: Opening url: C:\Users\RTOMPS~1\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20170926092556.log
The answer from Nick is very helpful, but I still failed at SSDT-Setup-ENU.exe /repair with the same error Error 0x800703e9: Failed to execute EXE package..
Then I tried it with a very straightforward way: (Disable UserAccountControl first)
copy SSDT-Setup-ENU.exe to c:\temp and execute SSDT-Setup-ENU.exe /layout to download a local copy of the bundle.
open C:\temp\redist and double click NDP461-KB3102438-Web.exe
open C:\temp\payload and double click vsta_setup.exe
repeat to install others...
This is the most likely link I came to when I got the same message in my log:
Applying execute package: Microsoft.DataTools.AnalysisServices, action: Install, path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe" /q /admin /instanceIds:"fc3f0e2c" /logFile:"C:\Users\a_nzchuk\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20171205113839_002_Microsoft.DataTools.AnalysisServices.log" "payload\Microsoft.DataTools.AnalysisServices.vsix"'
MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 17
MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 17
...........
...
Error 0x800707d3: Process returned error: 0x7d3
Error 0x800707d3: Failed to execute EXE package.
Error 0x800707d3: Failed to configure per-machine EXE package.
MainViewModel.OnPackageAction: Install Completed for package SQL Server Analysis Services (id: Microsoft.DataTools.AnalysisServices)
Applied execute package: Microsoft.DataTools.AnalysisServices, result: 0x800707d3, restart: None
So I'll document my findings here.
In my start menu I had Visual Studio 2017 (SSDT). It ran OK but didn't have any BI projects available
This is what I did from an Administrator elevated command prompt:
Copied SSDT-Setup-ENU.exe into C:\temp (rather than a user specific download folder which the admin user may not have access to)
Ran SSDT-Setup-ENU.exe /layout to pre-download support and redist files (this was after a required restart)
Ran SSDT-Setup-ENU.exe /repair to try and repair the install. It gave me a button Repair that I clicked.
Ran SSDT-Setup-ENU.exe /repair again. Selected Modify. Noted that only SQL Server Database was ticked, but none of the others (SSAS, SSIS, SSRS)
Ticked SQL Server Analysis Services and pressed Modify. It proceeded to do it. Got stuck at 50% for a few minutes but eventually worked
Repeated for SQL Server Reporting Services and SQL Server Integration Services
After this, when I reran VS2017, it had the BI projects and allowed me to create a 1400 SSAS solution
Previous failed installations left VS2017 recognising that the installation was present in Visual Studio Installer. I removed the installation, restarted and the re-install was successful...
For SSDT for VS2018, Version 15.5.2
same failed at execute exe. only do
1. SSDT-Setup-ENU.exe /layout
2. SSDT-Setup-ENU.exe /repair (tick SSAS/SSRS/SSIS based on your requirement)
and this already works. I think MS also do some job for this.
EDIT: This might not be relevant any more since SSDT 15.8.2 is now out.
In my case, I was on VS 2017 15.7.2 and I can't complete the installation in SSDT 15.6. What I did was to install SSDT 2017 15.7.0 and it worked.
Make sure to uninstall previous SSDT installations via the VS installer or Control Panel also the Microsoft Reporting Services Projects and Microsoft Aanalysis Services Projects extensions first if you have them before launching the installer.
Edit: I think my Python issue is a subset of Jeff Leach's comment about repairing Visual Studio. So, I would probably look at any Visual Studio errors you had while installing and try and fix them before trying to install SSDT. For the time being I would NOT update Visual Studio or its installer to the newest versions (15.7 and 1.16) because of known bugs with SSDT 2017. They are working on a fix that will be out with 15.7.2 but it's not out yet.
Info for the edit:
https://developercommunity.visualstudio.com/content/problem/246732/ssdt-1560-installer-the-configuration-registry-key.html
I found that Daniel's method worked, but I had to install Python manually to be successful.
After successfully installing the .msis in the payload directory I tried to install the Analysis Services VSIX and I wasn't successful because the installer couldn't install Python 3.6.3. I found the page at the bottom and did the following to successfully install the Analysis, Integration, and Reporting VSIXs.
Check error logs and find what version of Python is the problem.
Manually download and install the proper Python version (my logs said 3.6.3). The name of the executable was python-3.6.3-amd64.exe and I got it from https://www.python.org/ftp/python/3.6.3/python-3.6.3-amd64.exe
Uninstall SSDT extensions from within Visual Studio. I uninstalled all of my previously unsuccessful VSIXs.
Manually install VSIXs. This worked out for me and I am able to use all of the SSDT functionality!
Just to do control testing, I installed Reporting Services with the /repair option and was successful. I think the main issue was the Python error. I think if I would've had Python installed everything would've gone smoothly. This is very frustrating because I got this same Python "error" when first installing Visual Studio 2017 (15.6.7)...expect the "error" was just a caution and didn't prevent me from using Visual Studio. But somehow it prevented the install of SSDT 2017.
I hope none of y'all have to go through this like I did today at work!
Info that helped solve this:
https://developercommunity.visualstudio.com/content/problem/98172/packageidcpython3exex64packageactiondownloadpackag-1.html
I had the same error 0x800703e9 installing SSDT with the SSRS option checked. After trying some of the previous good suggestions unsuccessfully, including using the /layout option to download the package locally, I found that the Visual Studio installer portion of the package needed a reboot to finish. After the reboot, I was able to run Microsoft.DataTools.ReportingServices.VSIX successfully.
I have a similar problem with different error code, but the same
"Failed to execute EXE package problem".
I tried all the solution above to no avail. But, after creating an installation layout out of SSDT-Setup-ENU.exe and then trying to execute vsta_setup.exe as suggested by Daniel. I get to the underlying error message, it's has something to do with Android NDK believe it or not, and since I'm from Syria, any change to these packages should be done through a VPN connection. So the solution was to run Visual Studio 2017 installation layout, remove all these ugly android packages "Android SDKs and NDKs and even the emulators, yes, a nuclear solution since I don't have a VPN connection", and then run SSDT-Setup-ENU.exe /repair. Everything worked just fine.
I hope this might save someone's time after it wasted mine.
My installation came also with a error. I tried the several things mentioned above, but it didn't help. So I was guessing that it could be the disk space of my VirtualBox VM. I made the C: drive bigger and that was the trick.
SSDT requiere:
Hard disk space: up to 130 GB of available space, depending on features installed; typical installations require 20-50 GB of free space.
I have set up a jenkins slave server with cygwin and I'm launching builds on it via ssh.
The build of our project succeeds if run locally as the slave user both in the windows command prompt and in the cygwin command prompt. I can also ssh into the machine as the slave user and run the build successfully.
However, when jenkins runs the build as that slave, it fails trying to compile the first C++ project with the error: fatal error C1902: Program database manager mismatch; please check your installation.
Visual C++ 2010 express, and Visual C# 2010 express are both installed and required for our project to build.
In my research I found some indications that cygwin does not handle the remote login correctly here: https://java.net/projects/hudson/lists/users/archive/2008-10/message/130
Has anyone else solved this problem?
Try below solution
Use “Launch slave agents via Java Web Start” to add windows slave to jenkins master.
It will launch Jenkins service on windows machine using some local users account. Then change local user to the user you are using to build locally.
The problem with “Launch slave agents on Unix machines as SSH” method is, it runs connection using “cyg_server” user.
We've set up a new TFS 2012 Build Server and we are just not able to get it working. No queued builds show any progress even if the Build Controller and Agent are configured and enabled.
When we click the "Details" link on the Build Configuration node in the TFS Admin Console we get the error "HTTP Code 500: System.ServiceModel.ServiceActivationException".
How do we fix this?
P.S. We've installed on Windows Server 2012.
Found the problem. Not multiple host headers but only SSL binding on app tier - tweaked web.config for this. We have build and logs, yippee!