UPDATED BELOW
I have went trough several (if not all) posts mentioning this error on SO and google, but still having this issue. The error I get is:
Process with an id of x is not running
In addition I can notice this error in my VS output window as well:
The program '[11392] iisexpress.exe' has exited with code 0 (0x0).
The program '[11392] iisexpress.exe: Program Trace' has exited with code 0 (0x0).
Where the number is always the same as the PID mentioned in the original error.
I have checked and no, the PID is not used by any process, I have done a ton of stuff like proposed in here, here, here, here and some others ...
This is for all my Web projects (newly created from scratch or old ones).
So with a WPF for example this is working fine.
So this must be something IIS related i think, uninstalled it, reinstalled it had not effect, neither did renaming/removing the IISEXPRESS folder in documents or checking all options in CPanel => Turn features on/off for the IIS options and tons of other things I tried like adding environment variable
_CSRUN_DISABLE_WORKAROUNDS
run as admin, removing the .vs folder, removing the
IISUrl , DevelopmentServerVPath & DevelopmentServerPort
parts in the .csproj file or checking the
Tools menu > Options > Projects and Solutions > Web Projects > Use the 64 bit version of IIS Express
even uninstalled all my VS versions and reinstalled only 1 VS Enterprise 2017 ...
I'm completely lost here, what's happening?
Any suggestion is welcome!
UPDATE 1:
I have uninstalled the IISExpress 10 and installed the version 8, still the same issue.
This is what Event viewer is logging:
Log Name: Application
Source: Application Error
Date: 01/06/2019 09:33:00
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: PCName
Description:
Faulting application name: iisexpress.exe, version: 8.0.8418.0, time stamp: 0x4fbae3d6
Faulting module name: ntdll.dll, version: 10.0.17763.475, time stamp: 0x3230aa04
Exception code: 0xc0000008
Fault offset: 0x00000000000a356a
Faulting process ID: 0x2d68
Faulting application start time: 0x01d5184c3d470917
Faulting application path: C:\Program Files\IIS Express\iisexpress.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: cce33ecf-9507-42ab-87bf-9482a39181e9
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-01T07:33:00.972839500Z" />
<EventRecordID>58319</EventRecordID>
<Channel>Application</Channel>
<Computer>PCName</Computer>
<Security />
</System>
<EventData>
<Data>iisexpress.exe</Data>
<Data>8.0.8418.0</Data>
<Data>4fbae3d6</Data>
<Data>ntdll.dll</Data>
<Data>10.0.17763.475</Data>
<Data>3230aa04</Data>
<Data>c0000008</Data>
<Data>00000000000a356a</Data>
<Data>2d68</Data>
<Data>01d5184c3d470917</Data>
<Data>C:\Program Files\IIS Express\iisexpress.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>cce33ecf-9507-42ab-87bf-9482a39181e9</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
UPDATE 2:
I have tried running VS 2017 Enterprise in SafeMode and it gives me this error:
I will investigate this error further, please, if anyone has any idea, post it!
I have the same problem. Here are some of the things I've done that haven't worked:
Delete the .vs folder in my project
Delete the IIS Express folder in My Documents
Add _CSRUN_DISABLE_WORKAROUNDS to your environment variable
Restart the computer
Restart Visual Studio
Change the port
Even re-install visual studio
Uninstall IIS 10.0 Express via Control Panel, then reinstall
I've tried almost all the solutions I got from several forums and none of them have worked.
Finally I found the source of the problem. The source of the problem is not from my project nor from my visual studio, but from my IIS.
When I open iisexpress.exe from C: \ Program Files \ IIS Express, the command prompt closes immediately. If your IIS Express is fine, then what will appear is as shown below.
iisexpress.exe if success
What I do is reset or reinstall IIS Express via Turn Windows Features on or off in Control Panel. And follow the step by step contained in the following link
My worked solution
This is the only way that worked for me, and hopefully it will help the others too.
For me problem was in different version of .net version on machine where i was trying to start project.
VS Solution was created on .net 6.o.5 version and after transferring solution to pc where o.6.4 only installed - issue with process occurs.
After updating .net to correct version issue is gone.
P.S. method with deleting the .vs folder does not help.
P.S.2 VS2022
Related
I am having an issue when I try to publish a specific solution.
Related into:
I have been able to publish/deploy about 6 solutions with no issues.
The solution that is giving me issues when I try to Publish runs 100% on my local VS 2019, the issue is publishing
This is my first solution I created from new on VS 2019. All others were created on VS 2017
I can run in browser - https://api.nuget.org/v3/index.json
I did try to Run a NuGet package restore
I did try to implement different solutions I found while researching
If you google search for the error of “The request was aborted: Could not create SSL/TLS secure channel” you will see a lot of articles. I tried the solutions detailed with obviously no luck.
...
1>------ Publish started: Project: HFSPackagesApi, Configuration: Release Any CPU ------
Connecting to C:\deployments\HFSPackagesApi...
Determining projects to restore...
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\NuGet\NuGet.targets(128,5): Error : Unable to load the service index for source https://api.nuget.org/v3/index.json.
An error occurred while sending the request.
The request was aborted: Could not create SSL/TLS secure channel.
C:\Program Files\dotnet\sdk\3.1.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): Error NETSDK1004: Assets file 'F:\source\BitBucket\gmborl\LiveBackup\ReleaseInsightApp\HFSPackagesApi\HFSPackagesApi\obj\publish\win-x64\project.assets.json' not found. Run a NuGet package restore to generate this file.
1>Build failed. Check the Output window for more details.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
...
Fixed it in Windows 7 by doing these steps, outlined in Support Article:
Step 1
Add a DWORD registry entry called DefaultSecureProtocols with a value of 0x00000a00 to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
Note: Second one (in Wow6432Node) is needed only on 64-bit Windows.
Step 2
Created sub keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
In each of them add a DWORD entry called DisabledByDefault with a value of 0.
Note: You may need to create the TLS 1.x key and also the Client key.
After getting my Window 10 laptop operational with VS 2019 I am able to publish my solution.
This is no longer an issue.
I had the same problem. The OS is windows 7 profession service pack 1. When I published the ASP NET CORE project on IIS, the problem happened.
I solved it with the following steps.
First, I searched the https://api.nuget.org/v3/index.json on browser, it worked.
Second, I followed the solution from user11693, and I solved it.
Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html
I've seen a few related questions on stackoverflow that relate to this one, but none of them seem to address the specific behavior I'm observing.
I have a Windows Service defined as follows in a Wix 3.0 .wxs file.
<Component Id='Service' Guid='3c658a54-b236-11e0-bbf6-039615e482ae' >
<File Id='ServiceEXE' Name='m_agent_service.exe'
Vital='yes' Source='..\m_agent_service.exe'
KeyPath='yes' />
<ServiceInstall Id='MerakiServiceInstall'
Vital='yes'
Name='MerakiPCCAgent' DisplayName='Meraki Client Insight Agent $(env.VERSION)' Description="Meraki Client Insight Monitoring and Management Service"
Type='ownProcess' Interactive='no' Start='auto' ErrorControl='normal'>
</ServiceInstall>
<ServiceControl Id='MerakiServiceControl'
Name='MerakiPCCAgent'
Start='install' Stop='both' Remove='uninstall'
Wait='yes' />
</Component>
When I install the .MSI, the service is installed and running. Great.
When I then uninstall (either by running msiexec /x or using the Add/Remove Software from the Control Panel), the service keeps on running and is not removed. In fact, the log of the service itself tells me that none of the service shutdown code has been invoked. (When I use "sc stop", for example, I do see service shutdown code running cleanly.)
Here are some salient parts from the msiexec /x uninstall log:
MSI (s) (14:04) [11:33:54:692]: 1 application(s) had been reported to have files
in use.
Info 1603. The file C:\Program Files\Meraki\PCC Agent 1.0.67\m_agent_service.exe
is being held in use by the following process: Name: m_agent_service, Id: 3120,
Window Title: '(not determined yet)'. Close that application and retry.
MSI (c) (40:78) [11:33:54:692]: File In Use: -m_agent_service- Window could not
be found. Process ID: 3120
MSI (c) (40:78) [11:33:54:692]: No window with title could be found for FilesInUse
[...]
Action start 11:33:57: UnpublishFeatures.
MSI (s) (14:04) [11:33:57:379]: Doing action: StopServices
MSI (s) (14:04) [11:33:57:379]: Note: 1: 2205 2: 3: ActionText
Action ended 11:33:57: UnpublishFeatures. Return value 1.
Action start 11:33:57: StopServices.
MSI (s) (14:04) [11:33:57:379]: Doing action: DeleteServices
MSI (s) (14:04) [11:33:57:379]: Note: 1: 2205 2: 3: ActionText
Action ended 11:33:57: StopServices. Return value 1.
Action start 11:33:57: DeleteServices.
MSI (s) (14:04) [11:33:57:379]: Doing action: RemoveFiles
[...]
MSI (s) (14:04) [11:33:57:645]: Product: Meraki Client Insight Agent -- Removal
completed successfully.
MSI (s) (14:04) [11:33:57:645]: Windows Installer removed the product. Product N
ame: Meraki Client Insight Agent. Product Version: 1.0.67. Product Language: 103
3. Removal success or error status: 0.
Oh dear, whilst on the loo I had a brainwave and I think I have fixed it myself after all – sorry for the post! I think I shall explain what fixed it though in case any other beginners following the same Wix book as me run into the same issue.
Basically, I changed the Guid on my component, reinstalled, uninstalled and it all worked again. (I take on board that changing Guids may not be best practice, but this worked for me.)
To elaborate, I think there was actually no problem at all with my installer – the problem was on the PC I was using to test the installation. My first attempt at installing this windows service was done with no ServiceControl element, just the ServiceInstall element. I then tested the install, and it worked, but the service didn’t remove itself on uninstall, obviously. I then manually stopped and uninstalled the service from my PC using Services.msc.
I then read the next section of my book, realised I also needed a ServiceControl element, created it and re-tried the installer – but I was using the same Guid. The uninstall still didn’t work correctly and I assumed I’d done something wrong in my installer, hence the post above.
What I’m guessing had happened is that the previous install, using the same Guid but without the ServiceControl element, caused my PC to get corrupted somehow and prevented the new uninstaller from completing properly.
Let this be a lesson to me – never test your installer on your own PC! One of those rules I fully understand and happily ignore, till it bites me :)
Check the verbose log file and ensure the Component is being changed. It is possible the Feature is turned off or a Component/Condition is causing the Component to be skipped.
Hello I am trying to package and start up azure developement fabric on a windows 2008 server, I am so close yet still far. The steps I take are
1) run cspack.exe command /copyOnly to generate the .csx folder
2) run csrun.exe commmand /LaunchBrowser to start up the developement fabric and startup the browser
the error is as follows
System.BadImageFormatException: Could
not load file or assembly
'Interop.SSCE' or one of its
dependencies. An attempt was made to
load a program with an incorrect
format.
== Pre-bind state information === LOG: User = IP-0AE2B2DF\Administrator LOG:
DisplayName = Interop.SSCE (Partial)
LOG: Appbase =
file:///C:/Users/Administrator/Documents/Visual
Studio
2010/Projects/MyAzureProject/src/AzureCloudService/ServiceDefinition.csx/roles/MyAzureProject.Web/approot/
LOG: Initial PrivatePath =
C:\Users\Administrator\Documents\Visual
Studio
2010\Projects\MyAzureProject\src\AzureCloudService\ServiceDefinition.csx\roles\MyAzureProject.Web\approot\bin
Calling assembly : (Unknown).
=== LOG: This bind starts in default load context. LOG: Using application
configuration file:
C:\Users\Administrator\Documents\Visual
Studio
2010\Projects\MyAzureProject\src\AzureCloudService\ServiceDefinition.csx\roles\MyAzureProject.Web\approot\web.config
LOG: Using host configuration file:
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Aspnet.config
LOG: Using machine configuration file
from
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config.
LOG: Policy not being applied to
reference at this time (private,
custom, partial, or location-based
assembly bind). LOG: Attempting
download of new URL
file:///C:/Users/Administrator/AppData/Local/dftmp/s0/deployment(98)/res/deployment(98).AzureCloudService.MyAzureProject.Web.0/aspNetTemp/aspNetTemp/root/dfbc079a/82bed8d5/Interop.SSCE.DLL.
LOG: Attempting download of new URL
file:///C:/Users/Administrator/AppData/Local/dftmp/s0/deployment(98)/res/deployment(98).AzureCloudService.MyAzureProject.Web.0/aspNetTemp/aspNetTemp/root/dfbc079a/82bed8d5/Interop.SSCE/Interop.SSCE.DLL.
LOG: Attempting download of new URL
file:///C:/Users/Administrator/Documents/Visual
Studio
2010/Projects/MyAzureProject/src/AzureCloudService/ServiceDefinition.csx/roles/MyAzureProject.Web/approot/bin/Interop.SSCE.DLL.
ERR: Failed to complete setup of
assembly (hr = 0x8007000b). Probing
terminated.
this error happens with 2 dlls Interop.SSCE.DLL and SqlLite.dll Ive replaced all references to SqLite dll with a 64bit version and I dont have any references anymore to Interop.SSCE.DLL since I am not using it. Manually deleting these assemblies from the location
"C:\Users\Administrator\Documents\Visual Studio
2010\Projects\MyAzureProject\src\AzureCloudService\ServiceDefinition.csx\roles\MyAzureProject.Web\approot\bin"
solves the issue, but I dont obviously want to manually delete these everytime as I trying to automate a build process. My question is then how is the .csx folder actually generated and will this give me clues as to where these dll's are bring copied from? This is really frustrating as with the exception of those dll errors, I =m able to package the solution and startup the developement fabric with no other problems. Please Help!!
I realize this is old, but I just ran across it while trying to solve the same problem. In my case, the issue was that some of my projects were set to build x86 assemblies, instead of Any CPU. The solution was:
Go to Build -> Configuration Manager
Make sure "Active solution platform" is set to "Any CPU"
Make sure each of the projects also has the "Platform" set to "Any CPU"
Rebuild
Go to:
Tools > Options > Projects and Solutions > Web Projects
Check the Use the 64 bit version of IIS Express for web sites and projects.
This will ensure that your web project runs in x64 mode and will thus be able to use Service Fabric files.
Hope it helps...
I have nant set up to build my ASP.NET MVC project and it works fine locally. I add nant to a tools folder and add it to version control. TeamCity picks up my changes and starts the build but it fails.
I believe I'm using the latest version of Nant and I have added the .net framework 3.5 to the nant.exe.config. What am I missing on the server and yes the .net framework is installed on the server as the asp.net mvc app does work if I manually build and deploy there?
The build file is as follows:
<target name="compile" description="Compiles using the AutomatedDebug Configuration">
<msbuild project="Tolt.Sims.sln" />
</target>
Here is the error:
BUILD FAILED Failed to initialize the 'Microsoft .NET Framework 2.0' (net-2.0) target framework.
Property evaluation failed. Expression: ${path::combine(sdkInstallRoot, 'bin')} ^^^^^^^^^^^^^^ Property 'sdkInstallRoot' has not been set.
For more information regarding the cause of the build failure, run the build again in debug mode. Try 'nant -help' for more information
If you're using the beta version of NAnt (which currently is the only way you'll get support for targeting anything greater than the 2.0 framework), you maybe running into a registry problem. A similar problem was reported by Tim Barcz.
Things pretty much boiled down to NAntContrib (provider of msbuild task) pointing to the 2.0 version of msbuild. Check out his solution to see if it applies to your scenario.
Potentially, you dont have the .NET Framework 2.0 SDK installed.
You can install it from
http://www.microsoft.com/downloads/details.aspx?familyid=fe6f2099-b7b4-4f47-a244-c96d69c35dec&displaylang=en
I fixed this by adding the following in the registry:
New string value at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework
Named: sdkInstallRootv2.0
With the value: C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\
Seemed to spring into life...
w://
This was fixed after the 0.86 beta1 release. On April 1, 2010, 0.90 was released with the fix in case upgrading nant is an option for you. To provide further detail, the fix release in 0.90 appears to have been simple changes to the nant.exe.config file. The bolded text below was added and will likely fix the problem without having to install the 2.0 SDK.
<directory name="${path::combine(sdkInstallRoot, 'bin')}" if="${property::exists('sdkInstallRoot')}" />
Update the net-2.0 section to fix it.
See http://www.mail-archive.com/nant-developers#lists.sourceforge.net/msg07519.html; it's a known bug in 0.86 beta1.
I've run into similar issues with NAnt. I know this isn't the Best solution, but it is one that works if you need to get your project moving.
I've found that installing a development environment (C# Express didn't work for me, but VS 2008 did) on the server makes this issue go away. (Yes, I realize this goes against normal best practices, but it works and lets my scripts run so I can get back to coding.)
Just figured I'd share incase anyone else is in a similar situation..(this has worked for me both with CruiseControl.Net and with Hudson).