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?
Related
This is regarding Abbyy Setup issue that we are facing on a Azure Cloud Machine which is a Windows Server 2019 VM.
We followed the Admin Guide for Reader 12, the "Manual Runtime Installation Steps" were followed for the setup. The Bin64, Data and Inc folders are copied into a directory which will be later used while registering FREngine.dll on the OS. We have not done the Abbyy SDK installation.
We have VM setup locally which is a Windows Server 2019 VM image. On this setup we are able to Register the FREngine.dll successfully using regsvr32 command. Also we don’t see any issue and is working, w.r.t reading OCR/Barcode values successfully through Abbyy FineReader.
ISSUE
The issue is on the Azure Cloud System [VM Windows Server 2019], where we are able to Register the FREngine.dll successfully using regsvr32 command. However even with the successful Registration of FREngine.dll, when we try to initialize the FREngine, we are getting an exception "Invalid Engine instance" during the call to InitializeEngine( ) with all the Required parameters set.
// Create the abbyy engine instance in outproc process,
// as its recommended by Abbyy for 64-bit process
outProcLoader = new OutprocLoader();
if (outProcLoader != null)
engine = outProcLoader.InitializeEngine(AbbyyEngineUtils._strProjectId,
engLicensePath,
AbbyyEngineUtils._strEngPwd,
"", "", true);
Here we have a license file which is also copied into the location where FREngine.dll is present.
Due to this initial Step failure Abbyy Logs could not be generated from the codebase. However we see a log file that gets generated from Abbyy in the path “C:\ProgramData\ABBYY\SDK\12\FineReader Engine\” at this point of failure which states as follows:
10552 :ABBYY Licensing Service is unavailable: The RPC server is
unavailable.
We also we additionally tried running the Abbyy SDK’s Sample applications on this machine. This also fails with the above error during Abbyy Engine Initialization.
How can this be resolved?
More Info on Licensing Service:
We additionally tried installing the LicensingService and the LicensingSettings.XML had :
ProtocolType="LocalInterprocessCommunication" />
Here Ours is a Standalone Abbyy Installation and hence the Protocol Type used is LocalInterprocessCommunication which is for the local Licensing Service. It is not necessary to specify this protocol type for Standalone installation, as Standalone licenses are always used with the LocalInterprocessCommunication protocol type.
This was an additional Step tried by us. However the actual issue was with the Abbyy Licensing on Azure.
Did you happen to start the abbyy licensing service in the Azure VM ?
(Windows Key + R) Run command --> services.msc
In the Services Dialog, find the Abby...Licensing service.
Right Click -> Properties
You can click on the start and click ok.
Retry your above steps. Also, you could have startup type as Automatic if this works in the services in dialog.
As any other OCR solution some have licensing constraint to run on Azure and AWS , make sure your license is compatible.
as posted here
https://support.abbyy.com/hc/en-us/articles/360016441600-Can-I-run-FineReader-Engine-in-Virtual-Machine-or-Container-
also I would check the OS compatible version.
ABBYY SDK 12 Licensing Service has been tested in the following virtual environments:
Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2
Windows 10, Windows 8.1, Windows 8, Windows 7 SP1
We had a classic ASP application that had to be migrated to a new Windows Server (Windows Server 2012 R2 Datacenter). IIS was already setup and we migrated the files configured the URL and DNS, as well as setting up the classic ASP components for IIS. The web application initially opens okay but the error below pops up on the server continually.
We checked the relevant site was configured to run 32bit and we ensured that in the sites "Debugging properties" the "Enable Server-side Debugging" was set to false. Also, all those testing the site we ensured in Internet Options >> Advanced the two values of "Disable script debugging" were checked. But this did not resolve the error. I believe we have all the necessary components setup in the server roles
I then followed this URL and deleted certain registry entries and restarted the server.
https://learn.microsoft.com/en-gb/visualstudio/debugger/just-in-time-debugging-in-visual-studio?view=vs-2015
This seemed to take away the above error but then the relevant application pool continually stops. I checked the application logs and at each time the application pool stops there is an error stating below
Since creating this ticket I installed DebugDiag 2 and set up a rule for IIS "Crashing". Ran the application until the relevant IIS Application Pool stopped and examined the Dump files created by the rule. All of them appear to have one error concerning "VCRUNTIME140.dll". See image below.
I found that this was a common issue and related to Visual C++ Redistributable 2015. I looked at installed programs and there was versions 2010, 2013 and 2017 installed. Microsoft state that after version 2013 subsequent versions incorporate the last. So I installed the latest version of Visual C++ Redistributable and restarted the server. This made no difference. So I uninstalled the latest version and installed version 2015 and restarted but again the application pool still stops after several actions on the web application.
Does anyone know how do I resolve this please?
I am new to .Net core environment and facing issue while deploying application into IIS.
After publishing code and deploying into IIS server(Version 7), I am able to start application from Kestrel by going into directory where application hosted and running below command.
c:\inetpub\demoapp\dotnet "My App.dll"
By running above command, Kestrel is running on http://localhost:5000 and I am able to browse from browser. I am using latest .Net Core version 2.2.
But when I am trying to execute URL from IIS hosted application, I am getting below error.
HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure
Below is the event log from windows application log.
Application '/LM/W3SVC/49/ROOT/demoapp' with physical root 'C:\inetpub\demoapp\' failed to start process with commandline 'dotnet .\MyApp Web.dll' with multiple retries. The last try of listening port is '2405'. See previous warnings for details.
Anyone having idea how to resolve it?
In my case, It was win-64 architect issue.
You can change or switch architect from win-64 to win-86 then publish and don't forget to change Enable 32-bit Applications in IIS manager:
Right-click on the Application Pool and select “Advanced Settings…”
or select the same from the Actions pane after selecting the
Application pool.
Change the “Enable 32-bit Applications” to True (if you want the
application pool to spawn in a 32-bit mode)
Click OK.
p.s.: Don't forget to delete existing published files.
My environment:
Windows 10 Creator (1703 with current updates to this date)
Visual Studio 2017, Enterprise, 15.3 with most of the goodies turned on.
Windows 2016, again with all current updates.
iis 10 with WebDeploy installed (that's a whole other installation nightmare, suffice it to say that SO helped there and the answers are already out there so I won't go into it here). Turned on ASP.NET 4.6, otherwise mainly accepted the defaults.
My process:
As per the NuGet.Server documentation, create a new ASP.NET MVC project using the "Empty" template and download and install NuGet.Server as specified. I'm using .NET 4.7 as my framework.
Compile and configure as desired (at least ensure you have an api key in place).
Deploy to iis using the "Publish" | Web Deploy option
Try to get in touch with the NuGet.Server on the website and fail miserably!
My bindings are 192.168.1.25 (yes, the server has a fixed IP address), port 80. The name of the site is AWENuGet and the desired url is www.awenuget.com.
To be sure, all of this works just fine if you take the same project as described above, assign a local port number (creating the project will do that anyway) and then simply running the application in Visual Studio works just fine.
But, when I took that self-same project and simply deployed it to iis, miserable failure.
I tried to open the host file (Windows\System 32\drivers\etc) and added the following:
192.168.1.25 www.awenuget.com
to said file and it still failed.
...and the answer, for me, was to take that same hosts file entry that I made on the server so that the server could see it and install it in my dev machine's hosts file and voila! NOW it works just fine.
I have switched recently to windows 10 and have no clue if this is linked but my IIS doesn't seem to work as it used to. I previously had a remote connection to one of my website but every time I click its name in IIS it returns me an error: "Remote connections are not supported".
A quick check tells me that IIS Manager for Remote Administration is installed in its version 1.2. I have no idea what is happening and it is really frustrating because I cannot add any new website either.
I had a similar problem. I solved it by downloading and running "IIS Manager for Remote Administration 1.2" and doing a "Repair" operation. This did three things: 1) reduced the startup time for the IIS Manager dramatically, 2) added a "Start Page" root node in my IIS Manager Connections pane (I know this used to be there but I had not noticed it was missing after my Windows 10 update), and 3) fixed my remote connection node.