Failed to start process with commandline VSIISExeLauncher.exe - iis-express

I just updated my project from ASP.Net Core from 2.1 to 2.2.
When I start debugging my application using visual studio.
My application compiled and run.
Suddenly, it stopped and exited debugging mode.
When I checked Event Viewer, there is an error displayed:
Application '/LM/W3SVC/2/ROOT' with physical root '(my project path)' failed to start process with commandline 'c:\program files (x86)\microsoft visual studio\2017\community\common7\ide\extensions\microsoft\web tools\projectsystem\VSIISExeLauncher.exe -argFile "(temp)\tmpED0C.tmp"' with multiple retries. The last try of listening port is '44386'. See previous warnings for details
Any helps ?
Thanks,

Related

TFS build giving error - The active Test Run was aborted because the execution process exited unexpectedly

We are using Visual Studio 2019 and TFS server 2015.
TFS build is giving below error:
Error: The active Test Run was aborted because the execution process exited unexpectedly. The test execution process crashed while running the tests. To investigate further, open file:///C:/Users/username/AppData/Local/CrashDumps/TE.ProcessHost.Managed.exe.11108.dmp file in Visual Studio and choose "Debug in mixed mode".
##[error]VSTest Test Run failed with exit code: 1
##[error] at Microsoft.TeamFoundation.DistributedTask.Task.Internal.PowerShell.InvokeVSTestCmdlet.ProcessRecord()
##[error] at System.Management.Automation.CommandProcessor.ProcessRecord()
If we uncheck Code coverage enable checkbox, then build gets successful, its failing when we enable that check box.
Observation: Recently on server, Visual Studio Build Tools 2022 (17.2.5) got updated. After that TFS builds not working.
Please someone help to solve this issue.

Cannot debug with Visual studio 2019 -HTTP Error 500.0 - ANCM In-Process Handler Load Failure

I am trying to debug my own application, but when I launch it with the VS2019, he shows me this message:
HTTP Error 500.0 - ANCM In-Process Handler Load Failure.
At the beginning I had found on the internet that it is necessary to modify in the web.config the hostingModel from "InProcess" to "OutProcess" but I could no longer launch the application.
After that, I tried to run the application with dotnet run with command line,the ANCM In-Process Handler Load Failure is gone and in the same time i runned the application from VS2019,the error is gone also.
My application work now in Localhost with two Different Ports.
My problem now is When i made some change in my code i have to repeat this procedure to access debug :
shutdown application from command line (if its already up)
rebuild app with command line or IDE
execute dotnet run with command line
launch it with debugger of IDE
if anyone encountered such a problem, how did they solve it
By any chance, did your project name end with the characters "dotnet", like "myappdotnet.csproj"? I discovered that when trying to run any project that ends in those characters, IIS Express throws this exact error.
Unfortunately, I have no idea where this would be documented--if it is.

Build solution and start IIS Express with .bat file (without opening Visual Studio)

For local development purposes, I'd like to just run a .bat file to build my solution and run it on iis express.
Here's what I've got:
call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars32.bat"
devenv "C:\Path\To\Solution.sln" /build debug
echo "Web build completed. Launching IIS..."
CD "C:\Program Files (x86)\IIS Express\"
iisexpress /path:C:\Path\To\Webroot /port:58389 /clr:v4.0
This does indeed successfully build the solution and start iis express.
Here's my output:
[vcvarsall.bat] Environment initialized for: 'x86'
Microsoft Visual Studio 2017 Version 15.0.28010.2050.
Copyright (C) Microsoft Corp. All rights reserved.
1>------ Build started: Project: PDS.Utilities, Configuration: Debug Any CPU ------
2>------ Build started: Project: PDS.Ibex, Configuration: Debug Any CPU ------
...
========== Build: 11 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
"Web build completed. Launching IIS..."
Copied template config file 'C:\Program Files (x86)\IIS
Express\AppServer\applicationhost.config' to 'C:\Users\CXSVH9\AppData\Local\Temp\2\iisexpress\applicationhost2018116141435830.config'
Updated configuration file 'C:\Users\CXSVH9\AppData\Local\Temp\2\iisexpress\applicationhost2018116141435830.config' with given cmd line info.
Starting IIS Express ...
Successfully registered URL "http://localhost:58389/" for site "Development Web Site" application "/"
Registration completed
IIS Express is running.
Enter 'Q' to stop IIS Express
When I fire up localhost, I get the following output in Command Prompt:
Request started: "GET" http://localhost:58389/login.aspx
Request ended: http://localhost:58389/login.aspx with HTTP status 200.0
Request started: "GET" http://localhost:58389/login.aspx
Request ended: http://localhost:58389/login.aspx with HTTP status 200.0
200's. So, that's good.
But in the browser, I get the message: "Requested view is not available" (a message peculiar to my environment, I'd guess — I just started with this codebase).
Of course, if I start the project from inside Visual Studio, everything works fine. But, as a frontend dev, I'd rather skip that and just fire the project up with a script and use VS Code to edit my static files.
Any thoughts on why this is not loading assets from my web project?
The really frustrating thing is I had this working before, but accidentally deleted my original .bat file and can't get things sussed again.
UPDATE
When I clear cache in the browser, it does GET all my assets with 200's. But still, "Requested view is not available."
Let me somewhat sheepishly answer my own question: I needed to start an additional web service that our website depends upon. This was as simple as writing another batch file to start that web service using the same technique above, but changing the path and the port to their appropriate values.

Visual Studio 2015 Docker Integration wont attach for debuging

I created a Default .net Core RC2 MVC app using VS 2015. I added Docker Support so I could run and debug it in docker.
When I run the project it builds the docker container and starts it. Running the command "docker ps" shows the container running with the correct ports mapped. However I get the following error:
The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use NETStandard [version ...] or newer. This might be expected if the target process did not run.
Also trying to access the web page returns the following error:
[Fiddler] The connection to '10.0.75.2' failed.
Error: ConnectionRefused (0x274d).
System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it 10.0.75.2:80
Turns out the problem is related to the docker for windows beta I am running. By default it does not let you map volumes.
To enable open the docker for window settings:
And select Manage shared drives.
Select the C drive or drive you have the .Net code stored on and rebuild and deploy the project:

Playback.initialize() method failed in test Agent 2013 installed machine

I have created a Winform App to Run Coded UI test scripts recorded in VS2013. Its finely running in the VS2013[update 4] installed machine. But when try to run this in Test Agent 2013 installed machine, the exception has been thrown at Playback.Initialize() method , as "The following package failed to load: "C:\Program Files (x86)\Common Files\Microsoft Shared\VSTT\12.0\Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll"
I tried adding this dll in the reference but still the problem persists. I have added the following references. And I am sure that these dlls are available in the mentioned path.
Microsoft.VisualStudio.QualityTools.CodedUITestFramework.dll
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll
Microsoft.VisualStudio.TestTools.UITest.Common.dll
Microsoft.VisualStudio.TestTools.UITest.Extension.dll
Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll
Microsoft.VisualStudio.TestTools.UITest.Framework.dll
Microsoft.VisualStudio.TestTools.UITest.Playback.dll
Microsoft.VisualStudio.TestTools.UITesting.dll*
In that machine, only Test agent 2013 is installed and Configured for "Interactive Process" . Neither Test Controller is installed nor configured with any other test Controller installed machine.
I tried to Run the scripts with MStest using Command Line. Its running.
I have tried a lot by adding/removing many Coded UI dlls. But still the problem persists. Did I miss something? Thanks in advance.

Resources