Feeds:
Posts
Comments

Archive for the ‘Tutorial’ Category

Howdy,

The Problem.

For teamsites and collaborations, sometimes it can be useful to upload big file size documents – which is allowed only partially by SharePoint and IIS. They both have different default settings for the maximum upload file size of a single document or file. They are:

  • SharePoint Server 2010: 50 MB
  • IIS7: ~30 MB

So, when trying to upload a big document, this results in the following error:

image

85 MB is simply too much for the above mentioned settings. Now, the solution section will show you how to fix this.

The Solution.

The good news is: This can be custom tailored to your needs, by simply following 3 steps. Here comes the first step:

1. Increase the SharePoint Upload Limit via Central Administration

First, you must increase the SharePoint 2010 upload limit.

  • Central Administration
  • “Manage Web Applications”
  • Select desired web application row (don’t click on the title, just select)
  • “General Settings” in the ribbon
  • Under Maximum Upload Size, change the setting to the desired value (e.g. 200 MB in our example)
  • “OK”

 

image

Now, the web app is equipped for receiving large files, but IIS7 will still prohibit it, resulting in the same error message as above. So, let’s move on to step 2.

 

2. Increase the IIS7 request length

Use the following command on the machine you are running the IIS 7:

%windir%\system32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:valueInBytes

In our case, we’ll simply put 200x1024x1024=209715200 bytes.

You will receive a confirmation message after applying the command. Please bear in mind that you will need to run the cmd.exe in administrator mode.

image

 

3. Increase the IIS7 connection timeout length (optional)

One more thing to keep in mind is the connection timeout settings: When you upload large files, depending on your connection speed it can happen that the connection times out. If you want, you can increase the connection timeout to a larger value. The standard is 120 seconds. This step is optional, but can become required if you have users with low speed internet connections.

image

  • Open IIS
  • Select the Web Application
  • Click on Advanced Settings
  • Expand Connection Limits
  • Set the new value for Connection Time-out (seconds)

 

This is it – all done!

You users will now be able to upload larger files:

image

As usual, test any commands, configuration and settings on a test environment before applying them in production. Applying request lengths bears also some security implications to keep in mind. Use any advices and configurations at your own risk and evaluate risks before applying them.

 

Have a nice day and best regards!

Martin

Read Full Post »

Howdy folks,

if you are searching for the already installed MOSS 2007 language packs and don’t know where to find them, open the Registry Editor and search for the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\InstalledLanguages

It will give you a list with the installed languages, providing the corresponding LCIDs (e.g. 1033 for “English”).

image

Fig. 1: RegEd reporting three installed language packs for MOSS 2007.

 

Make sure not to change any settings in this place, as MOSS 2007 will manipulate these settings automatically upon installation/uninstallation of a language pack.

 

Enjoy and have a good time!

Best regards,

Martin

Read Full Post »

UPDATED: Find the new Youtube Link below!

Dear all,

episode 4 of SP5 is ready! This time it is dealing with the topic of moving site collections from one content database to another. Click below to watch the video (UPDATED):

Remark: If you want to create a new site collection using a specific content database, you need to use PowerShell, specifically the New-SPSite cmdlet:

New-SPSite –ContentDatabase <DBName>

This cannot be done from within Central Administration.

The involved cmdlets are:

Get-SPSite (lists site collections)
Get-SPContentDatabase (list content databases)
Move-SPSite (list content databases)
New-SPSite (create new site collection, specify content DB)

Important: After moving a site collection from one content DB to another, an iisreset is required. Be aware that this will cause a service disruption for some time (depending on your server’s configuration). Be sure to execute this only if you are fully aware that this will cause all websites to be inaccessible for some time.

Disclaimer: All tutorials are provided as is. You are responsible for any changes undergoing your system that derive from following this tutorial. It is hence recommended to consult your administrators and verify that the changes cannot harm your IT environment in any way.

Stay tuned till the next time!

Martin

Read Full Post »