Microsoft Knowledge Base Email Alertz

You may receive a The function requested is not supported error message when you try to connect to a Web site that is hosted on IIS

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 903071 - Last Review: December 3, 2007 - Revision: 3.3

You may receive a "The function requested is not supported" error message when you try to connect to a Web site that is hosted on IIS

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/ ) Description of the Microsoft Windows registry

On This Page

SYMPTOMS

When you try to connect to a Web site that is hosted on Microsoft Internet Information Services 6.0, Microsoft Internet Information Services 5.1, or Microsoft Internet Information Services 5.0, you may receive an error message that is similar to the following:
Error 500: The function requested is not supported.
Additionally, you may receive entries that are similar to the following in the Extended W3C log:
18:59:54 127.0.0.1 GET /localstart.asp 500 2148074242
Note The W3C Extended logs are located in the C:\WINDOWS\system32\Logfiles\.

CAUSE

This problem occurs if the following conditions are true:
  • The Web site is configured to use Windows Integrated authentication.
  • A strict security template has been applied to the Web server that prevents client computers that are running Microsoft Windows 2000 or earlier versions from authenticating as expected.

RESOLUTION

Determine whether a custom security template or a nondefault security template was applied to the Web server

To determine whether a custom security template or a nondefault security template was applied to the Web server, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  3. In the right-pane, verify that the Value data for the NTLMMinServerSec value is 0. If the value is not 0, security restrictions because of a nondefault template may be preventing client computers that are running Windows 2000 or earlier versions from connecting to the Web site.
  4. In the right-pane, verify that the Value data for the NTLMMinClientSec value is 0. If the value is not 0, security restrictions because of a nondefault template may be preventing client computers that are running Windows 2000 or earlier versions from connecting to the Web site.
  5. Quit Registry Editor.


If a custom security template or a nondefault security template was applied to the Web server, use one of the following methods to resolve this issue.

Method 1: Use the Secedit.exe utility to reset the default template

To use the Secedit.exe utility to reset the default template, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose, and then press Enter.

    Note You can ignore the warning that some files in the configuration are not found on the system.
  3. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  4. In the right-pane, verify that the Value data for the NTLMMinServerSec value is 0. If the value is not 0, security restrictions because of a nondefault template may be preventing client computers that are running Windows 2000 or earlier versions from connecting to the Web site.
  5. In the right-pane, verify that the Value data for the NTLMMinClientSec value is 0. If the value is not 0, security restrictions because of a nondefault template may be preventing client computers that are running Windows 2000 or earlier versions from connecting to the Web site.

Method 2: Use Registry Editor to reset the default security template

To change the registry to reset the default security template, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  3. In the right-pane, right-click NTLMMinServerSec, and then click Modify.
  4. In the Value data box, type 0 to replace the existing value, and then click OK.
  5. In the right-pane, right-click NTLMMinClientSec, and then click Modify.
  6. In the Value data box, type 0 to replace the existing value, and then click OK.
  7. Quit Registry Editor.

MORE INFORMATION

For more information about how to reset default security settings in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
313222  (http://kbalertz.com/Feedback.aspx?kbNumber=313222/ ) How to reset security settings back to the defaults

APPLIES TO
  • Microsoft Internet Information Services 6.0, when used with:
    • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Internet Information Services 5.1, when used with:
    • Microsoft Windows XP Professional
  • Microsoft Internet Information Services 5.0, when used with:
    • Microsoft Windows 2000 Server
    • Microsoft Windows 2000 Professional Edition
Keywords: 
kbtshoot kbprb KB903071
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Shafquat Hussain Mahar - shafkathussain NOSPAM-AT-NOSPAM gmail.com Report As Irrelevant  
Written: 12/11/2007 9:24 PM
The solution worked for me. but after sometime it reset the value again. so need to change the settings time to time resolve the issue. Please let me know if anyone have permanat solution.

Tony Report As Irrelevant  
Written: 5/13/2008 9:56 AM
Ask your administrator to look at group policy. That's probably why the settings change back. If you make the change, go to a command prompt, and type: gpupdate /force (or simply reboot) the registry keys should be reset back to the original value. My issue was due to a high-security template on servers in our DMZ.

sameh - sameh_abulfotooh NOSPAM-AT-NOSPAM hotmail.com Report As Irrelevant  
Written: 9/6/2008 12:09 AM
which security policy is the cause of this error? in my company, we have a custom security policy applied to all servers. But, I need to know specifically which policy is the cause of this error.