I am receiving an intermittent (but extremely frequent) error when attempting to debug my web app using Visual Studio 2012 and IE 11 via f5.
The error is a message box: "Unable to start program 'http://localhost:36422/default.aspx'. Access is denied."
Internet explorer opens, but no page is loaded.
If I retry enough times, it will eventually succeed, my app loads and I can debug.
I have noticed via task manager that when the error occurs, the internet explorer process is hanging around after I close it. The number of ie processes continues to build up until I have to kill them.
I am getting a large number of errors in my system event log which may be related (although an entry is not generated every time the error occurs):
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-00805F2CD064}
and APPID
{9209B1A6-964A-11D0-9372-00A0C9034910}
to the user my user name SID (S-1-5-21-1364137996-2577644926-3768900005-1179) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
A google search of the guid indicates that the application in question is Machine Debug Manager.
I have tried adding the interactive user to the access permissions for Machine Debug Manager using dcomcnfg and rebooting my pc to no effect.
Related
I had a Windows 2008 Server which was being used as Application server that has recently been upgraded to Windows 2012 -> Windows Server 2016 -> Windows Server 2019.
All of the applications under IIS work, but one. I am trying to figure out what is wrong. I have installed Visual Studio 2019 Remote Debugging tool on the server and trying to attach to the erroneous project under IIS.
I have the Remote Debugger running
but when I try to attach to remote process the Application pool and user names do not show up in the "Attach to process" window.
Since I can not see the details I can not connect to my application and debug. I am sure that "Show processes from all users" is checked.
I know that if the application does not run on the server it does not show up in this list, but I have called other applications under the site which are running but they don't appear either.
Try run the remote debugger under the different user account:
You can stop the remote debugger and restart it with the account you are using on the local computer.
You can start the remote debugger from the command line with the /allow parameter: msvsmon /allow username#computer
You can add the user to the remote debugger's permissions (in the
remote debugger window, Tools > Permissions).
If you can't use the methods in the preceding steps, you can allow
any user to do remote debugging. In the remote debugger window, go to
the Tools > Options dialog. When you select No Authentication, you
can then check Allow any user to debug. However, you should use this
option only if you have no choice, or if you are on a private
network.
I'm trying to add snap into Microsoft Management Console in windows 10. But when I try to add certificate, an error message is coming with the header Microsoft Management Console has stopped working:
When I click the Debug button, Visual Studio 2015 gives me a message like this:
I've tried a solution found by google search saying to run sfc/scannow command in command promt but didn't get any result.
So this doesn't address the error itself, but if you were trying to use the snap-in to access the local computer certificate store then there is a work around.
Open up command prompt and type in 'certlm.msc', this should directly open up the local computer certificate store plug-in without having to go through the buggy menus.
I have an MVC core website written in C# which is deployed to an AWS EC2 Instance with Windows Server 2012 R2 and IIS8 deployed on it.
I am trying to remote debug the application as I am getting errors thrown which I don't when running locally (details for another post maybe).
On AWS Console, I have a security group with the following Rules as guided by here:
and when I click on Debug->Attach to process, and browse to my AWS instance, I can see the correct dnx.exe process, however, when I attach to that process,
I get the The breakpoint will not currently be hit. No symbols have been loaded for this document
I've tried going to Tools->Options->Debugging->Symbols and clicking Load all symbols as it is my understanding that since VS2012 the symbols do not need to be deployed, but rather just on the local machine doing the debugging, taken from here.
In versions of Visual Studio before VS 2012, debugging managed code on a remote device required that the symbol files were also located on the remote machine. This is no longer the case. All symbol files must be located on the local machine or in a location specified in the Debugging / Symbols page of the Visual Studio Options dialog box. See .NET Remote Symbol Loading Changes in Visual Studio 2012 and 2013 on the Microsoft Application Lifecycle blog.
I can see the connections being initiated in the MSVSMON process on the EC2 instance.
I feel like I'm close but I'm just missing one simple thing.
You need to check on which port the Remote Debugger is running and allow inbound traffic on that port by opening Inbound Port [4024 in my case] with a Custom TCP Rule for Remote Debugging.
You can check the port used by Remote Debugger at Tools > Options in the Remote Debugger Menu.
After upgrading from Windows 7 Pro x64 to Windows 10 Pro x64, I cannot start IIS. Most of the Windows 10 system works fine. Some study tells me that the primary problem is that the Windows Process Activation Service (WAS) will not start.
I have another machine that upgraded to Windows 10 with IIS fine (Windows 7 Home Premium x64 up to Windows 10 Home Premium x64).
The IIS on that machine works OK (it only serves one website; so simpler setup.)
I have had NO LUCK finding anything on the Internet that resolves this.
I tried using the clean.iinstall IIS config files (no improvement).
I tried uninstalling IIS - uninstall failed and rolled back (see below).
I tried uninstalling WAS - uninstall failed, and rolled back.
DETAILS:
My first error trying to run IIS Manager program:
One or more problems have been detected during IIS upgrade. As a precaution,
one or more IIS services have been disabled. Please review the following error message:
Data loss has occurred - You upgraded your operating system or switched from one Windows SKU
to another SKU, and data from the previous installation of IIS has been lost or copied incorrectly.
As a result, the services W3SVC and MSFTPSVC have been disabled. Before enabling these services,
you should review the latest IIS 7.0 compatibility information.
(The link to see the IIS 7.0 compatibility information was a dead link.)
I decided to give it a try despite the compatibility warning. I started the services IIS, MSFTP, WAS and W3SVC (depends on WAS), then tried to start IIS Manager.
Failed to connect
There was an error when trying to connect. Do you want to retype your credentials and try again?
Details:
Creating an instance of the COM component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344}
from the IClassFactry failed due to the following error: 800700b7
Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7).
FACTS:
The IIS configuration files exist with non-zero length; they look coherent.
C:\Windows\System32\Inetsrv\Config
ApplicationHost.config
Administration.config
Redirection.config
I have a backup that I made that should be good (not just the automatic backups).
machine.config exists ok: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
The appPools folder exists: C:\inetpub\temp\appPools
The upgrade changed IIS from v7.5 to v10.0.10240.16384
This machine has one user account (me) and the account is marked Administrator.
My previous Windows 7 Pro with IIS 7.5 worked FINE for several years. IIS was giving no trouble before the upgrade.
I can use other network stuff OK: Internet, Outlook, PuTTY, MySQL Workbench (remote & local), and FileZilla.
Trying to start the Microsoft FTP service, or run appcmd or start W3SVC or WAS all give the same error:
Error 183: Cannot create a file when that file already exists.
appcmd list backup --> failed (running as Admin)
ERROR ( hresult:800700b7, message:Command execution failed.
Cannot create a file when that file already exists.)
Event Log after error starting WAS:
The configuration manager for Windows Process Activation Service (WAS) did not initialize.
The data field contains the error number.
error # = B7000780
I used the MS error lookup tool:
To see the appcmd error ( 800700b7)
for hex 0x800700b7 / decimal -2147024713 :
STIERR_HANDLEEXISTS stierr.h
1 matches found for "800700b7"
To see the WAS error (B7000780)
as an HRESULT: Severity: FAILURE (1), Facility: 0x1700, Code 0x780
for hex 0x780 / decimal 1920 :
SQL_1920_severity_10 sql_err
Skipping rebuild of index ID %d, which is on a read-only
filegroup.
ERROR_CANT_ACCESS_FILE winerror.h
The file can not be accessed by the system.
2 matches found for "b7000780"
I tried to uninstall IIS: 11/25
- uninstalled in windows features
- system did the work, I restarted system
- main system booted ok; then it treated the features
- the features uninstall failed at about 85% of total work
"We couldn't complete the features"
- system did a rollback
At reboot time, (some) services statuses are:
IIS runing auto IIS Admin Service (depends on HTTP service)
MSFTP off auto MS FTP Service (ftpsvc)
W3SVC off auto World Wide Web Publishing Service (depends on WAS)
WAS off auto Windows Process Activation Service
NetMsmqActivator off Auto Net.Msmq Listener Adapter
NetPipeActivator off Auto Net.Pipe Listener Adapter
NetTcpActivator off Auto Net.Tcp Listener Adapter
AppHostSvc off Auto Application Host Helper Service
==> THESE AUTO SERVICES ABOVE SHOULD BE RUNNING, BUT FAIL TO START PROBABLY DUE TO THE 'WAS' PROBLEM !
HTTP service is hidden, running:
sc queryex http ==> running
RPC and its dependencies are all OK, running.
I tried to uninstall WAS windows feature:
The system did the uninstall work, restarted, "could not complete features", rolled-back changes
I ran process monitor, but I could not see anything particular to resolve.
11/29 changed out the IIS configuration files, to use the clean.install versions:
C:\Windows\System32\inetsrv\config
I replaced applicationHost.config with applicationHost.config.clean.install (renamed it to the regular name)
I replaced administration.config with administration.config.clean.install (renamed it to the regular name)
I rebooted
I still could not start FTP or WAS, so maybe it's not getting far enough to read the configuration files?
My development workstation is running VS2012 Update 1. The OS is Windows 7 Professional Service Pack 1 x64. I have a laptop running Windows 8 onto which I've installed the VS2012 Remote Debugger. I've started msvsmon and it's quietly sitting in the system tray or what passes for it on Windows 8.
I have set up a breakpoint in VS2012 at a location where I need to do some debugging. In VS2012, I click on Debug | Attach to Process... I get the dialog showing the list of processes running on my machine. I change the machine name to the name of the Laptop.
I am having two different problems:
Problem 1:
With Windows Firewall running, VS2012 connects to the remote debugger server. I see the list of the processes running on the Laptop. I choose the one I want to debug and click Attach. I get "Unable to attach to process. The RPC server is not available."
What's going on here?
Problem 2:
I turn off Windows Firewall on my desktop. When I try to connect to the process running on the laptop, it connects and loads all of the symbols. So far so good. Once all of that is finished, I perform the action that would cause my breakpoint to be hit. The process on the remote machine freezes, but so does VS2012. I've sat here as long as 10 minutes waiting with no change. At that point, I kill msvsmon on the remote machine and my program goes away with it, but VS is still locked up.
Any ideas??
I have faced a similar issue in VS 2013 showing the message "Unable to attach to process. The RPC server is not available".
I have resolved this by un-checking the "Use Managed Compatibility Mode" option from Debug > Options and Settings > General Tab.