Prev: sharepoint domain change
Next: Resolution?
From: BahBah on 13 Jan 2010 05:51
Hi

We run SBS 2008 which obviously includes Sharepoint.

Completely out of the blue today we got the following error:

Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 12/01/2010 19:55:35
Event ID: 10036
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER01.domain.local
Description:
A database error occurred.

Source: Microsoft OLE DB Provider for SQL Server
Code: 1205 occurred 1 time(s)
Description: Transaction (Process ID 52) was deadlocked on lock resources
with another process and has been chosen as the deadlock victim. Rerun the
transaction.

Context: Application 'Search index file on the search server'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3 Search" />
<EventID Qualifiers="49152">10036</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-01-12T19:55:35.000Z" />
<EventRecordID>2202</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER01.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>

Context: Application 'Search index file on the search server'</Data>
<Data>Microsoft OLE DB Provider for SQL Server</Data>
<Data>1205</Data>
<Data>1</Data>
<Data>Transaction (Process ID 52) was deadlocked on lock resources with
another process and has been chosen as the deadlock victim. Rerun the
transaction.</Data>
</EventData>
</Event>

I am unsure what I can do to see what is/has/could be broken. I can access
http://companyweb and can search. We don't really use Sharepoint much so I am
unable to test if something new should have been added to the search index.

Any assistance that can be offered would be appreciated.

Thank you
From: Harish [MSFT] on 18 Jan 2010 15:32
The WSS inbuilt search is throwing a dead lock for some reason.

1.Try restarting the Windows Sharepoint search service.
2.IISreset
3.Increase the intervals b/w the sharepoint crawls.

Harish K
From: Suraj on 16 Feb 2010 00:15
I followed the directioned mentioned below since i also have a similar
problem like in previous thread. I still have the same problem. the following
event occurs.

Event Type: Error
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 10036
Date: 16.Feb.2010
Time: 10:28:14 AM
User: N/A
Computer: NTLK02
Description:
A database error occurred.

Source: Microsoft OLE DB Provider for SQL Server
Code: 4060 occurred 1 time(s)
Description: Cannot open database "WSS_Search_NTLK02_01" requested by the
login. The login failed.

Context: Application '01ed44fa-2aa4-44d4-9e3f-76ccf3b03492'

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



"Harish [MSFT]" wrote:

> The WSS inbuilt search is throwing a dead lock for some reason.
>
> 1.Try restarting the Windows Sharepoint search service.
> 2.IISreset
> 3.Increase the intervals b/w the sharepoint crawls.
>
> Harish K
 | 
Pages: 1
Prev: sharepoint domain change
Next: Resolution?