RapPort Administration and Maintenance | Microsoft SharePoint(TM) Portal Server 2001 Resource Kit (Examples & Explanations Series)

This section describes monitoring methods to ensure proper operation of RapPort. It also provides possible solutions to issues you may encounter.

RapPort uses SharePoint Portal Server as the underlying platform. Therefore, it assumes that an organization deploying and operating RapPort operates and maintains this environment as outlined in SharePoint Portal Server Administrator's Help online. This includes backup, monitoring and performance optimization. RapPort does not require any special backup or optimization of the SharePoint Portal Server environment.

This section focuses on monitoring and maintaining the portal provisioning process by addressing the following topics:

Monitoring Initial Operations. This section reviews possible failures caused by improper installation or configuration.
Monitoring Daily Operations. This section reviews daily tasks and monitoring methods to ensure RapPort operates successfully.
Diagnosing Request Problems. This section describes the failures that may occur during the provisioning process, along with detailed troubleshooting and suggested corrective actions.
Resolving Problems. This section provides detailed procedures for restoring the RapPort application to operation after a provisioning failure.

Monitoring Initial Operations

If the first request submitted to RapPort fails, it is likely the result of an error during installation. The following steps provide a list of items to check to confirm proper installation and setup. In addition, these steps can also assist in diagnosing problems in the event of recent modifications to the RapPort server configuration.

To verify RapPort settings:

Check the following items to confirm proper installation and setup. Please refer to the installation instructions for specific settings.

Confirm that the same domain account is a member of the local Administrator's group for all servers in this deployment. This account should be the same on the RapPort server, the template server, and any destination servers.
Confirm the existence of the RapPort virtual directory on the RapPort server and each destination server.
Check that the proxy configuration on the RapPort server and each destination server is in accordance with the installation instructions for RapPort.
Confirm that all folders are named properly.
Ensure that the RapPort folder on the RapPort server and each destination server are not set to Read only.
The Windows 2000 Everyone group should be granted Full Control NTFS permissions to the RapPort folder.
Ensure that only one instance of Autosetup.exe occurs in Task Manager on the RapPort server.
Ensure that you provided the common domain account during installation for Autosetup.exe to use on the RapPort server.
This domain account must be a member of the Local Administrator's group on each server in this deployment.
Confirm that you registered the COM+ package on the RapPort and destination servers using the appropriate domain account.
Confirm that you assigned the appropriate domain account to the role of coordinator for all workspaces on the template server.
In Internet Service Manager, ensure that the following folder specifies "Script Only" on the destination server:
Default Web Site/ Share Point Portal Server/Applications
Ensure that you configured Cscript as the default Windows scripting host on the RapPort server and each destination server.
Confirm the DLL registration on the RapPort server and each destination server.

For more information about performing these tasks, see RapPort Installations.

Monitoring Daily Operations

The RapPort application provides information whenever it receives a request or the provisioning status of a server changes. RapPort logs both successes and failures. RapPort records this information in several places:

Mails. All these events generate mail to the Support e-mail, RapPort Support. This mail includes the details of the activity.

Windows 2000 Event Viewer. These events also generate entries in the RapPort application log of each server.

RapPort application log. The RapPort application log of the RapPort server provides an overview of the status of each execution of AutoSetup.

You can view the log from the following location on the RapPort server.

Drive:\RapPort\Autosetup\Logs\ApplicationLog.txt

Request Log. RapPort creates a request log on the RapPort server and each destination server for each portal request. RapPort names this file request virtual_server_name.txt. This log provides a detailed status of the portal provisioning process. You can view the request log at the following locations:
Drive:\RapPort\Autosetup\Logs\virtual_server_name.txt on the RapPort server

Drive:\\RapPort\Logs\virtual_server_name.txt on the destination server.
Request File. RapPort creates a request file containing the user input when a user requests a new portal. The RapPort server modifies this request file with a code indicating the status of the portal provisioning process as the request goes through various stages during provisioning. You can view the file at the following location on the RapPort server:
Drive:\RapPort\RapPortWeb\Data\UserRequests\userdata_virtual_server_name.xml

After RapPort successfully completes a request, you can view the file at the following location on the RapPort server:

Drive:\RapPort\RapPortWeb\Data\History\userdata_virtual_server_name.xml

The following table describes the status codes stored in the request file:

Status codes in the request file


Code	Definition
0	Request started, not yet completed
1	Request completed
2	Provisioning Process has started
3	Provisioning Process has failed
4	Provisioning Process has succeeded

Although you can find status information in each of these places, it is recommended that you use e-mail messages sent to the RapPort Support as your primary method of monitoring and troubleshooting processes. This section uses e-mail notification as the primary method of monitoring activity.

Status Messages

Each time a user requests a new portal, you should expect RapPort Support to receive three messages.

Request Acknowledgement Notification. The RapPort server sends an e-mail acknowledging the request for a new portal to the person requesting who submitted the request. The RapPort server sends a copy of this e-mail to RapPort Support.
Workspace Creation Notification. RapPort server sends an e-mail acknowledging that it successfully created the workspace to the person who submitted the request. The RapPort server sends a copy of this e-mail to RapPort Support. If the workspace creation fails, the RapPort server notifies RapPort Support so the problem can be resolved and the process completed.
Wins/DNS entry requisition. After successful creating the virtual server, the RapPort server sends an e-mail message to the appropriate account, requesting a virtual server entry in the WINS/DNS table. The RapPort server sends a copy of this e-mail to RapPort Support.

During setup, you must specify an e-mail account to receive WINS/DNS entry requests. This account can be an individual user or group account.

Unavailable Destination Servers

RapPort makes the destination server(s) status as Unavailable under following conditions:

When a destination server has reached the specified number of workspaces as defined by the capacity in the ServerConfig.xml, it returns a status of "unavailable."
If the destination server encounters an failure during workspace creation, it returns a status of "unavailable" to prevent attempting to create additional workspaces on that server.

If the RapPort server marks a destination server as unavailable, then no additional workspaces can be created on it until the status changes to "available."

By marking the server "unavailable," RapPort forces the next portal request to skip that server in the selection process, but continues processing portal requests. RapPort sends an e-mail notifying RapPort Support when a server returns a "server unavailable" status. The message includes information explaining the reason for the status. For information about how to reset the status of a server, see Resolving Problems.

Daily Checks

The RapPort server sends e-mail to the support team, RapPort Support, at the completion of major tasks. The support team should use these e-mail notifications to conduct the daily checks to verify the system is operating properly or as a starting point to diagnose problem section. The following section summarizes possible failures and potential resolutions.

There are effectively four possible states the administrator may encounter in provision-ing a site:

Confirmation Mail Received, Provisioning Successful
Confirmation Mail Received, Provisioning Failed
No Confirmation Mail Received
Server Unavailable Mail Received

In each of these cases, action may be required. The following sections provide a brief overview of each situation followed by detailed troubleshooting guidance for each situation.

Confirmation Mail Received, Provisioning Successful

If RapPort Support receives all three e-mail messages, including the final confirmation mail with a successful status, you can generally assume that RapPort is operating correctly. However, there are some cases where RapPort may have encountered some problems in the process, but they were not considered significant enough to warrant a failure message.

As an example, RapPort may successfully replicate a workspace template but fail to copy a particular document. In this case, the portal provisioning process completed successfully and RapPort Support receives all three e-mail messages but the final workspace may lack some elements. To resolve this issue, you can manually copy the missing information or delete the workspace and restart the portal provisioning process entirely, depending on the specific instance where the failure occurred.

To determine if RapPort failed to copy or create any items, you must examine the RapPort request logs. For detailed instruction on how to check these logs and resolve any issues, see Verify Successful Workspace Creation under Diagnosing Request Problems.

Confirmation Mail Received, Provisioning Failed

In cases of outright failure, the e-mail message indicates the cause of the failure. For more information about reviewing any associated logs and resolving any issues see Confirm Failed Workspace Provisioning under Diagnosing Request Problems.

No Confirmation Mail Received

If no confirmation mails are received, then you must use the application log to determine status and determine corrective action. For more information about checking this log and resolving any issues see Review Application Log under Diagnosing Request Problems.

Server Unavailable Mail Received

RapPort sends a message notifying RapPort Support when a server is no longer available to accept requests.

If you receive this mail with a corresponding Workspace Failure e-mail message, see Confirm Failed Workspace Provisioning under Diagnosing Request Problems. Once completed then, you can reset the server status. For information about resetting the server status, see Reset Destination Server Status under Resolving Problems.

If you receive this mail without a corresponding Workspace Failure e-mail message, see Address Maximum Workspace Capacity under Resolving Problems.

Diagnosing Request Problems

This section describes how to diagnose and resolve problems encountered in the provisioning process. It is recommended that you view this section in the context of daily monitoring tasks.

Verify Successful Workspace Creation

To verify that RapPort successfully created a workspace, you must review the request logs. These logs exist on both the RapPort server and the destination server. Scan the request logs for any of the errors or keywords listed below and take the suggested corrective actions.

RapPort names this file request virtual_server_name.txt. You can view the request log at the following locations:

Drive:\RapPort\Autosetup\Logs\virtual_server_name.txt on the RapPort server

Drive:\\RapPort\Logs\virtual_server_name.txt on the destination server.

To determine the destination server, open the userdata_virtual_server_name.xml file in the history folder on the RapPort server and look for the name in the <server> tag.

Keywords: Error, Failed, Permission Denied, 404, 409, 403, 401, unauthorized, timed out, access denied, unable Unauthorized, Timed Out, Access Denied, Unable

Location._virtual_server_name.txt on the RapPort server, anywhere in section 4 through 14.

If the item on which the failure occurred is a document, URL link or a shortcut:

Copy the item manually from the workspace template into the new workspace.
Manually update all the properties associated with the item.
If the item on which the failure occurred is not a document:
Create the item manually in the new workspace.
Establish any required relationships or associations. For example, if RapPort fails to copy a document profile, then you must create it manually and update the metadata of all documents that are associated with this profile.

Error: Warning!! Unexpected Content Class found

Location._virtual_server_name.txt on the RapPort server, section 12.

This indicates that RapPort failed to copy a document or set of documents. To resolve this, perform the following steps:

Locate the name of the document in the <source href> portion of the error message in the request log.
Copy this document manually from the workspace template to the new workspace.
Manually update all the properties associated with the item.

Error: Unable to Create Default.asp file for Redirection.

Location._virtual_server_name.txt on the destination server.

RapPort did not create the page, default.asp, used to redirect the virtual server. You must create it manually by performing the following steps:

Create a folder with the same name as that of the request URL under <Drive:>\RapPort\VirtualServers folder on the destination server and create a new file, called default.asp, inside it.
Edit this file and put following content in it:
```
 <% @Language = "VBScript" %> <% Response.Redirect "/workspace_name"%> 
```
where workspace_name is the name of the workspace.
Save the file.

Error: Unable to Enable Discussions On Virtual Server

Location._virtual_server_name.txt on the destination server.

If you find this message in the request log, then you must manually enable discussions for that virtual server. For more information about how to enable discussions, see Chapter 12, Deploying SharePoint Portal Server in an Extranet Environment.

Confirm Failed Workspace Provisioning

When RapPort fails to provision a workspace, RapPort Support receives an e-mail message that indicates the request failed and provides a description of the failure. This sections lists these error messages, the appropriate log and location within the log where you can find additional information. It also provides procedures for diagnosing and resolving the underlying problem.

Error: Creation Of Template Instantiation Component(Tempinst.Dll) Failed

Location._virtual_server_name.txt on the RapPort server.

Verify that the RapPort COM+ application is properly installed on the RapPort server. If this is not properly installed, then remove and reinstall the COM+ application. If you still receive this error message, remove and reinstall the RapPort server. For more information about removing and reinstalling RapPort, see Removing RapPort.

To verify the RapPort COM+ application:

On the RapPort server, using COM Application Explorer, verify that the RapPort COM+ application package is running under the correct user name and password. To do this, see To create a new COM+ application:.
If it is not, edit the COM+ application package properties to enter the appropriate user name and password.
Reprocess the request. See If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation.

If the preceding procedure does not solve the problem, then remove and reinstall the COM+ DLLs by executing the following procedures:

