I've been working on creating reproducible development virtual machines for my team's work on Xperience CMS with the Hashicorp Vagrant tool. In this environment, the Xperience 13 administrative backend is encountering a runtime error upon startup, as can bee seen in the attached screenshot. I can confirm that the CMS connection string is correct because I have been able to successfully run an Xperience MVC Core site in the very same environment with the very same connection string. I have also used the exact same connection string to directly open a SQL connection using PowerShell in the exact same environment.
Things I have tried to diagnose the issue:
I have tried increasing the execution timeout to the maximum allowed value. The runtime error still occurs, and long before the timeout's default value of 2400 seconds.
I have tried attaching the Visual Studio debugger. The debugger reported "'CMS.DataEngine.ApplicationInitException' in CMS.DataEngine.dll" but no further details or stack trace.
I have confirmed the correct firewall passthrough rules are in place.
I have completely turned off Windows Firewall.
The environment is running on Hyper-V inside a Windows 10 host. The guest development environment has the following specs:
Windows 11 Pro 21H2
16GB RAM
200GB Virtual Drive
11th Gen Intel(R) Core(TM) i7-11800H # 2.30GHz 2.30 GHz - 4 virtual processors
SQL Server 2019
All required IIS features enabled for XperienceCMS
.NET Framework 4.8
Kentico Xperience CMS 13 Hotfix 47
I'm running out of ideas to diagnose this problem.
It was an NTFS folder permissions issue on inetpub\wwwroot that either wasn't being applied or wasn't being propagated down the hierarchy. IIS_IUSRS needed Modify permissions. Setting then resetting Modify, Read, and Execute permissions and propagating them down to subfolders and files solved the issue.
Related
Windows 10 Pro, v1803 Build 17134.648, 64-bit. Hyper-V Manager v10.0.17134.1.
I have had Hyper-V running on my Windows 10 machine for many months, but recently have had an error when starting my VMs up: Microsoft VmBus (Instance ID [long GUID]): Failed to Power on with Error 'The system cannot find the path specified.'.
(Note: I have moved my default Virtual Hard Disks and Virtual Machines folders to a harddrive that is not my C: due to space limitations.)
(clarification) While Hyper-V can see existing and new VMs, it cannot start any of them without throwing the above error. This applies to machine that pre-existed prior to the first error, or were newly created using Quick Create (with default settings.) There are no devices in the VM settings that indicate they are in error, and the VHD is found in the location the settings indicate it should be.
I have no idea what the path is that it's claiming it cannot find. I can find confirmation in the Event Logs, but no additional clues. In Applications and Services Logs/Microsoft/Windows/Hyper-V-Worker/Admin, I see the two error event IDs 12010 ['Windows 10 Dev Environment' Microsoft VmBus: Failed to Power on with Error 'The system cannot find the path specified.' (0x80070003).] and 10230 ['Windows 10 Dev Environment' failed to start.].
Can someone please give me a clue where I can look to confirm what "path specified" it's looking for, and how I can provide it, or change it?
Thanks to all who tried to help, but I have since abandoned this entirely. I have purchased a new machine, which I will be installing a new Windows 10 environment onto, and will start Hyper-V completely from scratch on that box, then after confirming that Hyper-V functions correctly, I will import my VMs to there.
I'm trying to debug an ASPNET Core/EF Core website hosted on Azure. When I try to attach the debugger in VS 2015, via Cloud Explorer, I get this error message:
Yet when I check the site in the Azure portal, it sure seems like it's 32 bit and set to enable remote debugging:
So what am I missing or doing wrong?
Portal setting controls the bitness of the IIS w3wp process. But ASP.NET Core runs in its own process, so that setting has no effect on it. Instead, what determines whether your .NET Core process runs as 32 or 64 bit is how you publish it.
Given that apparently your Core project is published as 64 bit, you might want to try switching the Portal setting to 64 bit. This will affect the debugger MSVCMON.exe process, which should then allow you to attach.
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?
This is problem with deleting a printer driver in windows 8 pc.
Our applicaton is working fine in UI Level deployment, we have installed and uninstalled successfully.
we have tested our Application in Windows 8 (32 and 64 bit) from UI Level and as well as PUSH Deployments.
But in PUSH (Active Directory deployment), "OpenPrinter()" function is failed to get the handle of requested printer driver. Then the deleteprinter also failed.
We have verified that the function is getting perameters as we expected. But it is failed.
Since the issue is happening only in Windows 8.
Servers are Windows 2003 and Windows 2008 r2 and Deploying per mechine basis.
Application developed in VC++ (VS 2008) and packaged with InstallShield12.
In our investigation we have found that Registry is not accessible to 'Openprinter()' function and it is failed to return the handle.
While we install the applicaton from PUSH, it is installing with SYSTEM account. We have verified this.
Is there any limitations to use the registry in Windows 8 PC?
or do we need to fix/set/configure any settings in Windows 8 PC?
or Is there any forbidden to access the registry for SYSTEM account?
Please help me to resolve the issue.
Thanks in advance.
Registry is not accessible in Windows 8 (32/64 bit) while active directory deploymentFinally things are broken out..The main reason is openprinter API depends on registry to get the handle for requested printer.By the time we have called the API, the registry is not available for it. when we have waited to complete 2 minutes, the API returns the handle.hence my PUSH uninstall is completed with out hang. Now problem is solved in my case.But it is a limitation with Windows 8.
I'm running Visual Studio 2010 and IIS 7.5
My site accesses a specified servers hardware for some statistical analysis.
When I debug my site in Visual Studio, I can access other servers hardware information with now issue. When I publish the site to IIS running as ASP.Net 4.0 appPool because the site is written under the 4.0 framework, the hardware retrieval fails. (note: when I run the site and analyze the local machine hardware, it works perfectly... the problem lies in analyzing another machine on the network.)
My question is, What is the difference in permissions a site is running under when debugging in Visual Studio in comparison to a published site in IIS 7.5?
Things I've tried...
Changing the app pool identity to every possible built in option, and my own domain profile, which is local admin on the machine I'm trying to retrieve hardware info about.
Changing the user that access the file directory of the website.
Changing app pools period. (The site has to run under .net 4.0, or else it barks out bad things).
I'm thinking I may need to install the site directly on the server that's being analyzed, but I find it odd that I can get all the data from other machine when I'm debugging. Any insight someone could bring would be greatly appreciated. Thanks!!
This answer is, in some cases, you have to add the appPool identity running the site to the "Performance Monitoring" group for the local machine in order to allow an ASP.NET site access the server's local hardware resources...