Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

NNTP Administration Tree Is Not Visible After You Upgrade to Windows 2003


View products that this article applies to.

Symptoms

The Network News Transfer Protocol (NNTP) administration tree may be hidden in the Microsoft Internet Information Services (IIS) Microsoft Management Console (MMC) snap-in.

↑ Back to the top


Cause

This behavior occurs if you upgrade your computer from Microsoft Windows NT 4 to Microsoft Windows 2000, and then you upgrade to Windows Server 2003. The NNTP administration tree does not appear in the MMC snap-in because the NNTPServiceVersion key in the metabase is set to 0 (zero).

↑ Back to the top


Resolution

To make the NNTP administration tree visible in the Internet Manager MMC, you must change the following metabase key in the MetaBase.xml file:
Key Name: NntpServiceVersion
Key Number: 45175
Existing Value: 0 New Value: 5
Key Location: LM\NNTPSVC

To change the value of the NntpServiceVersion Key, follow these steps:
1.Enable direct metabase edit:
a. Start the IIS Manager (Iis.msc).
b. Right-click the local computer, and then click Properties.
c. Click to select the Enable Direct Metabase Edit check box.
d. Click Apply, and then click OK.
2.Edit the metabase:
a. Open the MetaBase.xml file with a plain text editor, such as Notepad.

By default, the MetaBase.xml file is located in the Systemroot\System32\Inetsrv directory.
b. Locate the line NntpServiceVersion=, and then change the number to 5.
Note: All text in MetaBase.xml is case-sensitive.
c. Save the file.

↑ Back to the top


Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top


More information

You can also change the value change of the key programmatically in the MBSchema.xml file.

Note: You cannot edit the MBSchema.xml file directly by using the edit-while-running feature. To make changes to the metabase schema, you must make them programmatically. For more information about programmatically changing keys in the MBSchema.xml file, see the IIS Help Topic Code Examples to Configure Metabase Properties in the Help section Extending the Metabase Schema.

↑ Back to the top


References

For additional information about how to create a backup of the metabase, click the following article number to view the article in the Microsoft Knowledge Base:
324277 HOW TO: Create a Metabase Backup by Using IIS 6.0 in Windows Server 2003

↑ Back to the top


Keywords: KB816909, kbbug

↑ Back to the top

Article Info
Article ID : 816909
Revision : 6
Created on : 2/28/2007
Published on : 2/28/2007
Exists online : False
Views : 287