Feeds:
Posts
Comments

Archive for the ‘Web Application’ 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 »

Dear all,

it is my pleasure to announce a new initiative of communicating SharePoint knowledge via videos using the “SharePointFive” approach: Show how technical configurations are done within only a few minutes (guideline: 5 mins per video, up to a max of 15 in special cases.

If you want to learn about SharePoint 2010 configurations, but only want to invest a few minutes at a time, if you are looking for the essentials that make up what you actually want to do, then SharePointFive is for you.

SharePointFive (SharePoint5)

SharePointFive is a youtube channel, that you can access under the below mentioned URL. It contains all videos (currently 1 only :-)) that have been and will be published, showing how to apply SharePoint (or related) configurations in just a few minutes. Usually, like in this case, there will be published a related blog post on angler.wordpress.com, in order to facilitate it for you to copy scripts and apply them.

SP5Logo

http://www.youtube.com/sharepointfive

The Video

The video will give you an idea of the steps to be executed, a few caveats. But most of all, it is only a few minutes long and won’t take a long time to watch. This first episode of SharePointFive is  a bit longer (about 12-13 minutes), since it contains also the explanation and motivation why SP5 has been launched.

The Scripts

1. Create the Master Key:

 1: USE master;
 2: 
 3: go
 4: 
 5: CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'n0PWStealingAll0w3d!';
 6: 
 7: go

2. Create the Certificate:

 1: CREATE CERTIFICATE SP5Certificate WITH SUBJECT = 'SP5 DEK Certificate';
 2: go
 3: 

 

3. Back up Certificate & Private Key (EXTREMELY IMPORTANT TO KEEP IT BACKUPPED AND SAFE!):

 1: USE master;
 2: go
 3: BACKUP CERTIFICATE SP5Certificate TO FILE = 'C:\Certificate\TDECertificate.cer'
 4: WITH PRIVATE KEY (
 5: FILE = 'C:\Certificate\PK.pvk',
 6: ENCRYPTION BY PASSWORD = '?pkP4SsW0rD!');
 7: GO

4. Create Database Encryption Key:

 1: CREATE DATABASE ENCRYPTION KEY WITH ALGORITHM = AES_256 ENCRYPTION BY SERVER CERTIFICATE SP5Certificate;
 2: 
 3: GO

5. Enable Transparent Data Encryption for a Specific Content Database:

 1: CREATE CERTIFICATE SP5Certificate WITH SUBJECT = SP5Certificate;
 2: go

Please bear in mind:

  • Scripts need to be adapted to your needs, of course
  • Please run everything in a isolated test environment, before applying on production level
  • Consult your DBA before applying any changes to the SQL Server Instance, like running the beforementioned scripts.
  • The author of this blog cannot take responsibility for any damages caused by executing scripts, programs and configurations shown
  • It is your responsibility to inform yourself about possible side effects that are not reported. Usually, Technet and MSDN are good references for complete documentation of the concepts shown.
  • The scripts of SharePointFive are provided “as is”

Stay tuned till the next episode of SharePoint 5 and enjoy!

Best,

Martin

Read Full Post »

Dear all,

 

An error I ran recently across was the following. After creating a new SharePoint Server 2010 web application, I tried to activate the PerformancePoint Site Features. At first sight, everything seemed to be done in the correct order:

 

  • PerformancePoint Service Application running
  • Secure Store Service Application running
  • Connection for PPS and SSS to my web application
  • Site Collection created

 

I went on to my web application, then under:

Site Actions –> Site Settings –> Site Actions –> Manage site features

There I tried to activate the PerformancePoint Services Site Features. Tried. And failed. It failed with the following error messages:

 

image

 

So, the first message gave already a good hint. Off I went for the site collection features:

 

Site Actions –> Site Settings –> Site Collection Administration–> Site Collection Features

 

There, I had to enable both:

  • SharePoint Server Publishing Infrastructure and
  • PerformancePoint Services Site Collection Features

 

That did the trick! Now, returning to the site features, I was able to enable the PerformancePoint Services Site Features, and finally could create also KPIs, Scorecards and Dashboards.

 

image

More options for content creation after PerformancePoint Services have been enabled.

 

I hope this helps some of you with the same problem!

Best regards,

Martin

Read Full Post »

Hi folks,

While working through my current SP2010 lecture, I found an exercise which explained how to set up a document center and how to establish a connection to a web site. The goal of this set up? Simple: When working with a web application and working on documents, at a certain point you may want to have this information centralized. And here comes the document center into play. You can use it as a central access point for your documents without really caring how to upload and complete you document library there. In the end, while working in your web application, the “Send To” context menu of a document should contain an entry for sending the document to the document center. That’s all – simple but effective.

The exercise showed how to create a document center (just create a new site collection and select under “Enterprise” the “Document Center” template). So far, so good. The explanation went further and explained the need of setting up a “Send To” connection  (from the side of the web application). So far, everything made sense. As suggested, in Central Administration I went to “General Application Settings” | “Configure send to connection”. There, I had to choose the web application (http://sp2010:25001), specify a display name, and, most important, define the Send To URL. Which one to choose? I knew the URL of the document center, but this wasn’t verified as a valid URL. A bit of browsing on the internet told me that I should append _vti_bin/officialfile.asmx as a default to the URL.

image

 

After confirming, surprisingly I received the following error message:

 

image

 

Still not valid? Something must have been missing. So back to searching, and finally I could find it. After choosing the document center web application, choosing “Site Actions” | “Site Settings” | “Manage Site Features”, I arrived at the following mask:

 

image

 

There, I needed to activate the Content Organizer Feature – done! Now, one  could expect I needed to verify that the feature was really enabled. Still being in the document center, under “Site Administration”, there was the “Content Organizer Settings” menu entry enabled.

 

image

 

A click on it revealed a mask where different options could be set – but most important: The Web service URL I needed!

 

image

 

A little copy & paste, and the job was done! I hopped back to step 1 and set up the “send to connection” using the now valid URL. It worked.

 

image

 

As you can see in the screen above, in the web application containing the send to connection, the new “Doc Connection Center” is available and ready for use!

 

Stay tuned till the next time!

Best regards,

Martin

Read Full Post »