I am having problems with Portal indexes after migrating from one IIS
server to another (using the same SQL databases, SPS 2003). I am
getting a "protocol handler cannot be found" error whenever I
kickstart an crawl. I have done some investigation and I think the
problem is that when we installed SPS2003 on the new IIS server it
generated a new random port number for the Central Admin pages. When
we then restored the metabase from the OLD IIS Server it overwrote
that random number and we just changed the shortcut properties
accordingly for Central Admin. I wonder now if when the index starts
it is trying to invoke the HTTP protocol (also mentioned in the error
message) on the initial port number that was created, not the one that
we restored. I hope that I am on the right track and that that makes
some sense. Does anyone have any idea where I can find the original
port number stored and either change it to the new number or use
stsadm to set the existing port number to the original one?