• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Warning: Metabase key 7041 is out of range.

B

barjolu

Guest
Hi,

I have a problem on a couple of our Windows Plesk nodes.

I get a lot of these warnings in the event log:

Event Type: Warning
Event Source: Active Server Pages
Event Category: None
Event ID: 9
Date: 12/15/2009
Time: 11:15:26 AM
User: N/A
Computer: WIN2
Description:
Warning: Metabase key 7041 is out of range. Using 1 as default..

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I also get this one, that is not so good since it disables the application pool:

Event Type: Error
Event Source: W3SVC-WP
Event Category: None
Event ID: 2269
Date: 12/14/2009
Time: 12:37:50 PM
User: N/A
Computer: WIN2
Description:
The worker process failed to initialize the http.sys communication or the w3svc communication layer and therefore could not be started. The data field contains the error number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: aa 05 07 80 ª..€

Anyone know how to fix this? I have checked that the "Bypass Traverse Checking user right" is correct so that is not the problem.

Best regards
Johannes
 
It is IIS related Problems but not Plesk. Regarding first issue look at this solution. Maybe it will help.
For your second issue you can read MS KB article.
 
Hi, thanks for the answer.

I've tried the first solution, setting the metabase key, but it doesn't help.

The other solution, as I mentioned in my first post, is also not the case, since both the everyone and users group already is enabled in "Bypass traverse checking".

Since I have this problem on two of my machines, both running plesk 9.2.1, i thought this could have something to do with Plesk.
 
Back
Top