Nadine's Posts

SharePoint 2010 Updates and Build Numbers

2013-05-13T15:04:00Z

Hey guys,

I want to share this because I need it so much at customers to find the currently deployed version.

I will keep this post up-to-date ;)

SharePoint 2010 release numbers can be found similarly to how you find them in 2007

just go to Central Admin | System Settings | Manage Servers In Farm. Or, in PowerShell, use: (get-spfarm).buildversion

For more information on SharePoint 2010 updates, please visit http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

SharePoint 2010 Version/Release	Microsoft Support KB Reference	Version Number from Central Admin	Release Date
MSS 2010/Foundation April 2013Cumulative Update	KB 2775353, 2794728	14.0.6137.5000	14 April 2013
MSS 2010/Foundation Februar 2013 Cumulative Update	KB 2767793, 2760791	14.0.6134.5000	12 February 2013
MSS 2010/Foundation December 2012 Cumulative Update	KB 2596955, 2596957	14.0.6131.5003	22 December 2012
MSS 2010/Foundation October 2012 Cumulative Update	KB 2687564, 2687566	14.0.6129.5003	15 November 2012
MSS 2010/Foundation August 2012 Cumulative Update	KB 2687353 , 2687355	14.0.6126.5000	26 August 2012
MSS 2010/Foundation June 2012 Cumulative Update	KB 2598354 , 2598373	14.0.6123.5002	2 July 2012
MSS 2010/Foundation April 2012 Cumulative Update	KB 2598151 , 2598321	14.0.6120.5006	24 April 2012
MSS 2010/Foundation February 2012 Cumulative Update	KB 2597150 , 2597132	14.0.6117.5002	7 March 2012
MSS 2010/Foundation December 2011 Cumulative Update	KB 2597058, 2597014	14.0.6114.5000	22 December 2011
MSS 2010/Foundation October 2011 Cumulative Update	KB 2596508, 2596505	14.0.6112.5000	29 October 2011
MSS 2010/Foundation August 2011 Cumulative Update	KB 2553048, 2553050	14.0.6109.5002	7 September 2011
MSS 2010/Foundation June 2011 Cumulative Update	KB 2536599, 2536601	14.0.6106.5002	30 June 2011
MSS 2010/Foundation Service Pack 1	KB 2460045, 2460058	14.0.6029.1000	28 June 2011
MSS 2010/Foundation April 2011 Cumulative Update	KB 2512800, 2512804	14.0.0.5138	28 April 2011
MSS 2010/Foundation February 2011 Cumulative Update	KB 2475880, 2475878	14.0.0.5136	3 March 2011
MSS 2010/Foundation December 2010 Cumulative Update	KB 2459257, 2459125	14.0.0.5130	31 December 2010
MSS 2010/Foundation October 2010 Cumulative Update	KB 2394320, 2394323	14.0.0.5128	26 October 2010
Foundation July 2010 Hotfix	KB 2032588	14.0.5050.5001	13 July 2010
MSS 2010/Foundation June 2010 Cumulative Update	KB 983319, 983497, 2182938 , 2281364, 2124512, 2204024 - / KB 2028568 / TechNet summary	14.0.0.5114	29 June 2010
SharePoint 2010 RTM	N/A	14.0.0.4762	12 May 2010
SharePoint Server 2010 Release Candidate	N/A	14.0.0.4730	February 2010
SharePoint Server 2010 Public Beta	N/A	14.0.0.4536	November 2009
SharePoint Server 2010 SPC2009 Demos	N/A	14.0.0.4524	October 2009
SharePoint Server 2010 Technical Preview “2” [another SPC2009 demo build]	N/A	14.0.0.4514	October 2009
SharePoint Server 2010 Technical Preview	N/A	14.0.0.4006	25 April 2009

SharePoint 2013 Updates and Build Numbers

2013-05-13T10:46:00Z

Hey guys,

I want to share this because I need it so much at customers to find the currently deployed version.

I will keep this post up-to-date ;)

SharePoint 2013 release numbers can be found similarly to how you find them in 2007 or 2010

just go to Central Admin | System Settings | Manage Servers In Farm. Or, in PowerShell, use: (get-spfarm).buildversion

For more information on SharePoint 2013 updates, please visit http://technet.microsoft.com/en-us/sharepoint/jj891062.aspx