To remove and reinstall the COM+ DLLs:

Perform the following procedures:
- "To Delete the RapPort DLLs" under "Removing RapPort."
- "To Create a New COM+ Application" under "Install the RapPort Server."
- "To Add Components to the New (RapPort) COM+ Application" under "Install the RapPort Server."
Restart the computer.
Reprocess the request as described in "If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation."

If the previous step does not solve the problem, then remove and reinstall the RapPort server according to the following procedures:

To remove and reinstall the RapPort server:

Remove the RapPort server according to the procedure "Removing RapPort."
Reinstall the RapPort server according to the procedure "Installing the RapPort Server."
Reprocess the request as described in "If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation."

Error: Server Has Been Marked Unavailable As Capacity Is Exhausted

Error: Workspace Capacity On This Server Has Been Reached

Location._virtual_server_name.txt on the RapPort server, section 3.

This message indicates that the number of workspaces on this destination server has reached the specified capacity in ServerConfig.xml. To resolve this problem, see Address Maximum Workspace Capacity. Upon resolving the capacity problem, reset the server status to available. For more information, see Reset Destination Server Status.

Error: No Server Is Available

Location._ApplicationLog.txt on the RapPort server, section 3.

Reprocess this request once you add additional server capacity. To reprocess the request, see If The Request Fails When No Destination Server Is Available For Request Processing:.

Error: Rapport Virtual Directory Is Not Hosted On The Destination Server Or The Required Page(Createworkspace.Asp) Is Not Found In The Rapport Virtual Directory

Error: Generation Of Copy Script For Application Folder(S) Copy Failed

Location._ApplicationLog.txt on the RapPort server, section 3.

Perform the following steps on the destination server:

Verify that IIS is running on the destination server. If not, start IIS.
Verify that the RapPort virtual directory is properly configured on the destination server by using the Internet Services Manager. For more information, see To create a new virtual directory in the destination server.
Verify that the CreateWorkspace.asp page is present. For more information, see To copy destination server files:.
Check network connectivity by pinging the destination server from the RapPort server.
Set the server as available. For more information, see Reset Destination Server Status.
Reprocess the request by completing the steps described in "If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable."

Error: Copy ScriptApplication FolderRapPort DLL(RemoteWS.dll) is not Registered on the Destination ServerScript Failed

Location._Failure e-mail messages.

Perform the following procedures on the destination server:

Check the COM+ application settings, then try removing and reinstalling the COM+ packages. Finally, remove and reinstall the destination server.
Using the COM Application Explorer, check that the RapPort COM+ application package is running under the correct user name and password. For more information, see To create a new COM+ application:.
If the application package is not running under the correct user name and password, edit the COM+ application package properties to enter the appropriate user name and password.
Set the server as available, see Reset Destination Server Status.
Reprocess the request. See If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:.
If the previous step does not solve the problem, remove and reinstall the DLLs on the destination server, by performing the following procedures:
- "To Delete the RapPort COM+ Application" under "Removing the Destination Server."
- "To Unregister the RapPort DLLs" under "Removing the Destination Server."
- "To Register the RapPort DLLs" under "Removing the Destination Server."
- "To Create a new COM+ Application" under "Removing the Destination Server."
Restart the destination server.
Set the server as available by referring to "Resolving Problems: Reset Destination Server Status."
Reprocess the request by completing the steps described in "If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable."
If the previous step does not solve the problem, then remove and reinstall the destination server according to the following procedures:
"Remove the Destination Server"

"Install the Destination Server"
Set the server as available, see Reset Destination Server Status.
Reprocess the request, see If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:.

Error: Copy ScriptSharePoint Portal Server Not Installed on the Destination ServerCategory Failed

Location._e-mail messages only

Perform the following procedures on the destination server:

Check that SharePoint Portal Server is installed on the destination server, and the following registry key exists in the registry of the destination server: "HKEY_LOCAL_COMPUTER\SOFTWARE\Microsoft\SharePoint Portal Server\InstallPath". If not, then remove SharePoint Portal Server and reinstall SharePoint Portal Server.
Set the server as available. See Reset Destination Server Status.
Reprocess the request. See If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:.

Error: Workspace Creation Failed

Location._virtual_server_name.txt on the RapPort server, section 1.2.

Perform the following steps on the destination server:

Check whether the following services are running on the destination server:
- W3SVC
- Msdmserv
- MSExchangeIS
- MSSearch
If one of the services is not running, start the appropriate service.
Check whether SharePoint Portal Server on the destination server is accessible by using SharePoint Portal Server Administration. If it is not accessible, see SharePoint Portal Server Administrator's Help online.
Set the server as available, see Reset Destination Server Status.
Reprocess the request, see If The Request Has Failed During Workspace Creation:.

Error: Assignment of Common Administrator as Workspace Coordinator Failed on the Server

Error: Execution Permission Setting on Application Folder Failed on the Server

Location._virtual_server_name.txt on the RapPort server, section 1.2

Perform the following steps on the destination server:

Check whether SharePoint Portal Server on the destination server is accessible by using SharePoint Portal Server Administration. If it is not accessible, see SharePoint Portal Server Administrator's Help.
Set the server as available, see Reset Destination Server Status.
Reprocess the request, see If The Request Has Failed After Workspace Has Been Created But Before Copy Is Instantiated:.

Error: Virtual Server Creation Failed

Location._virtual_server_name.txt on the RapPort server, section 17.2.

Perform the following steps:

Check whether IIS is running on the destination server. If it is not running, start IIS.
Check that the RapPort virtual directory is properly configured on the destination server by using the Internet Services Manager. See To create a new virtual directory in the default Web site:.
Check that the CreateVirtualServer.asp page is present. See To copy destination server files:.
Check network connectivity by pinging the destination server from the RapPort server.
Reprocess the request. See If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation.

Error: Error Loading User Request Xml on Destination Server

Location._E-mail messages only

Perform the following steps.

Set the server as available. See Reset Destination Server Status.
Reprocess the request. See If The Request Fails When No Destination Server Is Available For Request Processing:.

Error: Error in the Response from Destination Server

Location._E-mail messages only

