SYMPTOMS
When you try to use the search feature in Microsoft Office SharePoint Portal Server 2003, the search feature returns no results. Additionally, you receive the following error messages in the gatherer logs.
You receive the following error messages in the gatherer logs for the Portal_Content index:
XX/XX/XXX HH:MM:SS Add http://Servername
The address could not be found, (0x80042616 - Error in the Site Data Web
Service.)
XX/XX/XXX HH:MM:SS Add
sps://Servername/site$$$people
The address could not be found, (0x80042617 - Error in the Site Data Web
Service.)
You receive the following error messages in the gatherer logs for the Non_Portal_Content index:
XX/XX/XXX HH:MM:SS Add
sps://Servername/site$$$site/scope=$$$default$$$
The address could not be found, (0x80042617 - Error in the Site Data Web
Service.)
Additionally, you receive the following three events in the Application log.
Event ID 3036
Event Type: Warning
Event Source: Microsoft SharePointPS Search Service
Event Category: Gatherer
Event ID: 3036
Date:
MM/DD/YYYYTime:
HH:MM:SSUser: N/A
Computer:
SERVERNAMEDescription:
The content source <sps://servername/site$$$people> cannot be accessed.
Context: http://servername/ Application, Portal_Content Catalog
Details:
Error in PortalCrawl Web Service. (0x80042617)
Event ID 3036
Event Type: Warning
Event Source: Microsoft SharePointPS Search Service
Event Category: Gatherer
Event ID: 3036
Date:
MM/DD/YYYYTime:
HH:MM:SSUser: N/A
Computer:
SERVERNAMEDescription:
The content source <http://servername/> cannot be accessed.
Context: http://servername/ Application, Portal_Content Catalog
Details:
Error in the Site Data Web Service. (0x80042616)
Event ID 3024
Event Type: Error
Event Source: Microsoft SharePointPS Search Service
Event Category: Gatherer
Event ID: 3024
Date:
MM/DD/YYYYTime:
HH:MM:SSUser: N/A
Computer:
SERVERNAMEDescription:
The update cannot be started because the content sources cannot be accessed. Fix
the errors and try the update again.
Context: http://servername/ Application, Portal_Content Catalog
Note If you use a Microsoft Network Monitor trace to crawl SharePoint Portal Server 2003, you may see traffic that resembles the following:
<<FRAME: 1696>>
GET / HTTP/1.0
<<FRAME: 1705>>
HTTP/1.1 401 Unauthorized
<<FRAME: 1713>>
GET / HTTP/1.0
<<FRAME: 1722>>
HTTP/1.1 401 Unauthorized
<<FRAME: 1726>> (starting NTLM)
GET / HTTP/1.0
<<FRAME: 1727>> (responding w/ NTLM)
HTTP/1.1 401 Unauthorized
<<FRAME: 1730>> (final NTLM)
GET / HTTP/1.0
<<FRAME: 1733>> (good response, we send the client over to default.aspx)
HTTP/1.1 302
<<FRAME: 1734>> (good response)
302 FOUND
<<FRAME: 1736>> (with our established NTLM)
GET /default.aspx HTTP/1.0
<<FRAME: 1871>> (good response, with our homepage being sent )
HTTP/1.1 200 OK
<<FRAME: 1873>> (continuing to send page)
<<FRAME: 1874>>(continuing to send page)
<<FRAME: 1877>>(continuing to send page)
<<FRAME: 1879>>(continuing to send page)
<<FRAME: 1880>> RST, ACK (from indexer)
<<FRAME: 1881>> RST (from indexer)
<<FRAME: 1882>> (continuing to send page)
<<FRAME: 1883>> RST (from indexer)
<<FRAME: 1884>>(continuing to send page)
<<FRAME: 1885>> RST (from indexer)
<<FRAME: 1887>> RST (from indexer)
<<FRAME: 1888>> (still continuing to send page)
<<FRAME: 1889>> (TCP reset from search machine.)
RESOLUTION
To resolve this problem, install Microsoft Office SharePoint Portal Server 2003 Service Pack 2 (SP2). After you install SharePoint Portal Server 2003 SP2, the SharePoint Portal Server Virtual Server that is running the .NET Framework 1.1 will work in the environment that has the .NET Framework 2.0 installed.
To download SharePoint Portal Server 2003 SP2, visit the following Microsoft Web site: