Thursday, December 16, 2010

Fix the SharePoint DCOM 10016 error on Windows Server 2008 R2

Thank you Wictor for this great post......Works perfectly.

Schannel error showing up on your front-ends event log

I am posting this as I have search the web for quite awhile and found a lot of issues surrounding this. However for SharePoint related issues I found very little. It seems this error could be realted to you using https in your sharepoint farm and a process or user initiates a http request instead. This error is just reporting it. As far as I know, these errors are common and not serious, it is simply a Security feature of Windows Server 2008 R2 that any negotiation or problem of unexpected messages for secure channel can be recorded. The Schannel level of logging can be configured as described in:


The General error is
The following fatal alert was generated: 10. The internal error state is 1203 "or it could be 10".
The Details are
- System
- Provider
[ Name] Schannel
[ Guid] {1F678132-5938-4686-9FDC-C8FF68F15C85}
EventID 36888
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2010-06-18T04:51:41.830028400Z
EventRecordID 10087
- Execution
[ ProcessID] 604
[ ThreadID] 3828
Channel System
- Security
[ UserID] S-1-5-18
- EventData
AlertDesc 10
ErrorState 1203 or it could be 10

Thursday, December 2, 2010

Added SSL now crawls stopped

First, open IIS manager, go to the sharepoint site, then double click SSL settings, check if you set “client certificates:” to Accept, if you did, change it to Ignore.

Second, use the default content access account when you specify authentication in crawl rules.