Skip to main content

James Milne

Go Search
Home
Downloads
 Help (new window) 
 

James Milne > Categories
SQL Database Collation Settings

This problems comes up from time to time when you try and install MOSS or WSS you might get the following message in the event log:

Error thrown to event log
---------------------------------------
The SQL Server collation on SQL Server instance ServerName\InstanceName
is not supported.  Windows SharePoint Services requires a Latin1 General
dictionary order, case insensitive, accent sensitive, kana sensitive, and
width sensitive collation (SQL_Latin1_General_*_CI_AS).

When you install or configure your SQL Server you should ensure to enable "Kana – sensitive" and "Width – sensitive" on the collation settings.

For more information read Prepare the Database Services article on tech Net:

SQL Server and database collation

The SQL Server collation must be configured for case-insensitive. The SQL Server database collation must be configured for case-insensitive, accent-sensitive, Kana-sensitive, and width-sensitive. This is to ensure file name uniqueness consistent with the Windows operating system. For more information about collations, see "Selecting a SQL Collation" or "Collation Settings in Setup" in SQL Server Books Online.

SharePoint Version numbers are different in “Site Settings” and “Central Admin”.. What?

Background

I had someone ask me "why are the version numbers in central administration different to the version numbers listed in site settings?" At first I was really bewildered by what them meant and I initially thought they might just be looking at the wrong environment. But sure enough a few screen shots later it was confirmed that the settings listed in Central Administration were very different to the numbers listed in the Site Settings.

Issue

Since being asked the original question I have come across a few other installations with the same issue, so I thought it would be worth a post.

Central Admin reports a version number that is higher than the version number reported in Site Settings.

Same farm, same content dbs..

Cause

 

The root of the problem is caused by not successfully completing the process of applying the WSS & MOSS service packs. You need to remember after applying the WSS or MOSS Service pack you MUST runt the "SharePoint Technology & Configuration Wizard" to "APPLY" the changes to SharePoint. In both of the environments that I came across this issue it was painfully obvious when I ran the "SharePoint Technology & Configuration Wizard" (aka PSConfig) what the issue was because the wizard offers to "apply updates" rather than the usual "Add/remove from farm" options.

 

Please, Please remember that you must also SUCCESSFULLY run the Wizard. Sometimes the wizard does bomb out with permission or connectivity issues, but you can simply run it again to re-try the updates.

Solution

 

Successfully complete the "Apply Update" phase by running the wizard. If it bombs out read the log and resolve the issues then run the wizard again. It must make it though the "apply updates" phase 100% (90% or "near enuf" wont do!) J

Event ID 10016 – DCOM Errors on a SharePoint Box

Error Message

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user <MOSS Service Account> SID <Account SID>. This security permission can be modified using the Component Services administrative tool.

Background

This is a common configuration issue, especially when following current best practices, such as NOT using Service accounts with local Administrator rights. Of course if you make your Moss.Service account a local Administrator this error message will go away, but that is overkill and your SharePoint Application pool service accounts do not need that level of access.

Solution

As the error message indicates you can use the "Component Services" Administrative tool which can be found in the Control Panel.

 

 

Further Reading

Thanks to Brad Saide for pointing out the official Microsoft Article KB920783.

Default Upload limit

 

This week I have been asked a few questions about the default upload limit that SharePoint uses.

First question was:

> Is there a file size limit for uploading files into SharePoint. If there is a limit, does SharePoint give you a warning advising that the file is too big?

Ok, easy question, Yes. The default file upload is 50MB. This can be increased to any _reasonable_ site required. I have personally tested up to 300 MB without any issues.

With regard to the warning message, unfortunately not. It usually lets you upload and when you hit the limit it bombs out and then tells you that the file was too bit.

This is understandable because the web browser can't tell sharepoint how big the file is until it has been uploaded, so a slight inconvenience.

Another unfortunate gotcha is the "Multi Upload" tool.. lets say the default upload limit of 50 MB is in place and I have 3 files all of 20 MB each. You might think cool 20 MB is less than 50 MB so I am fine to upload. Well this is the case if you use Explorer view or the Single file upload, but if you use the Multi Upload tool then you need to understand that the files are streamed up to the server as one continuous upload, so hence in this scenario the stream will be 60MB in size.. and of course you will get to 50 MB uploaded before the upload errors out.

 

The second question was:

> I have changed the Default upload limit in Central Admin but we are still getting a limitation on the file upload size. What gives?

Error Message:

Unhandled Exception: Microsoft.SharePoint.SPException: The form submission cannot be processed because it exceeded the maximum length allowed by the Web administrator. Please resubmit the form with less data.

 

Well because SharePoint is built on top of ASP.Net it inherits the same technical limitations and configurations. If you take a look in the Web.Config file there should be the following entry:

<httpRuntime maxRequestLength="51200" />

 

If this entry is present then you will need to change this value as well. More detail in KB822059.