Perform the following steps.

Check if IIS is running on destination server. If not start IIS.
Check whether the following services are running on the destination server:
- W3SVC
- Msdmserv
- MSExchangeIS
- MSSearch
If one of the services is not running, start the appropriate service.
Check whether SharePoint Portal Server on the destination server is accessible by using SharePoint Portal Server Administration. If it is not accessible, see SharePoint Portal Server Administrator's Help online.
Verify network connectivity by pinging the destination server from the RapPort server, by using the server name.
Set the server as available. See Reset Destination Server Status.
Reprocess the request. See If The Request Has Failed During Workspace Creation:.

Error: Copy ScriptFolderWorkspace Creation Request to Destination Server Timed OutFailed

Location._virtual_server_name.txt on the RapPort server, section 1.2.

Perform the following steps.

Change the ReceiveTime value in the Constants.xml file by increasing it to an appropriate value. Try various configurations to determine the optimal setting. To change the value, see To modify time-out settings:.
Change the ASP script time-out settings on the RapPort virtual directory on the destination server to a number greater than or equal to the ReceiveTime set in the step above. To change this value, see To modify ASP Script time-out:.
Set the server as available. See Reset Destination Server Status.
Reprocess the request as described under "If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable."

Error: Server Name Or The IP Address Could Not Be Resolved

Error: Server Connection Could Not Be Established

Location._virtual_server_name.txt on the RapPort server, section 1.2 or 17.2

Perform the following steps.

Verify network connectivity by pinging the destination server from the RapPort server, by using the server name.
Verify the network connectivity and registry entries by pinging the destination server from the RapPort server by using the IP address set in the destination server registry key:
HKLM\software\Microsoft\RapPort
Check whether IIS is running on the destination server. Restart IIS if it is not running.
Set the server as available. See Reset Destination Server Status.
Reprocess the request as described under "If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable."

Error: Server Name Or IP Address Could Not Be Resolved While Creating Virtual Server

Error: Failed To Get IP Address From

Location._virtual_server_name.txt on the RapPort server , section 17.2

Perform the following steps.

Verify network connectivity by pinging the destination server from the RapPort server, by using the server name.
Verify the network connectivity and registry entries by pinging the destination server from the RapPort server by using the IP address set in the destination server registry key:
HKLM\software\Microsoft\RapPort
Check whether IIS is running on the destination server. Restart IIS if it is not running.
Reprocess the request, see If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation.

Error: IIS Reset Failed On

Error: Reset IIS Failed

Location._ApplicationLog.txt on the RapPort server, section 4.

Perform the following steps on the destination server on which the request is being processed.

Wait for 5 minutes.
Restart IIS on the destination server.
Open todaysServer.xml on the RapPort server in Notepad.
Delete the XML node for this destination server from this todaysServer.xml.
Save the file.

Error: Workspace Coordinator(S) Role Assignment Failed

Error: Workspace Author(S) Role Assignment Failed

Location._virtual_server_name.txt on the RapPort server, section 15.

Perform the following steps.

Check whether SharePoint Portal Server on the destination server is accessible by using the SharePoint Portal Server Administration. If not it is not accessible, see SharePoint Portal Server Administrator's Help online.
Reprocess the request. See If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation.

Error: Rapport Registry Key Path Not Found

Location._ApplicationLog.txt on the RapPort server, section 4.

From the RapPort server, on the Start Menu, click Run.
Type regedit and then click OK.
In Registry Editor, navigate to the node:
Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
Expand HKLM\Software\Microsoft key and check whether the RapPort key exists under it. If it exists, delete and re-create this key. See To import the RapPort server registry entries:.
Reprocess the request. See If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:.

Error: Error While Saving File

Location._virtual_server_name.txt on the RapPort server or ApplicationLog.txt on the RapPort server

This message indicates that RapPort cannot save one of the XML files typically because the XML files were left as read-only during installation. Perform the following steps.

Check that file permissions on RapPort server are not read-only, see To remove the read-only attributes for the files: under Install the RapPort Server.
Check that file permissions on the destination server are not read-only, see To remove the read-only attributes for the files: under Install the Destination Server.
Reprocess the request, see Restart a Portal Provisioning Request.

Error: Folder Not Found

Error: Error Occurred In Opening Folder

Error: File Not Found

Location._virtual_server_name.txt on the RapPort server or ApplicationLog.txt on the RapPort server

One of the folders required by AutoSetup is missing. You must remove and reinstall the RapPort server. Perform the following procedures:

"Removing RapPort server"
"Install the RapPort server"

Open completion of the procedures listed above, resubmit the site request.

Error: Invalid Common Administrator Account

Location._ApplicationLog.txt on the RapPort server, section 1.

Perform the following steps.

Check whether the following registry key exists on the RapPort server:
HKLM\software\Microsoft\RapPort\CommonAdmin

For more information, see To verify that registry entries have been successfully imported:.

Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
Check whether the user name value in this key is still a valid Windows NT domain account.
Reschedule Autosetup.exe to run again.

Error: Error In Parsing Xml

Error: Invalid ServerConfig.xml File

Location._virtual_server_name.txt on the RapPort server or ApplicationLog.txt on the RapPort server, sections 1.7-1.9, 3.

This error may occur in the event that a configuration file was recently modified and not edited correctly. The error message indicates the name of the XML file that is causing the problem. Perform the following steps.

Check the file by opening it in Internet Explorer. Internet Explorer uses its built-in XML parser to analyze XML content and report errors.
Correct any problems with the XML file. For more information, see Customizing Configuration Settings.
Check the XML file by opening it in Internet Explorer again.
Reschedule Autosetup.exe to run again.

Error: Error Occurred In Sending Rapport E-Mail

Location._ApplicationLog.txt on the RapPort server, section 3.

Confirm that the SMTP information and settings in mails.xml are correct. Perform the following steps:

Open the file, mails.xml, in Internet Explorer. Internet Explorer uses its built-in XML parser to analyze XML content and report errors.
Correct any problems with file, mails.xml. For more information, see To edit Mails.xml:.
Check that the SMTP server name specified is correct.
Check that the e-mail user names are valid user names.
Check that the SMTP server is properly configured. See To configure the default SMTP virtual server:.
Check that the SMTP server is actually running by checking with the local operations team.
Check the request status. View section 3 of the application log to determine the request status and pertinent error message.
If the request was successful, send the appropriate confirmation mail to the person who requested the site and RapPort Support. Send the WINS/DNS entry request to the appropriate e-mail account.