SharePoint 2013 Version/Release	Microsoft Support KB Reference	Version Number from Central Admin	Release Date
MSS 2013/Foundation April 2013 Cumulative Update	KB 2726992, 2751999	15.0.4505.1005 , 15.0.4505.1002	26 April 2013
SPS 2013/Foundation March 2013 Product Update	KB 2767999, 2768000	15.0.4481.1005	12 March 2013
SPS 2013 RTM	N/A	15.0.4420.1017

FileNotFoundException on Create SiteCollection based on Custom Site Definition

2012-10-31T13:49:00Z

Hey guys,

Today i gonna try to renew our SiteDefinition project. First of all i try to save a site collection as template and importing it into Visual Studio.

Importing in Visual Studio was not the problem, but when I redeploy the solution and try to create a new site based on the newly created site definition I got the error

So I gonna take a look at the ULS Log and find the following:

"The system cannot find the file specified. "

"Failed to create list "Variation Labels" in web ... "

So I start researching why this won't work.

Like below shown the Folder "Other imported Files" was missing in the newly imported Site Definition Project.

Here are the steps how I resolve this problem:

Login to the Site Collection as SiteCollection Admin which you want to save as template
Go to SiteSettings
SiteCollectionAdministration
Site Collection Features
Deactivate the Feature "SharePoint Server Publishing Infrastructure"
Reactivate the Feature
In my case I have to try it 2 times to reactivate the feature.

After that I save the site as template, and import it into visual studio and everything has been fine.

I even doesn't know why the hell this has been corrupt, The only thing we have done was to backup the site and restore it on a new WebApplication.

I would be very grateful for any answer why this going to be happened.

Cheers

SharePoint 2010 Powershell Add QuotaTemplates

2012-02-27T20:00:00Z

Hey guys,

here is a little tutorial for getting quotas easily on each environment.

Add first you need to create a new XML Config Files for all values:

Name => this is the displayName which will be shown in Central Admin

StorageMaximumLevel => Gets or sets a limit in bytes on all disk space used by the site collection.

StorageWarningLevel => Gets or sets a storage warning level in bytes for when administrators of the site collection receive advance notice before available storage is expended.

Here is a preview of the Powershell Script the whole Script can be downloaded here

SharePoint Powershell truncated results

2012-01-31T18:01:00Z

Hey guys,

I had a problem everytime I executed the following Powershell command, I received a truncated table as default.

Get-SPWebTemplate

If you don't want the results to be truncated you have to use the following additional command property. (This can be used for every PowerShell command which has an table as output)

Get-SPWebTemplate | format-table -auto

cheers

SharePoint 2010 Bug: The Trial Period for this product has expired

2012-01-30T19:51:00Z

Hey guys,

today i came across this annoying error. I couldn't believe that this has happened.

We only updated the server with Office Web Apps and after running the configuration wizard, each site i try to open failed with the following error message:

I searched the web and found a lot of post's, here are my results:

I'll tried first the official solution from an MS Guy (http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/644ab342-4eaa-468c-95c1-f345a4f65f26/)

Go To Central Administration
Monitoring
Review rule Definition
Search for the rule "Trial period for this product is about to expire"
Disable this rule
iisreset

But this solution was not helpfull in my case, so i tried the other one I found:

Open IIS Management Console
Go to the Application Pool Page
look which users has been used for SharePoint
add this users to the local administration group
iisreset

The second solution helped in my case. If you have other solutions for this Bug please let me know, then i will update this post :)

cheers

nadine

SharePoint 2010 German Link List

2011-12-27T16:06:00Z

Hey guys,

I found a nice site for all people which are interested in SharePoint 2010

http://blogs.msdn.com/b/sharepointalps/archive/2010/02/07/sharepoint-2010-linkliste.aspx

There are links for Technical diagrams, Performance, Permissions, Migration and Installation but the most of them are for german guys.

cheers

SharePoint Deploying custom wsp Solutions easily

2011-12-27T15:11:00Z

Hey guys,

In this post I want you to show the SharePoint Installer projects from CodePlex for 2007 and from Andri Yadi for SharePoint 2010.

These guys are doing a great job!

Solution Installer SharePoint 2007:

Luckily the guys from codeplex provide an excellent basis for deploying custom solutions.

Go to http://sharepointinstaller.codeplex.com/ and download the package. After extraction you should have a folder structure as below:

The only thing which must be changed is the Config file.

Configuration:

Configuration Keys:

