Feeds:
Posts
Comments

Archive for the ‘tips’ Category

Dear all,

this is a quick one.

 

The Problem.

Recently I had the problem of not being able to create a page based on a custom master page and page layout. The error shown was:

image

“List does not exist”

“The page you selected contains a list that does not exist”

When clicking on “Site Actions”-> “Create Page”, it simply wouldn’t show the insertion mask for title and URL, but issue the above shown error. The solution for this is easy and quick.

The Solution.

It is quite easy to solve this problem. The authenticated users just don’t have the permissions to read the master page gallery – or in other words: No masterpage access, no new page (which makes sense). Hence, you can go to:

Site Actions –> Site Settings –> Master pages and page layouts –> Settings –> Document library settings –> Permissions

and add there the group NT AUTHORITY\authenticated users (Read, Restricted Read), just like in the screenshot given below:

image

Return to the site or page where you initially wanted to create a page, and you will see it is going to create the page without problems.

 

I hope this was of some help!

Have a good time and stay tuned to the next blog post!

Best regards,

Martin

Read Full Post »

Dear all,

it’s a celebration day: angler.wordpress.com has reached a 50,000 hits!

 

Print

 

It’s about time to say thanks to all of you out there!

Numbers are still increasing, and currently we have about 3,000 views per month on average.

 

We will continue to contribute as much as we can about SharePoint Server!

 

Cheers!

Martin

Read Full Post »

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 again,

I encountered a problem during the installation of the prerequisites of SharePoint 2010 Enterprise. The installation of KB976462 failed, and so would eventually the whole prerequisites installer. The error message pointed me to the log file.

Here is an excerpt from the installation log:

2012-01-11 16:07:21 – Beginning download of Hotfix for Microsoft Windows (KB976462)
2012-01-11 16:07:21 –
http://go.microsoft.com/fwlink/?LinkID=166369
2012-01-11 16:07:23 – Size of download of "Hotfix for Microsoft Windows (KB976462)" in bytes is "4331740"
2012-01-11 16:07:23 – Download of "Hotfix for Microsoft Windows (KB976462)" completed successfully
2012-01-11 16:07:23 – Installing Hotfix for Microsoft Windows (KB976462)
2012-01-11 16:07:23 – "C:\Windows\system32\wusa.exe" "C:\Users\xxx~1\AppData\Local\Temp\KB926A2.tmp.msu" /quiet /norestart
2012-01-11 16:07:26 – Install process returned (-2145124329)
2012-01-11 16:07:26 – [In HRESULT format] (-2145124329)
2012-01-11 16:07:26 – Last return code (-2145124329)
2012-01-11 16:07:26 – Error: The tool was unable to install Hotfix for Microsoft Windows (KB976462).
2012-01-11 16:07:26 – Last return code (-2145124329)
2012-01-11 16:07:26 – Options for further diagnostics: 1. Look up the return code value 2. Download the prerequisite manually and verify size downloaded by the prerequisite installer. 3. Install the prerequisite manually from the given location without any command line options.
2012-01-11 16:07:26 – Cannot retry

So, the solution is quite simple: You must download, extract and install the hotfix manually. The following 3 steps show how it works:

1. Download the KB976462 manually from here:

http://archive.msdn.microsoft.com/KB976462/Release/ProjectReleases.aspx?ReleaseId=4317

image

Choose the “x64” version of the msu file. Save it to a local directory: I used here C:\Installation\KB976462.

2. Open a command prompt and expand the msu file (make sure you open cmd with administrator rights)

expand -f:* "C:\Installation\KB976462\Windows6.1-KB976462-v2-x64.msu" %TEMP%

3. install using:

pkgmgr /n:%TEMP%\Windows6.1-KB976462-v2-x64.xml

 

All done! Re-run the prerequisites installer – it should finish with success, as expected.

 

Hope this was of some help!

Thanks 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 »

Dear all,

the third episode of SharePoint 5 is ready and can be viewed here:

Please note the slight watermark – I am testing another recording software, so in future there will be no more watermark.

This time, we’re dealing with the installation of language packs for

  • Windows Server 2008 (make sure to grab the 64-Bit version of the LPs!)
  • SharePoint Server 2010

Purpose: Creating sites in different languages than only the originally installed SharePoint Server 2010 language.

Here are the links for downloading all the language packs:

 

Windows Server 2008:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=1246

SharePoint 2010 Language Packs: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3411

 

IMPORTANT: Do not execute these steps without prior consulting your administrator and plan for downtime. There will be a service disruption when running the Products Configuration Wizard, where your SharePoint Contents won’t be accessible for some time. Please bear that in mind before executing any of the above mentioned steps.

 

Best regards and stay tuned till the next episode,

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,

while you can plan and organize availability on farm level by configuring Network Load Balancing and also SQL Server database mirroring and failover clustering, you do also have the possibility to plan for high availability on service application level, especially for critical service applications like PerformancePoint. In order to perform this, you must have a failover database server along your normal SQL server.

 

Higher availability for PerformancePoint Services can be achieved by adding additional failover databases to the PerformancePoint Service Application.

 

Go to the Central Administration, choose the row of the PerformancePoint Services Application (don’t click the name, otherwise you’ll “Manage”), and select “Properties” from the ribbon. Just like in Fig. 1

 

image

Fig.1: Open the properties window for the PerformancePoint Service Application

 

Next, in the “Failover Database Server”, insert the name of your failover database server.

image

Fig. 2: Specify the database failover server

After you did this, click “OK” to confirm.

 

Before fully relying on this mechanism, it could make sense to do a test run to verify whether the failover is working at all.

 

Caution: Do not execute the following steps in a production environment, unless you know what you are doing. At all costs, before testing the settings, notify users, schedule downtimes and make sure to do this together with a SQL administrator. Before applying any changes in production, test them in a similar test environment. The following steps assume that you have a working failover cluster for SQL server. If you don’t, DO NOT PROCEED at this point. If you are having only a single instance of SQL server (tested or untested) or a failover cluster that has been untested or is known not to be working, DO NOT EXECUTE the following steps. Otherwise you might lose data and functionality of your SharePoint environment.

 

1. Open a PPS dashboard.

2. Then, shut the principal SQL server instance down (again: Caution! do not do this in a production environment or without experience. You might lose all or partial functionality of SharePoint temporarily). This is the machine that is running Configuration Manager.

3. The failover server should now take over all the workload of the principal server.

4. Refresh the dashboard. It should work fine.

5. Try to modify it to see whether also write operations work on the PPS failover database.

6. Make sure to start again the SQL Server instance and verify that everything is up and working again.

 

The PowerShell approach:

The same result can also be achieved using the following PowerShell cmdlet:

 

Set-SPPerformancePointServiceApplication –Identity <Identity> –DatabaseFailoverServer <Servername>

 

This is very straightforward and increases the availabilty of your PerformancePoint Services.

Upshot: If you have a running SQL Server failover cluster, with little effort you can achieve high availability also for you Business Intelligence data. Not bad, is it?

 

Stay tuned, and till next time!

Martin (still in Calabria)

Read Full Post »

Older Posts »