If the request failed, send the appropriate e-mail to RapPort Support indicating the failure and the error message recorded in the application log. Treat this as a standard failure mail, and troubleshoot accordingly.

Error: Error Occurred In Initializing Rapport E-Mail Service

Location._ApplicationLog.txt on the RapPort server, section 3.

Confirm that the SMTP information and settings in mails.xml are correct. Perform the following steps:

Open the file, mails.xml, in Internet Explorer. Internet Explorer uses its built-in XML parser to analyze XML content and report errors.
Correct any problems with file, mails.xml. For more information, see To edit Mails.xml:.
Check that the SMTP server name specified is correct.
Check that the e-mail user names are valid user names.
Check that the SMTP server is properly configured, see To configure the default SMTP virtual server:.
Check that the SMTP server is actually running by checking with local operations team.
Reschedule Autosetup.exe to run again.

Error: Dedicated Server Unavailable

Location._ApplicationLog.txt on the RapPort server, section 3.

This message indicates that the dedicated server against which the request was being processed has been marked as unavailable by the RapPort application. First you must determine the reason for the failure. The reason determines the corrective action you must perform.

To determine the cause of a status "Unavailable":

On the RapPort server, open ServerConfig.xml by using Internet Explorer.
Locate the <entry></entry> node for the affected destination server.
The text in the <comment></comment> provides the reason for the failure. Locate this cause in the following sections and follow the correctives steps provided.

Reason: Rapport Virtual Directory Is Not Hosted On The Destination Server Or The Required Page(Createworkspace.Asp) Is Not Found In The Rapport Virtual Directory

Check whether IIS is running on the destination server. If it is not running, start IIS.
Using the Internet Services Manager, check that the RapPort virtual directory is properly configured on the destination server. For more information, see "To create a virtual directory for the destination sever."
Check that the CreateWorkspace.asp page is present, see To copy destination server files:.
Check network connectivity by pinging the destination server from the RapPort server.
Set the server as available, see Reset Destination Server Status.
Reprocess the request, see If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:.

Reason: Workspace Creation Failed

Check whether the following services are running on the destination server:
- W3SVC
- Msdmserv
- MSExchangeIS
- MSSearch
If one of the services is not running, start the appropriate service.
Check whether SharePoint Portal Server on the destination server is accessible by using the SharePoint Portal Server Administration. If it is not accessible, see SharePoint Portal Server Administrator's Help online.
Check that remoteWS.DLL is properly registered on the destination server. For more information, see To register the RapPort DLLs:.
Check that Createworkspace.asp exists on the destination server. See To copy destination server files:.
Set the server as available. See Reset Destination Server Status.
Reprocess the request. See Restart a Portal Provisioning Request.

Reason: Binding To Folder Using SharePoint Portal Server Software Development Kit (SDK) Failed

Check whether the following services are running on the destination server:
- W3SVC
- Msdmserv
- MSExchangeIS
- MSSearch
If one of the services is not running, start the appropriate service.
Check whether SharePoint Portal Server on the destination server is accessible by using the SharePoint Portal Server ADMINISTRATION. If it is not accessible, follow the appropriate troubleshooting guidance in SharePoint Portal Server Administrator's Help online.
Set the server as available, see Reset Destination Server Status.
Reprocess the request, see Restart a Portal Provisioning Request.

Reason: Attempt To Restart SharePoint Portal Server And Other Services Failed

Perform the following steps on the destination server on which the request is being processed:

Restart services manually on the destination server. To do this run the following commands on the destination server in the order given below from a Command Prompt:
```
 net stop w3svc net stop msdmserv net stop msexchangeIS net stop mssearch net start mssearch net start msexchangeIS net start msdmserv net start w3svc 
```
Check the Windows NT event viewer application log to identify the possible causes of the service(s) failing to start.
Check whether SharePoint Portal Server on the destination server is accessible by using SharePoint Portal Server Administration. If it is not accessible, see SharePoint Portal Server Administrator's Help.
Set the server as available, see Reset Destination Server Status.
Reprocess the request as specified under "If The Request Has Failed After Workspace Has Been Created But Before Copy Is Instantiated."

Reason: Rapport DLL(Remotews.Dll) Is Not Registered On The Destination Server

Perform the following steps on the destination server on which the request is being processed:

Check that the RapPort COM+ application package is running under the correct user name and password by using the COM Application Explorer as specified under "To Create a New COM+ Application."
If it is not, edit the COM+ application package properties to enter the appropriate user name and password.
Set the server as available as specified under "Reset Destination Server Status"
Reprocess the request as specified under "If The Request Fails When Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable."
If the previous steps do not solve the problem, then remove and reinstall the DLLs on the destination server, by executing the following procedures:
- "To Delete the RapPort COM+ Application"
- "To Unregister the RapPort DLLs"
- "To Register the RapPort DLLs"
- "To Create a new COM+ Application"
Restart the destination server computer.
Set the server as available as specified under "Reset Destination Server Status"
Reprocess the request as specified under "Restart a Portal Provisioning Request: If the request fails when destination server on which the request is being processed gets marked as unavailable."
If the previous steps do not solve the problem, then uninstall and reinstall the destination server:
- "Remove the Destination Server"
- "Install the Destination Server"
Set the server as available as specified under "Reset Destination Server Status"
Reprocess the request as specified under "If The Request Fails When Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable."

Reason: SharePoint Portal Server Not Installed On The Destination Server

Perform the following steps on the destination server on which the request is being processed:

Ensure that SharePoint Portal Server is installed on the destination server, and that the following registry key exists in the registry of the destination server:
HKEY_LOCAL_COMPUTER\SOFTWARE\Microsoft\SharePoint Portal Server\InstallPath
If it is not installed, remove SharePoint Portal Server and reinstall SharePoint Portal Server.
Set the server as available. For more information, see Reset Destination Server Status.
Reprocess the request. For more information, see If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:.

Reason: Error Loading User Request Xml On Destination Server

Open the userdata_virtual_server_name.xml file by opening it in Internet Explorer. Internet Explorer uses its built-in XML parser to analyze XML content and report errors.
Set the server as available, see Reset Destination Server Status.
Reprocess the request, see Restart a Portal Provisioning Request.

Reason: Workspace Creation Request To Destination Server Timed Out

Perform the following steps on the destination server:

Change the RecieveTime value in the Constants.xml file by increasing it to an appropriate value. Try various configurations to determine the optimal setting. To change the value, see To modify time-out settings:.
Change the ASP script time-out settings on the RapPort virtual directory on the destination server to a number greater than or equal to the RecieveTime set in the step above. To change this value, see To modify ASP Script time-out:.
Set the server as available. See Reset Destination Server Status.
Reprocess the request as described under If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:.

Reason: Server Name Or The IP Address Could Not Be Resolved

Reason: Server Connection Could Not Be Established

Perform the following steps on the destination server:

Verify network connectivity by pinging the destination server from the RapPort server, by using the name of the server.
Verify the network connectivity and registry entries by pinging the destination server from the RapPort server by using the IP address set in the destination server registry key HKLM\software\Microsoft\RapPort.
Check whether IIS is running on the destination server. If it is not running, restart IIS.
Set the server as available. See Reset Destination Server Status.
Reprocess the request as specified under "If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable."

Reason: Assignment Of Common Administrator As Workspace Coordinator Failed On The Server

Reason: Execution Permission Setting On Application Folder Failed On The Server

Perform the following steps on the destination server on which the request is being processed:

Check whether IIS is running on the destination server. If it is not running, restart IIS.
Check whether SharePoint Portal Server on the destination server is accessible by using the SharePoint Portal Server Administration. If it is not accessible, see SharePoint Portal Server Administrator's Help.
Set the server as available as specified under "Reset Destination Server Status."
Reprocess the request as specified under "If The Request Has Failed After Workspace Has Been Created But Before Copy Is Instantiated."

All Other Error Messages

Reprocess the request by completing the steps described in the following section: "If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation."

Review Application Log

If you suspect that RapPort has completed a request but did not send an e-mail confirming the request, either success or failure, then you can review the application log on the RapPort server to confirm the status of the request. The application log shows the status of any processed requests and indicates any failures that may have occurred.

The following procedure describes how to check the application log for errors. If you do not find an error and the site request was successful then you must manually send the confirmation e-mail message and WINS/DNS request.

To determine the status of a request:

Open the RapPort application log and scroll to the end of the log file.
Search for the last occurrence of the text string "Starting RapPort AutoSetup" and check the date and time prefixed to it. This date and time should correspond to the Scheduled Task for AutoSetup.
To access Scheduled Tasks, on the Start menu, point to Settings, and then click Control Panel. Double-click Scheduled Tasks.
If the date and time do not correspond, verify the last time AutoSetup executed from Scheduled Tasks. If Last Run Time does not correspond to the time under Schedule, this implies that AutoSetup did not execute at the appropriate time.
Confirm that you have added AutoSetup as a Scheduled Task. Specify a new time to process the requests for new portals.
If the Scheduled Task successfully occurred and there are no corresponding entries in the RapPort application log, then the RapPort server is not installed properly.
Remove RapPort from the server. For more information about how to do this, see Removing RapPort.
Reinstall the RapPort server. For more information about how to do this, see Install the RapPort Server.
If the last occurrence of the text string "Starting RapPort AutoSetup" has the correct date and time prefixed to it then look for messages in the RapPort application log. For more information, see Daily Checks for possible solutions.
Search by name for current request file, for example, userdata_workspace_name.xml, in the RapPort application log.
Look for the corresponding string "RapPort Request: virtual_server_name", where virtual_server_name is the name of the requested portal. Verify the status of the request as success or failed.
If the request succeeds, see Verify Successful Workspace Creation.
If the request fails, see "Workspace Provisioning Failed."
If there is no corresponding "RapPort Request: workspace_name" string for the current request, then it implies that AutoSetup is unable to complete the request.
Restart the server.
Follow steps to restart the portal request. For more information, see Restart a Portal Provisioning Request.

The following section discusses possible resolutions based on specific failure messages in the applications log. This section contains a list of keywords or error messages, the log location, and possible resolutions.

Error: Invalid Common Administrator account

Application log – 1

Perform the following steps.

Check whether the registry key HKLM\software\Microsoft\RapPort\ CommonAdmin exists on the RapPort server. See To verify that registry entries have been successfully imported:.
Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
Check whether the user name value in this key is still a valid Windows NT domain account.
Reschedule AutoSetup to run again.

Error: Folder Not Found

Error: File Not Found

Location._ApplicationLog.txt on the RapPort server.

One of the folders required by AutoSetup process is missing. Remove and reinstall the RapPort server as described below:

"Removing RapPort"
"Install the RapPort server"
Reprocess the request, see Restart a Portal Provisioning Request. The specific procedure depends on the step where this error occurred. For example, if this error occurred during workspace creation, see If The Request Has Failed During Workspace Creation:.

Error: Error In Parsing XML

Error: Invalid ServerConfig.xml File

Location._ApplicationLog.txt on the RapPort server, sections 1.7–9, 3, 4.

This error may occur if a configuration file was recently modified and not edited correctly. The error message indicates the name of the file that is causing the problem.

Perform the following steps.

Check that file by opening that file in Internet Explorer. Internet Explorer uses its built-in XML parser to analyze XML content and report errors.
Correct any problems in the XML file by editing as directed by the original procedure or see the section, RapPort Administration and Maintenance for detailed editing instructions.
Check the XML file again by using Internet Explorer.
Reschedule AutoSetup to run again.

Error: Error Occurred In Initializing Rapport E-Mail Service

Location._ApplicationLog.txt on the RapPort server, section 3.

Confirm that the SMTP information and settings in mails.xml are correct by performing the following steps:

