Cannot Successfully Access Personal Web Page (PWP) Services (236017)
The information in this article applies to:
- Microsoft Commercial Internet System 2.5
This article was previously published under Q236017 SYMPTOMS
When you attempt to use Personal Web Page (PWP) services for MCIS 2.5 with Personalization and Membership services, you cannot use PWP if the user objects are located in containers outside of the container configured as the Base DN (the Members container by default).
FTP publishing to PWP for members of communities works well and the member can authenticate as a domain or member. Users in multiple communities attempting to view the PWP cannot successfully access the PWP resources.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Commercial Internet System service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
File name Platform
-----------------------
Pwpfltr.dll x86
Pwpinstall.exe x86
Pwpfltr.dll Alpha
Pwpinstall.exe Alpha
WORKAROUND
Place all users in the Personalization and Membership container referred to for the Base DN.
If a number of communities are hosted, then (because each community requires a unique Base DN) each community must be accessed through a unique Web server. This requires one "server per community."
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
When the fix has been installed, user objects can be stored in subcontainers under ou=Members.
| Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB236017 |
|---|
|