Hi
Transferred a site from IIS4 to IIS6 the other day and was quite
impressed. However, we were having problems with the FrontPage2002
search engine component. I checked that under "Web Service Extensions"
in IIS6 management that I had allowed "All unknown CGI extensions" as
I know from bitter experience that IDQ falls under that category.
However, still no joy. Was coming up with errors finding
"/_vti_script/mypage.htm0.idq" saying "the system cannot find the path
specified". A fair amount of headscratching ensued as I could see the
IDQ and the HTX there fine.
After some time, I found that the IISMT tool had also migrated the
extension mappings for .asp, .idq, .htx and just about every other
extension too. Of course, they were located in \winnt.... on the old
server and \windows.... in the new. Hence they were all screwed up.
Posting for the benefit of anyone else who gets caught up in this.
I can't see any benefit for transferring extension mapping like this,
especially when these are basic 'default' extension handlers
(especially for .asp for example) and it doesn't even check to make
sure the new ones exist (or attempt to migrate them). So you get a
broken configuration out of it in other words.
Perhaps anyone from MS reading might like to enlighten me with a
cracking reason for this :)
AW