I'm trying to assign APPDIR as a virtual directory using Tools-IIS and the install goes to a successful completion but the IIS MMC shows a virtual web error status of "The system cannot find the path specified".
I checked "Virtual directory is a web application" with "application level=Medium" in Tools-IIS. Same error with "application level=Low" or "application level=High".
Even though I'm running my app as a virtual directory, it needs to run as it's own application. This is a valid IIS configuration option.
I'm running AI 3.7.1 on win xp professional sp2 with IIS 5.1 .NET 1.1.
Installation error occurs on win xp professional sp2 with IIS 5.1 .NET 1.1, AND Win 2K server sp4 with IIS 5.0 .NET 1.1.
The MetaBase entry for the created virtual directory has some wierd entries:
AppWamClsid: WAM {DA11AC7A-453F-47A0-B66C-7F55066261B7}
AppPackageID: WAM {12F8BBAA-6070-448D-A5EA-D1987D59AE07D}
AppPackageName: WAM IIS-{Default Web Site//ROOT/myapp}
AspAllowOutOfPocComponents WAM 1
When I delete these metabase properties the above error goes away. Maybe these entries are valid for windows server 2003 but they certainly muck things up in xp and win2k server.
Suggested Articles
Hi,
The Virtual Directory status message "The system cannot find the path specified" is a bogus message shown by the IIS MMC due to the fact that the respective parent Web Site was not restarted. It has nothing to do with the IIS MetaBase entries: "AppWamClsid", "AppPackageID", "AppPackageName", "AspAllowOutOfPocComponents", which have perfectly correct values automatically assigned by the IIS ADSI Provider Layer Interface.
The purpose of these metabase keys is not intended solely for Windows 2003 Server. This IIS MMC status message will change once you will restart the parent Web Site or the IIS service all together. However, the virtual directory created will be functional regardless if you do a manual restart of the parent Web Site, or not. The status message does not imply that the virtual directory is not functional.
We cannot programmatically impose a IIS service restart, or a parent Web Site restart due to the fact that this could cause a serious inconvenience for some heavy-duty servers where virtual directories or web sites must be "hot plugged".
Regards,
Ionut
The Virtual Directory status message "The system cannot find the path specified" is a bogus message shown by the IIS MMC due to the fact that the respective parent Web Site was not restarted. It has nothing to do with the IIS MetaBase entries: "AppWamClsid", "AppPackageID", "AppPackageName", "AspAllowOutOfPocComponents", which have perfectly correct values automatically assigned by the IIS ADSI Provider Layer Interface.
The purpose of these metabase keys is not intended solely for Windows 2003 Server. This IIS MMC status message will change once you will restart the parent Web Site or the IIS service all together. However, the virtual directory created will be functional regardless if you do a manual restart of the parent Web Site, or not. The status message does not imply that the virtual directory is not functional.
We cannot programmatically impose a IIS service restart, or a parent Web Site restart due to the fact that this could cause a serious inconvenience for some heavy-duty servers where virtual directories or web sites must be "hot plugged".
Regards,
Ionut
Thanks Denis for the quick reply.
You're right, restarting IIS does eliminate the error messages. I did run into a hang up when testing and don't recall exactly what the problem was. When I manually deleted the metabase entries, the problem went away. I don't recall what the problem symptoms were. If I can recreate it, I'll update this topic.
Thanks again.
You're right, restarting IIS does eliminate the error messages. I did run into a hang up when testing and don't recall exactly what the problem was. When I manually deleted the metabase entries, the problem went away. I don't recall what the problem symptoms were. If I can recreate it, I'll update this topic.
Thanks again.
FOLLOW US