BannerImage
Accepts a path to your own banner image. The image is automatically stretched to fit the title bar. Remove or specify empty value to omit banner image.

LogoImage
Accepts a path to your own logo image. Remove or specify empty value to omit banner image.

EULA
Accepts a path to your own EULA file. Remove or specify empty value if you do not want to present an EULA to the user.

SolutionId
Specify the GUID of your solution as indicated in the manifest.xml file within your WSP. The installer will need this to detect any existing solution in the SharePoint solution store.

SolutionFile
Specify the filename of the solution file, e.g. mysolution.wsp. Creating the solution file is of course your job entirely - but I can highly recommend you to take a look at the Visual Studio 2005 Extensions for WSS 3.0

SolutionTitle
The title of your solution. This is displayed on various screens within the installer.

SolutionVersion
Specify the version of your solution. The upgrade option will only show if this version number is different from the previously installed solution.

FeatureScope
Set to "Farm" if the feature in your WSP is scoped to the farm. Set to "Site" if your feature is scoped to a site collection.

This value should be identical to the Scope value specified within your feature XML file within your WSP. Features scoped to the WebApplication or Web are not currently supported.

The installer only supports installing a single feature within your WSP.

FeatureId
Specify the semicolon delimited list of GUIDs of the features as indicated in the feature XML files within your WSP.

The installer will automatically activate these features at the end of the installation process. Specify empty value if the installer should not activate any feature.

UpgradeDescription
Text to display during an upgrade.

RequireDeploymentToCentralAdminWebApplication
Set to true if you want to force deployment of your solution to all central administration web applications.

RequireDeploymentToAllContentWebApplications
Set to true if you want to force deployment of your solution to all content web applications.

DefaultDeployToSRP
Set to true if you want the user deployment to default to all Shared Resource Providers (e.g., SSP, My Sites). The user can change this default in the deployment screen.

RequireMoss
Set to true if your solution requires Microsoft Office SharePoint Server 2007 to install and run. Leave out or set to false if your solution will settle for a WSS only farm.

SSPRelativeConfigLink
Optionally provide a relative link to a configuration page for your feature that is accessible after your farm feature is activated.

This link should be relative to the site where your feature is available (e.g., the SSP URL). This applies only to features scoped to the Farm.

SiteCollectionRelativeConfigLink
Optionally provide a relative link to a configuration page for your feature that is accessible after your Site (site collection) feature is activated.

This link should be relative to any site collection where your feature is available. This applies only to features scoped to the Site (site collection).

DocumentationURL
Optionally provide a complete link to where documentation is available for your feature. This is displayed at the end of installation.

=======================================================================================================

Solution Installer for SharePoint 2010:

Go to the following page http://netindonesia.net/blogs/andriyadi/archive/2010/02/27/sharepoint-2010-solution-installer.aspx and download the packages.

After extraction you should have a folder structure like below:

It's the same like the codePlex project you only need to edit the setup config file.

here is a sample configuration for a Site Feature:

Configuration Keys:

There are only one new Config Key, all others has been used from the old codeplex project, so see the documentation for more infos on this.

RequireSPS:

if this is set to true the installer checks if sharePoint is really installed on the machine.

Note: This setting is currently corrupt because it will check the registry if 2010 is installed with build version 12. So please don't use it!

cheers

Linq To SharePoint Part2 Coding

2011-12-27T14:24:00Z

Hey guys,

this is the second part for Linq To SharePoint, if you have missed the introduction please click here

Getting Started:

Open Visual Studio 2010
Create a new SharePoint Project e.g. EventReceiver
Import your existing Entity Class which has been generated before (Add->Existing Item -> SampleEntities.cs)
Add Microsoft.SharePoint.Linq reference to the project (Reference -> Add -> .Net Component -> Microsoft.SharePoint.Linq)

Now your project should look like the following structure:

Coding:

before you can use Linq functionalities you need to add the following using statements within your eventReceiver class:

Now we can instantiate an object with the generated EntityClass and fetch some data in depending on the where clause.

In this sample I only want to receive the item which has been added and had the Source equal to "Test".

The most cool new thing is intellisense, which you'll never find using CAML Query. Have a look at this:

You can use Linq To SharePoint to fetch, add, update or delete data here are some samples for this:

Update Sample:

Delete Sample:

Add Sample:

Happy Coding :)

cheers

Linq to SharePoint Part1 Introduction

