|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 309675 - Last Review: December 30, 2002 - Revision: 2.1 IIS Lockdown Tool Affects SharePoint Portal ServerThis article was previously published under Q309675 One of the following symptoms may occur:
- You may not be able to install SharePoint Portal Server and
you may receive the following error message:
[2]
CVAIComponent, Error 0x80004005: VAIFy failed [0] CVAIComponent:Install,
Error setting up VAI. -or-
- You may not be able to access the workspace by using the
portal and you may receive the following error message when you access the
portal:
HTTP 404 - File Not Found
This issue can occur if the Internet Information Services
(IIS) Lockdown tool is blocking .asp pages. To resolve this issue, remove the IIS Lockdown Tool, and
then reinstall it with support for ASP pages turned on. To do this, follow
these steps:
- Run the IIS Lockdown tool Setup (IISLockd.exe) again, and
then click Undo.
- On the This Server Was Already Configured
screen, click Next.
- Click the Yes button on the dialog box that appears.
- Wait while IIS Lockdown Tool restores your previous
settings. This can take up to half an hour to complete.
- Click the Next button, and then click the Finish button to exit the Lockdown Tool setup.
- Re-run the Lockdown Tool setup program, and then click Next.
NOTE: When you re-run the setup program, make sure that you select the
View template settings option when you select a server
template. Or, you can select the Other template, which will allow you to select each setting
manually. - On the Script Maps screen, make sure that you clear the check box next to
Active Server Pages (.asp).
- Set the rest of the options based on your server
setup.
- Restart the server.
NOTE: This process will restore the backup of your metabase that was
made when you initially ran the IIS Lockdown Tool. If you have made any changes
to your IIS configuration since that time, such as adding sites or virtual
directories, these changes will be lost.
If you have made changes to your IIS configuration since
you first ran the IIS Lockdown Tool, you can use this workaround to restore
support for ASP pages without removing your configuration changes:
- Start Internet Services Manager.
- Expand the server object that is running SharePoint Portal
Server.
- Open the properties for the virtual directory of your
workspace.
- Click Configuration.
- Under Application Mappings, click the .asp extension, and then click Edit.
- In the Executable box, change the file name from 404.dll to
asp.dll.
- Click OK to close all of the properties dialog boxes.
- Stop and then restart the default Web site.
Repeat these steps for all of the workspaces. If you
installed URLScan when you installed the IIS Lockdown Tool, you must make a few
more changes as follows:
- Open the C:\Winnt\System32\Inetsrv\Urlscan\Urlscan.ini file
in Notepad.
- Under the Options section, note the value of the UseAllowExtensions option.
- If UseAllowExtensions is set to 0, find the DenyExtensions section farther down the file, and then comment out the .asp,
.cer, .cdx, and .asa lines by putting a semicolon (;) in front of
them.
- If UseAllowExtensions is set to 1, find the AllowExtensions section farther down the file, and then add .asp, .cer, .cdx, and
.asa, each on their own line.
- Save the Urlscan.ini file, and then restart IIS.
NOTE: If you set up SharePoint Portal Server for use on an extranet,
you must repeat this process for the secondary virtual directories that are
created.
APPLIES TO- Microsoft SharePoint Portal Server 2001
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
|
 |
 |
 |
 |
 |
 |
 |
| |