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.


Tuesday, November 16, 2010

The credentials you provided for the sql server service are invalid & The current SKU is invalid

Summary: The credentials you provided for the sql server service are invalid & The current SKU is invalid

Ok, disk problems resolved, resuming the install (not doing advanced prepare this time!)
Successfully installed first single node cluster, hoooooray!!!!
When attempting to add node to the cluster, it failed stating “the credentials you provided for the sql server service are invalid”. It Failed on SQL Server / SQL Server Agent. I attempted to change the password to no avail, failed every time.
Found this article: which states “To work around this issue, type the domain account manually in the Account Name text box.” This is not true, as the boxes are grayed out and do not allow you to change the account.
Unsure to as where I got the information from, but I had read somewhere that CU1 would resolve this specific issue (trying to find link).
Ok, installed SP1 on the node which has the single node cluster setup.
Attempted to add node, “Failed: SQL 2008 Cluster – The current SKU is invalid.”
Found these articles: &
Install SP1 on a node that doesn’t have SQL installed huh? Interesting. The 2008 cluster install doesn’t use the task scheduler any more, and the nodes have to be manually installed, so why do I need to patch a server that doesn’t have any trace of SQL on it yet?
Low and behold, when I went to install SP1 on each of the other nodes, it patched the “shared features” successfully.
Tried to add node to cluster, successful on each node!
Had to install SP1 again on each node after I completed the install.
What did I learn?
You need to install SP1 (or at least CU1) after installing your first single cluster node. After that, you have to install SP1 (or CU1) prior and post to adding any other nodes on the cluster. Crazy, but at least I know now.



Migrate 07 Content DB to 2010--last two steps!

Reset Site Definition under site actions, then go in and do visual upgrade.


Thursday, October 7, 2010


Download them here, I forgot where I got them from...


SharePoint Server 2010 performance and capacity test results and recommendations

I took the liberty of zipping up all the word docs from MS and giving you guys a link :)


SharePoint 2010 SharePoint Sizer Tool

HP has a pretty cool tool for SharePoint Architects, download it here.

HP Sizer for Microsoft SharePoint is a complimentary planning resource that encapsulates knowledge gained from extensive performance characterization of Office SharePoint Server 2007 and SharePoint 2010 in the HP Alliances Performance and Solutions labs, widespread collaboration between HP and Microsoft, and numerous SharePoint performance whitepapers produced by HP engineering. The Sizer offers a quick and consistent methodology for determining and comparing configurations, as well as detailed, customizable server and storage solutions complete with bill of materials and pricing.

HP Sizer for Microsoft SharePoint solicits data or uses built-in defaults to determine optimal configurations based on SharePoint deployment best practices. Selectable configurations include entry level, highly available, and application optimized solutions. A "what if" feature allows rapid comparison of the effects of workload changes, platform and storage technology selection, and provides role-based server configurations, capacity utilization, and estimated network traffic. Users can select a configuration and then customize their environment by adding or substituting components within best-practice guidelines.

The tool also addresses one of the most critical areas of SharePoint server design: performance and capacity planning for the storage subsystem. Its storage sizing and configuration capabilities offer detailed best-practice storage volume and RAID recommendations to support database and content storage needs using HP direct-attach storage, HP StorageWorks MSA or EVA Storage SAN solutions.

Monday, October 4, 2010

Configure NLB as normal on a windows 2003/2008 box.

Configure NLB as normal on a windows 2003/2008 box.

Add new server to the farm and select host site on this server

Go into the registry of the server HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14\WSS

For each server make sure the link is going to the server itself. This fixes your actual server link in the programs shortcuts on each server.

Then, go into Central Admin on either server and configure access mappings.
Drop down the application and click central admin. Make one of them the default and the other the Intranet.

So, you should have for instance: DEFAULT http://gigaportal:9111 and INTRANET http://gigaportal2:9111

Friday, August 27, 2010

SPS 2010 Developer Dashboard...helps in troubleshooting

Stsadm –o setproperty –pn developer-dashboard –pv ondemand (or “on” or “off”)

This will put a small icon in the top right of your sharepoint page. Click it and it will display debugging info on your page all the way at the bottom. The cool thing is its activated by each person, by that if you click it, only you see the information.

Very useful!

Language Translator for SharePoint

This thing is cool. Just add a content editor webpart. Paste the code in a .txt file and link the content editor to the .txt file in the sharepoint library.

really cool and a load of time savings!

Thursday, August 26, 2010

Moving site collections to new databases SharePoint 2010

On the SharePoint Server, open command prompt to hive.
Type Stsadm -o enumsites -url > .xml

I used this for example:
Stsadm -o enumsites -url http://sp-giga > c:\sites.xml

Edit the sites.xml file to remove all sites that you do NOT want to move to another content db.

Then once you have done that, save the file back to c:\sites.xml.
Type Stsadm -o mergecontentdbs -url -sourcedatabasename -destinationdatabasename -operation 3 -filename

For example:
Stsadm -o mergecontentdbs -url http://sp-giga -sourcedatabasename wss_content -destinationdatabasename wss_content_sc_IT -operation 3 -filename c:\sites.xml

Check to make sure the sites moved over in central admin, manage content databases

Tuesday, August 24, 2010

SharePoint 2010 fly-out menu NOPE not there!

Flyout levels are still a problem for SharePoint, you will need to modify the v4.master page and change the string value DynamicDisplayLevels from “1” to “3”, and this will allow sub menus to fly out three levels. In order to do this, make sure you have the publishing feature on and the navigation is set to show sub-sites. In order to change this value, use SharePoint designer, open up the master page and click code view. Do a find for the string. Save it, publish it, approve it.

SharePoint 2010 .pdf's here we go again

This post covers everything to a tee, and works perfectly. The only thing I have to add is this:

In the web browser, open Central Admin, under Application Management, click manage service applications.

Left side, click file types. Click new file type, put .pdf in there. Scroll down the list you should see the pdf icon there now and associated to adobe.

This actually worked better in 2010 then 2007!

SharePoint 2010 pre-req's location for download

Here is the location of all those pesky pre-reqs you need prior to installing sharepoint. You ask why do this? Well, if you have a lab setup with NO internet connectivity it is a very useful thing to have them all on a usb stick!

Friday, August 20, 2010

SQL server at (Blank) has an unsupported version 10.0.2531.0

You update SQL 2008 to SP1 thinking ok I am ready......NO U R NOT! You will get the folowing error:

SQL server at [Your-DATABASE-SERVER] has an unsupported version 10.0.2531.0. Please refer to “” for information on the minimum required SQL Server versions and how to download them.

You might see threads here an there say that the minimum build number for SQL server is 10.0.2531.0. This is not very accurate as the minimum build for SPS 2010 for the SQL 2008 Enterprise Edition is the version number 10.0.2714.0 which is the cumulative update package 2. They are up to five now which I will post the link here:

If I had read the Pre-req from Microsoft for SharePoint 2010 it does state this.......But who reads! :)

SharePoint 2010 n SQL 2008 can't connect to DB

  1. Open the SQL Server Configuration Manager (Start > SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager
  2. Navigate to the SQL Server Network Configuration > Protocols for MSSQLSERVER node in the tree view
  3. Enable TCP/IP and Named Pipes (you’ll be warned that these changes will not apply until you the service is shut down)

That will allow you when installing SPS 2010 to connect to a SQL 2008 Server. This took 4 hours to finally figure out.