U današnjem postu istražit ćemo uzrok, a zatim ponuditi rješenja za problem web - aplikacija koje vraćaju HTTP pogrešku 503^{(HTTP Error 503)} i WAS događaj 5189^{(WAS event 5189)} , nakon što nadogradite Windows 10.

Web - aplikacija HTTP pogreška 503^{(HTTP Error 503)} & WAS događaj 5189

Ako imate računalo sa sustavom Windows 10^{(Windows 10)} ili Windows Server 2016 s omogućenim Internet Information Services (IIS) i nadogradite na noviju verziju sustava Windows 10 ili Windows Server 2016 , tada se neke web aplikacije možda neće pokrenuti, ali umjesto toga, mogu prikazati sljedeću poruku o pogrešci:

Service Unavailable

HTTP Error 503. The service is unavailable.

Štoviše, ako vidite zapisnik događaja^{(Event Log)} , vidjet ćete sljedeću poruku:

WAS događaj 5189: Usluga aktivacije Windows procesa^{(Windows Process Activation Service)} nije uspjela generirati konfiguracijsku datoteku spremišta aplikacija za spremište aplikacija '< DefaultAppPool >'. Vrsta pogreške je '0'. Da biste riješili ovaj problem, provjerite je li datoteka applicationhost.config ispravna i ponovno izvršite posljednje promjene konfiguracije. Podatkovno polje sadrži broj pogreške.

Uzrok web - aplikacije HTTP pogreška 503^{(HTTP Error 503)} i WAS događaj 5189

Do ove pogreške može doći jer Windows Activation Service ( WAS ) stvara privremenu konfiguracijsku datoteku za svaki bazen IIS aplikacija u mapi ispod tijekom uobičajenog rada.

C:\inetpub\temp\appPools

Tijekom početne faze nadogradnje, Windows Update skenira postojeće mape i datoteke (izvan mape Windows ) i bilježi njihove staze koje će se vratiti nakon nadogradnje. Međutim, budući da su konfiguracijske datoteke privremene, brišu se kada se WAS zaustavi.

U sljedećoj fazi Windows Update , ove prethodno skenirane datoteke i mape kopiraju se na privremenu lokaciju za nadogradnju. Nakon nadogradnje sustava Windows, Windows Update^{(Windows Update)} stvara simboličku vezu na svaku mapu koja je kopirana na privremenu lokaciju za nadogradnju prije nego što pokuša vratiti te datoteke i mape na njihovo izvorno mjesto.

Međutim, budući da te privremene konfiguracijske datoteke više ne postoje, Windows Update ne uklanja simboličke veze.

Kada se WAS pokuša pokrenuti kao IIS radni proces, ne stvara privremenu mapu za pisanje konfiguracije zbog simboličkih veza. Stoga Http.Sys vraća HTTP 503 pogrešku.

Kako riješiti HTTP pogrešku 503 ^{(HTTP Error 503)}web - aplikacija i događaj WAS 5189

Kako bi riješio ovaj problem, Microsoft preporučuje ručno brisanje simboličkih veza (simboličke veze mogu se izbrisati isto kao i obične datoteke) koje stvara Windows Update . Da biste to učinili, slijedite ove korake.

Otvorite naredbeni redak u povišenom načinu rada^{(Open Command Prompt in elevated mode)} , kopirajte i zalijepite donju naredbu i pritisnite Enter :

net stop WAS /y
rmdir /s /q C:\inetpub\temp\appPools
net start W3SVC

Nadam se da će ovaj post pomoći!

Web apps HTTP Error 503 and WAS event 5189 on Windows 10

In today’s рost, we will explore the cause аnd then provide the solutions to the issue of Web applications returnіng HTTP Error 503 and WAS event 5189, after you upgrade Windows 10.

Web apps HTTP Error 503 & WAS event 5189

If you have a computer that is running Windows 10 or Windows Server 2016 that has Internet Information Services (IIS) enabled, and you upgrade to a newer version of Windows 10 or Windows Server 2016, then some web applications may not start, but instead, they may throw up the following error message:

Service Unavailable

HTTP Error 503. The service is unavailable.

Moreover, if you see the Event Log, you will see the following message:

WAS event 5189: The Windows Process Activation Service failed to generate an application pool config file for application pool ‘<DefaultAppPool>’. The error type is ‘0’. To resolve this issue, please ensure that the applicationhost.config file is correct and recommit the last configuration changes made. The data field contains the error number.

Cause of Web apps HTTP Error 503 and WAS event 5189

This error can occur because the Windows Activation Service (WAS) creates a temporary configuration file for each IIS application pool in the folder below during typical operation.

C:\inetpub\temp\appPools

During an initial upgrade phase, Windows Update scans the existing folders and files (outside the Windows folder) and records their paths to be restored after the upgrade. However, because the configuration files are temporary, they are deleted when WAS is stopped.

In the next phase of Windows Update, these previously scanned files and folders are copied to a temporary upgrade location. After Windows is upgraded, Windows Update creates a symbolic link to each folder that was copied to a temporary upgrade location before it tries to restore these files and folders to their original location.

However, because these temporary configuration files no longer exist, Windows Update does not remove the symbolic links.

When WAS tries to start as an IIS worker process, it does not create a temporary folder to write the configuration because of the symbolic links. Therefore, Http.Sys returns an HTTP 503 error.

How to resolve Web apps HTTP Error 503 and WAS event 5189

To resolve this problem, Microsoft recommends to manually delete the symbolic links (Symbolic links can be deleted the same as regular files) that are created by Windows Update. To do this, follow these steps.

Open Command Prompt in elevated mode, copy and paste the command below and hit Enter:

net stop WAS /y
rmdir /s /q C:\inetpub\temp\appPools
net start W3SVC

Hope this post helps!

Related posts

• HTTP pogreška 503, problem je nedostupna usluga

• Popravi pogrešku 503, usluga nedostupna - Steam

• Popravite pogrešku učitavanja aplikacije 5:0000065434 u sustavu Windows 10

• Popravite Bdeunlock.exe lošu sliku, pogrešku sustava ili pogreške nereagiranja

• Popravi pogrešku u trgovini Microsoft Store 0x87AF0001

• Popravite iTunes kod pogreške 5105, Vaš zahtjev se ne može obraditi

• Sigurnosni centar nije uspio potvrditi pozivatelja s pogreškom DC040780

• Popravite pogrešku Steam u nevaljanoj konfiguraciji skladišta na računalu sa sustavom Windows

• Popravite pogrešku skripte u sustavu Windows 11/10

• Popravi lošu sliku, status pogreške 0xc0000020 na Windows 11/10

• Mrežna pogreška: Nije moguće pristupiti mrežnom disku, pogreška 0x80004005

• Kako popraviti loš status pogreške slike 0xc000012f u sustavu Windows 11/10

• Popravi Runtime Error R6034 u sustavu Windows 11/10

• Instalirajte Realtek HD Audio Driver Greška, pogreška OxC0000374 na Windows 10

• Runtime Error 482 - Pogreška ispisa u sustavu Windows 10

• Popravite šifru pogreške sigurnosne kopije sustava Windows 0x8078012D, operacija sigurnosnog kopiranja nije uspjela

• InstallShield Kod pogreške 1722 tijekom instalacije MSI programa

• Kako popraviti Runtime Error 217 na Windows 11/10

• Došlo je do problema pri pokretanju ovog alata, kod pogreške 0x80080005 - 0x90018

• Origin DirectX Setup Error: Došlo je do interne pogreške