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:
CVAIComponent, Error 0x80004005: VAIFy failed
Error setting up VAI.
- 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
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
- 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
- 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
- Restart the server.
: 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
- Open the properties for the virtual directory of your
- 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
- 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.
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
- 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
- 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.
: If you set up SharePoint Portal Server for use on an extranet,
you must repeat this process for the secondary virtual directories that are
Article ID: 309675 - Last Review: October 24, 2013 - Revision: 2.1
- Microsoft SharePoint Portal Server 2001
|kbnosurvey kbarchive kberrmsg kbprb KB309675|