Internet Services
|
|
Internet Information Services
Metabase access permissions
Products: Windows .NET Standard Server, Windows .NET Enterprise Server (32-bit version only), and Windows .NET Datacenter Server (32-bit version only).
IIS 6.0 now uses the Admin Base Objects
(ABO) OpenKey method for checking access permissions to the metabase. Permission to access a key in the metabase is based on the access control list (ACL) for the key. An error is displayed when you run code that uses the OpenKey method, if
the ACL for the key that the code uses prohibits access to the key in the metabase.
To work around this issue, add an access control entry (ACE) to the metabase for the user running code that uses the OpenKey method.
Alternatively, the user should log on to an account that has access permission for the metabase. For more information about how to add an ACE to the metabase, see "About the Metabase" in IIS online Help.
Renaming or
moving metabase files or the History folder is not supported
Products: Windows .NET Standard Server, Windows .NET Enterprise Server (32-bit version only), and Windows .NET Datacenter Server (32-bit version only)
Internet Information Services (IIS)
6.0 no longer supports renaming or moving metabase files (Metabase.xml and Mbschema.xml) or the metabase History folder. Renaming or moving them causes IIS to stop functioning correctly and might pose a security risk. If the files or folder
have been moved or renamed, you must return them to their original name and location.
To return metabase files and the History folder to their original state
Ensure that the metabase files are named Metabase.xml and Mbschema.xml and that the History folder is named History.
Ensure that all metabase files and the History folder are located in systemroot\System32\Inetsrv.
Ensure that the Local System account and Administrators group are assigned Full Control permission to the metabase files and History folder.
UDDI Services
Products: Windows .NET Standard Server, Windows .NET Enterprise Server (32-bit version only), and Windows .NET Datacenter Server (32-bit version only)
UDDI Services cannot create or write to a log
file in its default location. To work around this limitation, change the default location of the log file to one for which the service has write permissions, such as systemroot\Inetpub\Uddi.
To
change the location of the UDDI log file
Start Registry Editor (Regedit.exe), and then locate the following key:
HKLM\MICROSOFT\SOFTWARE\UDDI\DEBUG
Double-click LogFileName, and then type the new path and file name for the log file.
Click Save, and then close Registry Editor.
UDDI Services database components can only be installed on Microsoft Data Engine (MSDE) or SQL ServerTM 2000 Service Pack 2 or later. Earlier versions of SQL Server 2000 are not supported
and are not listed during installation.
Microsoft® Windows® .NET Enterprise Server Release Candidate (RC) Documentation
| 
SharePoint
au
Quotidien
avec
EROL
