Event Id | 1000 |
Source | Windows SharePoint Services 2.0 |
Description | #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. |
Event Information | According to Microsoft: CAUSE: This problem occurs when one or both of the following conditions are true: • You configure an Internet Information Services (IIS) virtual server that has an assigned IP address, and then extend that virtual server by using Windows SharePoint Services. • You configure an IIS virtual server that has a host header name, you extend that virtual server by using Windows SharePoint Services, and then you install Web Part assemblies in the Bin folder instead of in the global assembly cache. In each of these configurations, the Microsoft Office SharePoint Portal Server 2003 services cannot obtain sufficient information from the virtual server to load the Web Part or the Web Parts. Therefore, you receive the message that is described in the "Symptoms" section. RESOLUTION: To resolve this problem, obtain the latest service pack for Windows SharePoint Services. For more information, click the following article number 887624 CAUSE 2: 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. RESOLUTION: A supported hotfix is now available from Microsoft |
Reference Links | Event ID 2262 and event ID 1000 occur, and users experience search problems in SharePoint Portal Server 2003 You may get unexpected search results or errors from a server farm with the Chinese (Traditional) version of the SharePoint Portal Server 2003 event id:1000 source:Windows SharePoint Services 2.0 Article:887624 Description of Windows SharePoint Services Service Pack 2 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.