Nadine's Posts : SharePoint 2013

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