Prev: Portal Creation Failed !!
Next: Restore SPS 2003
From: Jay on 20 Jun 2005 14:32 I rolled my migration over the weekend and an ugly issue has raised it's head. My search at both the Portal And WSS site level has broken. I am using SSL and have changed the configuration in the Configure Alternate Portal Access to reflect that but when I try and crawl portal or non-Portal content get the following error message in the gatherer log 6/20/2005 10:20:00 AM Modify https://servername/ The address could not be found, (0x80041204 - An unrecognized HTTP status was received. Check that the address can be accessed using Internet Explorer. ) I can access the portal by clicking the servername link. Any suggestions are appreciated! TIA
From: Harry Ng on 22 Jun 2005 13:25 Let's try to remove all the index and serch server in the "chnage component" page and then restore all the settings and try full crawl again. This can refresh index settings. -- Harry Ng harry(a)infocan.net System Consultant Microsoft Certified Trainer INFOCAN Computer (HK) Limited "Jay" wrote: > I rolled my migration over the weekend and an ugly issue has raised it's > head. My search at both the Portal And WSS site level has broken. I am using > SSL and have changed the configuration in the Configure Alternate Portal > Access to reflect that but when I try and crawl portal or non-Portal content > get the following error message in the gatherer log > > 6/20/2005 10:20:00 AM Modify https://servername/ > The address could not be found, (0x80041204 - An unrecognized HTTP status > was received. Check that the address can be accessed using Internet Explorer. > ) > > I can access the portal by clicking the servername link. > > Any suggestions are appreciated! > > TIA
From: Jay on 22 Jun 2005 14:20 Actually fixed it by telling Sharepoint to "ignore SSL Name Warnings" basically I have a name mismatch on the certificate and the server since we mapped our existing Sharepoint URL to a new serverwith our new implementation. The certificate points at the URL and generates warnings out the wazoo in the Gatherer logs. Once I checked the box to ignore the Name Warnings it has worked quite well. Thanks for the suggestion Harry "Harry Ng" wrote: > Let's try to remove all the index and serch server in the "chnage component" > page and then restore all the settings and try full crawl again. This can > refresh index settings. > -- > Harry Ng > harry(a)infocan.net > System Consultant > Microsoft Certified Trainer > INFOCAN Computer (HK) Limited > > > "Jay" wrote: > > > I rolled my migration over the weekend and an ugly issue has raised it's > > head. My search at both the Portal And WSS site level has broken. I am using > > SSL and have changed the configuration in the Configure Alternate Portal > > Access to reflect that but when I try and crawl portal or non-Portal content > > get the following error message in the gatherer log > > > > 6/20/2005 10:20:00 AM Modify https://servername/ > > The address could not be found, (0x80041204 - An unrecognized HTTP status > > was received. Check that the address can be accessed using Internet Explorer. > > ) > > > > I can access the portal by clicking the servername link. > > > > Any suggestions are appreciated! > > > > TIA
|
Pages: 1 Prev: Portal Creation Failed !! Next: Restore SPS 2003 |