You may experience problems when you search for content on SharePoint Portal Server 2003

Article translations Article translations
Article ID: 835225 - View products that this article applies to.
Expand all | Collapse all


In a server farm deployment of Microsoft SharePoint Portal Server 2003, when the servers are under a heavy load, users may experience problems when they search for content. For example, queries to the portal site may time out. Additionally, error messages that are similar to the following are logged to the application event log of one or more servers in the server farm:

Event ID: 2262
Type: Warning
Source: W3SVC-WP
Category: None
ISAPI 'Drive:\Windows directory\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.

Event ID: 1000
Type: Error
Source: Windows SharePoint Services 2.0
Category: None
#50070: Unable to connect to the database Database Name on SQL Server Computer Name. Check the database connection information and make sure that the database server is running.


This problem may occur when heap corruption occurs under low memory conditions. When heap corruption occurs under low memory conditions, the Microsoft Search Tripoli Query component (Tquery.dll) stops responding.


This problem is corrected in Microsoft SharePoint Portal Server 2003 Service Pack 1.

To resolve this problem, obtain the latest service pack for Microsoft SharePoint Portal Server 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
889380 How to obtain the latest service pack for SharePoint Portal Server 2003


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in SharePoint Portal Server 2003 Service Pack 1.


Article ID: 835225 - Last Review: July 26, 2006 - Revision: 4.6
  • Microsoft Office SharePoint Portal Server 2003
kbqfe kbshareptportalsvr2003sp1fix kbqfe kbfix kbbug KB835225

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from