IIS Migration Wizard Topics | Previous | Next

Troubleshooting the IIS Migration Wizard

Contents

Page Cannot Be Displayed Error
When Starting the Wizard from a Web Page

When you are trying to start the wizard from a Web page by connecting to http://[source]/iismu/welcome.htm, you might receive an error message that the page cannot be displayed. If you do, it means that the source Web server is not running.

To correct the problem, stop the wizard, start the source Web server, and then start the wizard again. If the source Web server is IIS, you need to start the Default Web Site or, if you have renamed or deleted it, the Web site that appears first under the Administration Web Site in the IIS snap-in of the MMC.

Page Cannot be Displayed Error after Step 2

After starting the wizard and completing the second step (Step 2: connect to the source server), you might receive an error message that the page cannot be displayed. If you do, it means that either the target component is not installed, or the target Web server is not running. To correct the problem, use the following steps:

If after taking these steps, you continue to receive an error message that the page cannot be displayed, the likely cause is that you do not have a default installation of Windows 2000 and IIS 5.0 on the target computer. The IIS Migration Wizard does not support target platforms without a default installation. You can try to correct the problem by making sure that the IIS Default Web Site responds to requests made to localhost. The wizard uses the address "localhost" when moving from Step 2 to Step 3. Use the following steps to address this problem.

  1. In the IIS snap-in on the target computer, make sure that the IP address of the Default Web Site is set to ALL UNASSIGNED.
  2. On the target computer, make sure that the IIS Default Web Site is running on port 80.
  3. On the target computer, make sure that the IIS Default Web Site is the ONLY Web site running on port 80.

Response.isClientConnected VBScript Error

If you get the following error message when running the wizard:

Microsoft VBScript runtime error '800a01b6'
Object doesn't support this property or method: 'Response.isClientConnected'

It could mean that you have an extra, outdated ASP DLL on your Windows NT source computer. To see if this is the case, on the source computer, open the \WINNT\system32\inetsrv folder. If you find a folder named ASP within it, take the following steps:

  1. Make sure that there is a file named asp.dll within the inetsrv folder, in addition to the ASP folder. If so, proceed with the remaining steps.
  2. In the Services program in Control Panel, stop the IIS Admin Service. This also stops the FTP, HTTP, and SMTP services.
  3. Back up the ASP folder and its contents to another location on your hard drive. In the unlikely case that the newer asp.dll didn't work properly, you could then restore the ASP folder to its original location.
  4. In the inetsrv folder, delete the ASP folder.
  5. In the Services program in Control Panel, restart the IIS Admin Service.
  6. Verify that script mappings are correct at each level on which you have defined an application. To do this, in the IIS snap-in, open the property sheets for each application root folder and click the Home Directory tab. Under Application Settings, click Configuration, and verify that the script mappings reference \inetsrv\asp.dll.
  7. In the Services program in Control Panel, restart the FTP, HTTP, and SMTP services.

Stalling on Netscape Source Servers

Sometimes the IIS Migration Wizard stalls while creating the migration archive on Netscape source servers. This occurs when the connection timeout value on the Netscape source server is too short. To correct this problem, use the Netscape Server Administrator to increase the value for HTTP Persistent Connection Timeout under Server Preferences/Performance Tuning.