Nadine's Posts

SharePoint 2013 Document Set View is not visible

Nadine Storandt — Tue, 10 Feb 2015 12:45:00 GMT

Hi Guys,

I ran into this problem on one of my customers environment, if you create a document set within a library the DocumentView within Document Set was not visible:

I did a lot of checks and finally ran acroos this blogpost!!

http://www.eliostruyf.com/document-set-view-not-visible-in-sharepoint-2013/

So the first thing i checked was if i get the same java script error like him. To check this enable the Developer Tools within IE (F12) and reload page

and yes i got the same error!

So my conclusion was that something is wrong with the customized masterpage, after we did some checks we saw that the PlaceHolder

PlaceHolderPageTitleInTitleArea was commented out.

After we changed this to: (also please ensure that visibility property of this placeholder is removed. If it is set to false, it is also not working)

It started to work again:

cheers

SharePoint Missing UserPermissions after Upgrade Published Tool on Codeplex

Nadine Storandt — Wed, 28 Jan 2015 10:57:00 GMT

Hi guys,

I want to share a nice tool with you which I has written during my last project. (Its just an console application, might be changed in the future)

https://missingspuserpermission.codeplex.com/

Summary:

This tool can be used in the following scenarios:

- On Upgrade Scenario

- On NTLM to Claims Conversion Scenario

Somehow Sharepoint loose some of the users or AD-groups within the SharePoint groups if you e.g. upgrade your env to a new version or doing a NTLM to Claims Conversion.

In most of the cases the admins do not recognize this as it is only a subset of users who are missing on certain places.

So this tool gives you the ability to document all your user permission from the farm before doing any of the specified actions and later

comparing the results from before and after and add the missing ones back to the sites.

Any Feedback is appreciated! :)

SharePoint 2013 and Visual Studio 2013

Nadine Storandt — Tue, 11 Mar 2014 15:49:00 GMT

Hey guys,

If you are working on a SharePoint 2013 Development machine please consider the following.

If you have already installed SharePoint 2013 and then install Visual Studio 2013, you will get some problems!

If you try to run SharePoint Configuration Wizard, it might will fail with the error message 'Task finalize has failed with an unexpected error' . Neither in the EventLog nor in the ULS log there will be a error message which might be helpfull. But if you try to open e.g. Central Administration -> Upgrade and migration -> Check upgrade status will result in a unexpected error but this time you will find in the ULS log an appropriate error message! In this case something like 'Could not load file or assembly 'Microsoft.Data.Edm, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencie' or any other Microsoft.Data.* related assembly.

Another symptom will be that you can not create new siteCollections or any other stuff related to SharePoint_Config db.

This might be caused by the installation files of Visual Studio 2013!

Resolution:

Install WCF Data Services 5.0 for OData V3
Reboot Machine ( no iisreset)
Run Configuration Wizard again

I'm not 100% sure that everything will work correct in Visual Studio 2013 now but i will keep this post up to date if i get some more information.

SharePoint 2013 Updates and Build Numbers

Nadine Storandt — Tue, 11 Mar 2014 11:00:00 GMT

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 February 2014 Service Pack 1	KB 2817429, 2817439	15.0.4569.1000	25 February 2014
MSS 2013/Foundation December 2013 Cumulative Update	KB 2850024, 2849961	15.0.4551.1511	10 December 2013
MSS 2013/Foundation October 2013 Cumulative Update	KB 2825647, 2825674	15.0.4551.1001	08 October 2013
MSS 2013/Foundation August 2013 Cumulative Update	KB 2817616, 2817517	15.0.4535.1000	13 August 2013
MSS 2013/Foundation June 2013 Cumulative Update	KB 2817414, 2751999,	15.0.4517.1005, 15.0.4517.1003	26 June 2013 11 June 2013
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

SharePoint 2010 Updates and Build Numbers

Nadine Storandt — Wed, 06 Nov 2013 11:00:00 GMT

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 February 2014 Cumulative Update	KB 2863913, 2863938	14.0.7116.5000	11 February 2014
MSS 2010/Foundation December 2013 Cumulative Update	KB 2849971, 2849990	14.0.7113.5000	10 December2013
MSS 2010/Foundation October 2013 Cumulative Update	KB 2825786, 2825824	14.0.7110.500	8 October 2013
MSS 2010/Foundation August 2013 Cumulative Update	KB 2825949, 2825990	14.0.7106.500	13 August 2013
MSS 2010/Foundation Service Pack 2	KB 2687453, 2687464	14.0.7015.1000	01 August 2013
MSS 2010/Foundation June 2013Cumulative Update	KB 2817363, 2817392	14.0.7102.5000	11 June 2013
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 not supported on Windows Server 2012 R2