2011-12-27T13:39:00Z

Hey guys,

The best new feature within SharePoint 2010 is in my eyes Linq To SharePoint. It's just incredible because there is no further need for CAML Queries:)

So i want to describe the first use of this feature. If you don't know what is LINQ or how to write LINQ Queries just click here for a quick introduction in msdn.

Getting started:

If you want to use Linq To SharePoint you must have defined your structure for a common SharePoint Site.

In this sample I use a Site which has a CustomLibrary (which has the default columns) and a CustomList (which have some custom Columns defined).

So the first step is to generating the DataEntities for Linq To SharePoint, to do this Microsoft has released a CMD Line Tool named SPMetal.exe

This Tool is located here:

Just open a Command Line and browse to the 14" folder.

Now you can run the tool with the following options:

/web --- Defines the site from which the entities should be used

/namespace --- Defines the namespace which should be used for code generating

/code --- Defines the Name and the Save Location of the Entity Class in depending on the extension (*.cs or *.vb) the code language will be used

There are several more options for this tool here is a short reference from MSDN:

After you execute the command line tool it generates a new Class with all entities which has been found on this site including CustomList with Custom Columns.

Generated Class:

Now we are ready for coding, but how to use this entities i will show in the next post ;)

cheers

Upgrade TFS 2010 to SharePoint Foundation 2010

2011-10-25T08:41:00Z

Hey guys,

here is a short instruction for upgrading TFS 2010 to SharePoint Foundation 2010

back up all the databases. Backup is always the best practice before doing any vital changes.

2. install SQL Server 2008 SP2. SharePoint 2010 requires SQL Server 2008 SP1 and CU2 at least. Now, SP2 is available so I install SP2 directly.

3. run SharePoint install wizard and choose to install prerequisite.

4. run SharePoint install wizard and choose to install SharePoint Foundation 2010, the wizard will automatically detect there is WSS 3.0 existing and it will do the upgrade automatically.

5. run SharePoint foundation 2010 configuration wizard, during the process, it allows you to choose whether to upgrade the theme and layout for the existing site.

6. Upgrade should be successfully.

hope it helps someone!

nadine

SharePoint 2010 Enterprise Features Exposed

2011-02-24T10:22:00Z

Hey guys,

Eric Kraus has a nice post on the various GUID's associated with the Enterprise Feature.

This was very helpful because in some cases when you try to create a new site based on a Template you only get a GUID as error message from SharePoint.

BizTalk: Binding File could not be read or missing Filters

2010-12-02T10:17:00Z

Hey guys,

just for your knowledge, I think this bug is well known.

If you store your binding file within TFS and edit it with Visual Studio manually, e.g. insert placeholder or something else.

Then be aware of this issue, if you are using Filter Actions within a SendPort:

- Open Binding File in Visual Studio:

- This Configuration is looking well:

- If you now copy some new content for the sendPort into the binding file, it will be re-formatted and the filter will look like:

In this case (Carriage return after StartTag and before EndTag <Filter>) BizTalk will throw an error while reading the binding file.

- Also there is another case when the filters will not be displayed (Whitespaces after StartTag and before EndTag <Filter>) and which is not supported by BizTalk, but will not throw an error only the Filters will be missing:

HowTo: using CreateFileBasedResourceManager

2010-10-26T16:55:00Z

Hey guys,

here is a little step by step explanation how to use "CreateFileBasedResourceManager":

- first of all you need to create *.resx file with values

- next step is to generate a *.resources file from the previous generated *.resx file

To generate the *.resources file open command prompt and type resgen yourresource.resx

- Now copy the newly created *.resources file into an unique Directory e.g. C:\Temp\ResourceSet

- Access in C#

- Now you can easily check if the desired errorKey exists in the resource file.

cheers :)

Removing Drop Off Library SharePoint 2010

2010-10-22T10:09:00Z

Hey guys,

if you want to delete a "Drop Off Library" follow the steps below:

1. Download SharePoint Manager from codeplex http://spm.codeplex.com/

2. Extract the files on the SharePoint Server and Start the exe with 'Run as Administrator'

3. Then navigate to the 'Drop Off Library' which you want to delete

4. Select on the Property Page 'Allow Deletion' and set it to TRUE

5. Now go back to the SharePoint portal and the 'Drop Off Library'

6. Select Document Library Settings and now there should be the option 'Delete this Library'

greets

nadine :)