Open the file, mails.xml, in Internet Explorer. Internet Explorer uses its built-in XML parser to analyze XML content and report errors.
Correct any problems with file, mails.xml, by editing as directed in "To edit Mails.xml."
Check that the SMTP server name specified is correct.
Check that the e-mail user names are valid user names.
Check that the SMTP server is properly configured. For detailed procedures, see To configure the default SMTP virtual server:.
Check that the SMTP server is actually running by checking with local operations team.
Reschedule AutoSetup to run again.

Error: Error Occurred In Sending Rapport E-Mail

Location._ApplicationLog.txt on the RapPort server, section 3.

Confirm that the SMTP information and settings in mails.xml are correct by performing the following steps:

Open the file, mails.xml, in Internet Explorer. Internet Explorer uses its built-in XML parser to analyze XML content and report errors.
Correct any problems with file, mails.xml, by editing as directed in the "To edit Mails.xml."
Check that the SMTP server name specified is correct.
Check that the e-mail user names are valid user names.
Check that the SMTP server is properly configured. See To configure the default SMTP virtual server:.
Check that the SMTP server is actually running by checking with the local operations team.
Check the request status. View section 3 of the application log to determine the request status and pertinent error message.
If the request was successful, send the appropriate confirmation mail to the person who requested the site and RapPort Support. Send the WINS/DNS entry request to the appropriate e-mail account.
If the request failed, send the appropriate e-mail to RapPort Support indicating the failure and the error message recorded in the application log. Treat this as a standard failure mail, and troubleshoot accordingly.

Resolving Problems

This section provides procedures to correct RapPort in the event of a failure. It is recommended that you view this section in the context of daily monitoring tasks and diagnosing problems.

View the RapPort Server Configuration

The RapPort application maintains all configuration information in XML files on the RapPort server. These files are in the following directory on the RapPort server:

Drive:\RapPort\AutoSetup\Configuration folder

In many instances after correcting a failure, you must edit one of these files. The following sections describe when, where and how to edit these files to recover from a failure.

Address Maximum Workspace Capacity

When a destination server has reached the specified number of workspaces, it returns a status of unavailable. After a destination server has reached its capacity for workspaces, you have two options. You can increase the limit or you can add additional destination server. Both options require modifying your RapPort configuration.

To extend the capacity of a server:

Using Notepad, open ServerConfig.xml and revise it as follows.

Locate the <entry></entry> XML node for this destination server in the file.
Within this node, edit the <available>n</available> XML node and change the n to y (<available>y</available>), to mark this destination server as available for further workspace creation on it.
The XML tag <available></available> denotes the availability status of each destination server. RapPort marks a destination server as "y" in the <available> tag provided it can successfully create workspaces.
Within the same <entry></entry> node for the destination server, clear the text within the <comment><comment> node. This clears the reason for the unavailable status.
Within the same <entry></entry> node for the destination server, edit the text in the <capacity></capacity> node and replace the text within this node by an appropriate value increased value for the workspace capacity for this destination server depending on the available disk space and other criteria as appropriate.

To add new capacity by adding a new destination server:

Leave the availability status and capacity of the current destination server at its current values. This server is no longer available for processing requests.
Add an entry for a new destination server in ServerConfig.xml. For more information about how to do this, see Customizing Configuration Settings.

Reset Destination Server Status

After you resolve the underlying cause for a destination server marked as unavailable, you must reset the status to available.

The following procedure describes how to reset the status of a destination server to available.

To reset the status of a destination server:

Using Notepad, open ServerConfig.xml and revise it as follows.

Locate the <entry></entry> XML node for this destination server in the XML file.
Within this node, edit the <available>n</available> XML node and change the n to y (<available>y</available>), to mark this destination server as available for further workspace creation on it.
The XML tag <available></available> denotes the availability status of each destination server. RapPort marks a destination server as "y" in the <available> tag provided it can successfully create workspaces.
Within the same <entry></entry> node for the destination server, clear the text within the <comment><comment> node. This clears the reason for the unavailable status.

Delete a Workspace and Associated Settings

In some cases RapPort partially completes a request and then fails. In this case, it may be necessary to remove the failed workspace, so that you can process the request again and create the workspace with the proper name.

Perform the following procedures to delete the registry entries associated with discussions, the virtual server and then finally the workspace:

Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.

To delete a workspace and associated settings:

On the Start menu, click Run.
In the Open text box, type cmd.
Change Directory to the following directory:
%systemroot%\Inetpub\AdminScripts
Determine the registry sequence number associated with the virtual server.
The registry manages the virtual servers by sequence number, not by their English names. To determine the sequence number, issue the following command:
cscript adsutil.vbs enum W3SVC/1

This returns the name of the first virtual server. Repeat this command incrementing the value (initially "1" ) until the correct virtual server displays. Note this sequence number as you need it in step 7.
Close the Command Prompt.
Edit the registry by using Registry Editor.
Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
Expand the following key:
HKEY_LOCAL_COMPUTER/SOFTWARE/MICROSOFT/Office/9.0/Web Server/Number, where number is the value of the sequence number noted above.
Delete this key from the registry.
Close Registry Editor.
Delete the virtual server by using Internet Services Manager.
Wait for 5 minutes and then restart IIS.
After IIS has successfully restarted, delete the associated workspace by using the SharePoint Portal Administration.

Restart a Portal Provisioning Request

After you resolve a problem stopping RapPort from completing a request for a new portal, you can restart the provisioning process. The following sections review the possible causes and describe how to restart the provisioning process, as this process varies according to the type of failure.

If The Request Has Failed During Workspace Creation:

Using SharePoint Portal Server Administration, delete the workspace on the destination server if it exists.
In Notepad, open the corresponding request file, userdata_virtual_server_name.xml, on the RapPort server and change the request status XML node to "1" (completed request).
Save the request file.
Double-click the file to open it in Internet Explorer to confirm that the XML formatting is correct. Internet Explorer should display the file without any errors.
Follow the steps to change destination server status to available. For more information, see Reset Destination Server Status.

The RapPort server processes the request the next time AutoSetup runs as a Scheduled Task.

If The Request Has Failed After Workspace Has Been Created But Before Copy Is Instantiated:

In SharePoint Portal Server Administration, delete the workspace on the destination server, if it exists.
In Notepad, open ServerConfig.xml on the RapPort server and decrement the current workspace count for the destination server within the <current></current> XML node by one. For example, for a given server the Current value may be set to 7, it must be reduced to 6, because the workspace process was started but not successfully completed.
Save ServerConfig.xml.
In Notepad, open the corresponding request file, userdata_virtual_server_name.xml, on the RapPort server and change the request status XML node to "1" (completed request).
Save the user request XML file.
Double-click the file to open it in Internet Explorer to confirm that the XML formatting is correct. Internet Explorer should display the file without any errors.
Follow steps to change destination server status to available. For more information, see Reset Destination Server Status.

RapPort processes the request the next time AutoSetup runs as a Scheduled Task.

If The Request Failed During The Copy Process, Roles Assignment, Or Virtual Server Creation

In SharePoint Portal Server Administration, delete the workspace on the destination server, if it exists.
In Notepad, open ServerConfig.xml on the RapPort server and decrement the current workspace count for the destination server within the <current></current> XML node by one. For example, for a given server the Current value may be set to 7, it must be reduced to 6, because the workspace process was started but not successfully completed.
Save ServerConfig.xml.
In Notepad, open the corresponding request file, userdata_virtual_server_name.xml, on the RapPort server and make the following changes:
- Change the <status> tag to "1" (completed request).
- Check the request log, virtual_server_name.txt, on the RapPort server to determine the server type (Shared or Dedicated).If the server type is Shared then change the <server> tag to "shared."
Save the request file.
Double-click the file to open it in Internet Explorer to confirm that the XML formatting is correct. Internet Explorer should display the file without any errors.

RapPort processes the request the next time AutoSetup runs as a Scheduled Task.

If The Request Fails When No Destination Server Is Available For Request Processing:

Address the capacity limitations of the destination server by either increasing the capacity or adding an additional destination server. For more information, see Address Maximum Workspace Capacity.
Follow steps to change destination server status to available. For more information, see Reset Destination Server Status.
In Notepad, open the corresponding request file, userdata_virtual_server_name.xml, on the RapPort server and change the request status XML node to "1" (completed request).
Save the request file.

RapPort processes the request the next time AutoSetup runs as a Scheduled Task.

If The Request Fails When The Destination Server On Which The Request Is Being Processed Gets Marked As Unavailable:

Follow steps to change destination server status to available. For more information, see Reset Destination Server Status.
In Notepad, open the corresponding request file, userdata_virtual_server_name.xml, on the RapPort server and change the request status XML node to "1" (completed request).
Save the request file.

RapPort processes the request the next time AutoSetup runs as a Scheduled Task.

If Autosetup.Exe Stops Responding During Request Processing And The Current Request Remains With <Status> = "2" ( In Process):

Using Task Manager, terminate the AutoSetup.exe application.
In Notepad, open the corresponding request file, userdata_virtual_server_name.xml, on the RapPort server and make the following changes:
- Change the request status XML node to "1" (completed request).
- Remove the text, server_name from <server>server_name</server> XML node.
  Do not remove the XML node, only remove the text within the node.
- Remove the complete node <commonadmin></commonadmin>.
  Remove the complete node along with the tags, do not remove only the name "Common Admin."
Save the request file.
If copy was in progress and workspace creation was successful when it failed then open ServerConfig.xml on the RapPort server by using Notepad and decrement the current workspace count for the destination server within the <current></current> XML node by one. For example, for a given server the Current value may be set to 7, it must be reduced to 6, because the workspace process was started but not successfully completed.
Save ServerConfig.xml.
Follow the steps in "Delete a workspace and Associated Virtual Server" to delete the workspace and the virtual server (if created).

RapPort processes the request the next time AutoSetup runs as a Scheduled Task.

Resolving RapPort Setup Wizard Problems

This section describes errors that may occur when a user requests a new portal by using the RapPort Setup Wizard. This section lists the error messages, possible user action, and suggested resolution. These problems can be organized into two groups.

Non-Critical Errors

These are warnings or errors that may appear in a dialog box to the user when working with the RapPort Wizard. None of these errors are critical to the request process, and most are intermittent. The solution is to simply acknowledge the message and repeat the action, the request then continues. No further troubleshooting is required. These messages are listed as follows:

An error occurred contacting the server for checking URL availability. Please try again.
An error occurred contacting the server for saving the request data. Please try again.
An error occurred contacting the server for deleting the incomplete request data. Please try again.
An error occurred contacting the server for getting the users/roles data. Please refresh this page to try again.
An error occurred contacting the server for deleting the incomplete request data. Please try again.
An error occurred contacting the server for saving the users/roles data. Please try again.
An error occurred contacting the server for temporary saving of the users/roles data space.

Critical Errors

These errors cause the request process to fail, and consequently the RapPort provisioning process never begins and therefore never creates the workspace. Although there are several errors, only two situations can generate these error messages: The client computer accessing the wizard is missing a component or the server is missing a component. These messages are:

Error: An error occurred creating an MSXML2.DOM Document object. If this occurred after using the Dedicated Server dialog box, then the RapPort server is missing the MSXML3.DLL file. This file is installed as part of the SharePoint Portal Server installation.

Although the error message reports a problem with MSXML2, the actual problem is with MSXML3.

Rerun the SharePoint Portal Server installation, and select Repair. For more information, see SharePoint Portal Server Administrator's Help.

Error: An error occurred checking for URL availability._To resolve this problem, perform the following:

Check for the existence of a file named <virtual_server_name>.txt in the following directory:
drive:\RapPort\RapPortWeb\Data\CheckAvailability
If it does not exist, using Windows Explorer, check that the Windows 2000 Everyone group is assigned Full permissions on the directory:
drive:\RapPort\RapPortWeb\Data.

Error: An error occurred creating the MSXML2.ServerXMLHTTP object.
Error: An error occurred creating the MSXML2.XMLHTTP object.
Error: An error occurred creating an MSXML2.DOM Document Object.
The likely cause of these errors is that the client computer is missing the required MSXML3 component. To resolve this problem, perform one of the following actions:

Install the retail version of Office XP (some Beta versions do not contain the required components).
Install Office 2000 and MSXML3 SP-1. You can download a copy of MSXML from http://msdn.microsoft.com.