Nadine Storandt — Mon, 04 Nov 2013 15:23:00 GMT

Hey guys,

currently SharePoint 2013 is not supported for installations on servers running Windows Server 2012 R2.
If you are on such an environment and try to install SharePoint Pre-requisites you get an really annoying error.

"Application Server Role, Web Server (IIS) Role: configuration error"

Even if you have configured everything yourself the error does not disappear. At this point of installation he tries to execute Server Roles configuration via Powershell.

In the Log File of the preparation tool you will see the following lines, the identifier for the problem is the error Code (2).
If this is your case then you have an not supported operating system installed.

There is no workaround for this problem currently, it will be solved with the release of SP1 for SharePoint 2013, but no release date is announced.

cheers

SharePoint Update Hell

Nadine Storandt — Thu, 26 Sep 2013 09:44:00 GMT

Hey guys,

everyone of you who is working with sharepoint have seen the following scenario.

You install a patches on the servers (WFE/APP) and when running the ConfigurationWizard on one of them you will get the following error:

"HotFix xy is missing on WFE1"

If you are really sure that everything has been installed on the farm then try the following commands for solving this error.

So the first thing you can try is to manually start a timerjob which checks and updates the version number on the current server.

1. Open SharePoint Management Shell on the server which makes trouble

2. Run the command Get-SPProduct –local, this will trigger the Timer Job

3. Wait a minute and then try to start the Configuration Wizard again

!!Warning use it on your risk!!

If the above steps do not help here is another workaround which might be helpfull.

1. Open SharePoint Management Shell on the server which makes trouble

2. Run the command psconfig.exe -cmd installcheck –noinstallcheck , this will run the Configuration Wizard without the installcheck.

3. After that try to run the Configuration Wizard in normal mode.

UserGroup WebService with SharePoint 2013 Claims Authentication

Nadine Storandt — Fri, 14 Jun 2013 09:20:00 GMT

Hey guys,

I'm experiencing some issues when working with the UserGroups WebService.

As many of you know SharePoint 2013 recommended to use Claims-Based authentication mechamism, so by default each SharePoint is using this authentication.

(Difference between Claims and Classic)

Each time you add a new user to a group please be aware to use the prefix for claims authentication for the loginName, otherwise SharePoint will add permission for the Windows User account.

And if classic mode is not configured for this site the user won't get access to the site.

Claims-Based Authentication (more infos):

UserGroupProxy.AddUserToGroup(role, displayName, "i:0#.w|" + loginName, email, description);

Windows Authentication:

m_UserGroup.AddUserToGroup(role, displayName, loginName, email, description);

Also if you receive users from a SharePoint site where Claims based authentication is active, the user object will look like the following:

Sid	Name	LoginName	Email	Notes	IsSiteAdmin	IsDomainGroup	Flags
	Admin	i:0#.w\|datest\admin	Admin@daenet.test		True	False	0

As you can see the SId is not filled, if you need to compare the SharePoint user with a NetworkIdentity you need to search the account by DisplayName, Email or LoginName (be aware to cut off the prefix)

greets

nadine

"Sign in as different user" is missing in SharePoint 2013 sites

Nadine Storandt — Fri, 14 Jun 2013 09:15:00 GMT

Hey Guys,

i just want to write it down for myself ;) Because everytime I'm searching for the workaround.

As microsoft already confirmed the Option "Sign in as different user" is missing in SharePoint 2013 sites see KB 2752600.

Here are the workarounds:

1. Start InternetExplorer by using Run as different user <- this option can cause some other problems, so I prefer the second workaround.

2. Access the SharePoint site by using the following url http://yoursite/_layouts/closeconnection.aspx?loginasanotheruser=true

cheers

FileNotFoundException on Create SiteCollection based on Custom Site Definition

Nadine Storandt — Wed, 31 Oct 2012 13:49:00 GMT

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

Nadine Storandt — Mon, 27 Feb 2012 20:00:00 GMT

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

Nadine Storandt — Tue, 31 Jan 2012 18:01:00 GMT

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

Nadine Storandt — Mon, 30 Jan 2012 19:51:00 GMT

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

Nadine Storandt — Tue, 27 Dec 2011 16:06:00 GMT

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

Nadine Storandt — Tue, 27 Dec 2011 15:11:00 GMT

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