3
w3wp.exe-Fehler nach WSUS 3.0 Installation
Seit der Installation von WSUS 3.0 erscheint sporadisch folgende Fehlermeldung:
Quelle: Application Error
Kategorie. (100)
Ereigniskennung: (1004)
Fehler in Warteschlange: Fehlgeschlagene Anwendung w3wp.exe, Version 6.0.3790.3959, fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse 0x001f0017.
Der Server ist W2K3 Standard mit SP2 und es läuft IIS 6.0
Hat jemand eine Ahnung, wo das Problem liegen könnte???
Im Voraus vielen Dank
Lars
Quelle: Application Error
Kategorie. (100)
Ereigniskennung: (1004)
Fehler in Warteschlange: Fehlgeschlagene Anwendung w3wp.exe, Version 6.0.3790.3959, fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse 0x001f0017.
Der Server ist W2K3 Standard mit SP2 und es läuft IIS 6.0
Hat jemand eine Ahnung, wo das Problem liegen könnte???
Im Voraus vielen Dank
Lars
Share on Facebook
Share on Twitter
Share on Reddit
Share on LinkedinPlease also mark the comments that contributed to the solution of the article
Content-Key: 62495
Url: https://administrator.de/contentid/62495
Printed on: April 25, 2024 at 14:04 o'clock
3 Comments
Latest comment
Habe exakt das gleiche Problem.
Bin echt gespannt ob jemand eine Antwort parat hat.
Bin echt gespannt ob jemand eine Antwort parat hat.
Hallo,
ich habe auchg das selbe problem.
Habe bisher noch keine Antwort im Internet dazu finden können.
Wer kann helfen ?
ich habe auchg das selbe problem.
Habe bisher noch keine Antwort im Internet dazu finden können.
Wer kann helfen ?
Habe eine Lösung gefunden:
Method 3: Grant NETWORK SERVICE the necessary permissions to access the ASP.NET registry key
Note Use this method if you are running ASP.NET on a domain controller. An advantage of this is that you do not have to create an additional domain user account that you have to maintain or retain the password for. However, if you reinstall ASP.NET by using aspnet_regiis or the ASP.NET performance counters, the permissions on the registry key may be reset.
To grant NETWORK SERVICE the necessary permissions to access the ASP.NET registry key, follow these steps:1. Start Registry Editor, and then locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Names registry key.
2. Right-click Names, and then click Permissions.
3. Click Add, type NETWORK SERVICE, click Check Names, and then click OK.
4. In the Groups or User Names list, click Advanced.
5. In the Advanced Security Settings for Names dialog box, click the Permissions tab, click NETWORK SERVICE, and then click Edit.
6. In the Permission Entry for Names dialog box, make sure that NETWORK SERVICE appears in the Name box.
7. Click to select the following check boxes:• Query Value
• Set Value
• Create Subkey
• Enumerate Subkeys
• Notify
• Read Control
8. Click OK in all the dialog boxes, and then close Registry Editor.
Method 3: Grant NETWORK SERVICE the necessary permissions to access the ASP.NET registry key
Note Use this method if you are running ASP.NET on a domain controller. An advantage of this is that you do not have to create an additional domain user account that you have to maintain or retain the password for. However, if you reinstall ASP.NET by using aspnet_regiis or the ASP.NET performance counters, the permissions on the registry key may be reset.
To grant NETWORK SERVICE the necessary permissions to access the ASP.NET registry key, follow these steps:1. Start Registry Editor, and then locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Names registry key.
2. Right-click Names, and then click Permissions.
3. Click Add, type NETWORK SERVICE, click Check Names, and then click OK.
4. In the Groups or User Names list, click Advanced.
5. In the Advanced Security Settings for Names dialog box, click the Permissions tab, click NETWORK SERVICE, and then click Edit.
6. In the Permission Entry for Names dialog box, make sure that NETWORK SERVICE appears in the Name box.
7. Click to select the following check boxes:• Query Value
• Set Value
• Create Subkey
• Enumerate Subkeys
• Notify
• Read Control
8. Click OK in all the dialog boxes, and then close Registry Editor.
