Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Portal Indexes fail after IIS migration

  Asked By: Mindy    Date: Jul 06    Category: Sharepoint    Views: 753

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?



3 Answers Found

Answer #1    Answered By: Laura Walker     Answered On: Jul 06

Here's the command you're looking for:

stsadm.exe -o setadminport
-port <port>

Answer #2    Answered By: Nina Banks     Answered On: Jul 06

that looks like just the job to change
the port number. Unfortunaely I do not know what port the installation
of SPS on the new server used (we changed the shortcut property and
overwrote the metabase). I think unless I can change the port number
that we bought over with the old metabase to the port number used by
the current installation I am going to have to reinstall SPS on a
blank IIS server.

If I have overwritten the metabase and changed the shortcut does
anyone know where I can find the port number used by the SPS
installation on the new server?

Answer #3    Answered By: Renee Murray     Answered On: Jul 06

I got this sorted in the end. I was barking up the wrong tree
with the port number thing. Even after I completely reinstalled SPS I
still had the problem. In the end reinstalling SPS Service Pack 2
AFTER I had connected to the existing config database fixed the
problem (which was a Microsoft bug apparently). I had previously
installed the relevant WSS and SPS Service Packs prior to connecting
to the config database.

Didn't find what you were looking for? Find more on Portal Indexes fail after IIS migration Or get search suggestion and latest updates.