System cannot find the path specified code 0x80070003

[guest]

Case 1: The downloaded file is damaged. Re-downlaod it.

Case 2: The user doesn't have write permission in the folder you try to install the software.

Case 3: If it is windows 7 or windows 2008 R2, you may want to logon administrator to install the software.

Case 4: "The System Cannot Find the Path Specified" Event ID 5007 Message is Logged by the Microsoft Exchange System Attendant
This behavior can occur because the msExchDataPath attribute on the server object is the base folder where the system attendant writes the tracking log files. However, it appends the ServerName.log. For example, if the server has the name Server7890, the value for the msExchangeDataPath attribute is drive name:\Exchsrvr. The actual path to which the tracking logs are written is similar to the following example:
drive name:\Exchsrvr\Server7890.log
This event ID message is common on Cluster Servers; however, it is not restricted to Cluster Servers.
To resolve this behavior, make sure that the msExchDataPath attribute is pointed properly, and that the msExchDataPath attribute contains a folder ServerName.log

To modify the msExchDataPath attribute, start ADSI Edit from the Windows 2000 Support Tools.

WARNING: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Exchange 2000 Server, or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.


In ADSI Edit, click to expand the Configuration container.
Click to expand each of the following:
CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=YourOrganization, CN=Administrative Groups, CN=YourAdministrative Group, CN=Servers, CN=ServerName
Right-click ServerName, click Properties, and then in the Select Property to View list, click the msExchDataPath attribute.
Type the correct path in the Edit Attribute box, and then click Set.
Restart the Exchange 2000 Server computer.

[guest]

When you try to open Internet Services Manager (ISM) or a Microsoft Management Console (MMC) snap-in on a computer that is running Microsoft Internet Information Services 5.0 (IIS), you may receive an error message that is similar to the following:
Error connecting to ServerName:
The system cannot find the path specified.
Do you wish to continue to attempt to connect to this server in the future?
Note ServerName is the name of the server that is running IIS.

If you click Yes, the name of the server does not appear in ISM or in the MMC, and you cannot configure any Web sites. Additionally, Microsoft FrontPage server extensions and Web publishing may not work as expected.

You experience these symptoms even though all existing Web sites start and work as expected.

This issue occurs if the configuration information in the IIS metabase does not match the services that are installed on the computer. This issue is known to occur if the following conditions are true:
The FTP Publishing Service is installed on the computer.
The IIS metabase contains no configuration information for the FTP Publishing Service.

Method 1: Use the Adsutil.vbs utility to determine the services that are configured in the metabase
To use the Adsutil.vbs utility to determine the services that are configured in the IIS metabase, follow these steps:
Click Start, click Run, type Services.msc, and then click OK.
In the Services snap-in, under Name, verify the IIS services that are installed on the computer.
Click Start, click Run, type cmd, and then click OK.
At the command prompt, type the following command, where HardDisk is the hard disk where IIS is installed:
cd HardDisk\inetpub\adminscripts
To verify that an IIS service is configured in the metabase, type the following command at the command prompt, where ServiceName is the IIS service that you want to verify in the IIS metabase:
Adsutil.vbs enum ServiceName
For example, to verify that the IIS metabase contains configuration information for the FTP Publishing Service, type Adsutil.vbs enum MSFTPSVC.

If you receive an error message that is similar to the following, the IIS service may not be installed correctly:
The path requested could not be found.
After you determine the configuration differences between the information that is stored in the metabase and the services that are running on the computer, install or remove services on the computer. To do this, follow these steps:
Click Start, click Run, type Appwiz.cpl, and then click OK.
Double-click Add/Remove Windows Components.
Double-click Internet Information Services (IIS).
Click to select or click to clear the check boxes for the services that you want to configure, and then click Next.
Follow the prompts on the screen to complete the Windows Components Wizard.
Back to the top
Method 2: Delete the registry key for the FTP Publishing Service
To delete the registry key for the FTP Publishing Service, follow these steps:

Note Only follow these steps if the FTP Publishing Service is installed on the computer and if the IIS metabase contains no configuration information for the FTP Publishing Service.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
Click Start, click Run, type cmd, and then click OK.
Locate the folder where the Adsutil.vbs file is located.
To enumerate the configuration information for the FTP Publishing Service in the IIS metabase, type the following command:
Adsutil.vbs enum MSFTPSVC
If the IIS metabase contains no configuration information for the FTP Publishing Service or if you receive an error message, go to step 4.
Click Start, click Run, type regedit, and then click OK.
Locate and then right-click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\INetMgr\Parameters\AddOnServices\FTP
In the right pane, right-click FTP, and then click Delete.
Quit Registry Editor.

[guest]

If you use command line, the path named in the command does not exist for the drive specified, or the path was entered incorrectly.

Retry the command using the correct path.

[blin]

In our case, copy the update file from network drive to a local drive. Then run it from the local drive. That works for us.