SharePoint 2013

Install SharePoint 2013 on Windows 2012 R2

Last week I did something I thought I’d never do again, install SharePoint 2013 Server. It had been a while and to make things a little more interesting the server was in a data centre with no internet access and no easy way of transferring files across. Here are a few things I learnt that I’m sure will be helpful if you find yourself in the same situation.

Environment:

  • Windows Server 2012 R2
  • SharePoint Server 2013

Problem 1: How do you get the pre-reqs onto the server?

Download the pre-requisite files here and copy them into your install source “Prerequesite” folder (look inside your install source folder structure for this).

Download the prerequisite files for SharePoint 2013 Server

Problem 2: AppFabric install issue

AppFabric wouldn’t install via the prerequisite installer giving error 1603. Lots of digging around suggested the issue was due to .NET but I found the solution was to run the pre-req installer at the command line using the full path:

C:\SP\prerequisiteinstaller.exe /AppFabric:C:\SP\prerequisiteinstallerfiles\WindowsServerAppFabricSetup_x64.exe”

If you get error 1603 you should also check the Local Groups in Computer Management and remove the “AS_Observers” and “AS_Administrators” groups if they exist.

Problem 3: The Prerequisite installer says .NET 4.5 is missing

This is because the SharePoint installer doesn’t recognise the later versions of .NET installed with Windows Server 2012 R2 includes .NET 4.5. Microsoft provides and update for this that replaces a file in the root directory of your install source files.

Download the fix for the .NET 4.5 error

Let me know if you have any other tips that might help someone else who finds themselves installing older versions of SharePoint on newer Windows versions.

Advertisements

Nintex Web Part Maintenance Page error

When applying a custom master page to our SharePoint site, we struck an issue with opening Nintex forms.

Sorry, something went wrong

An unexpected error has occurred.

Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.

 

After a bit of digging around with ULSviewer, we found this error in the SharePoint Log

Application error when access /site/Lists/ourlist/DispForm.aspx, Error=The control collection cannot be modified during DataBind, Init, Load, PreRender or Unload phases.

at System.Web.UI.ControlCollection.Add(Control child) 

at Nintex.Workflow.Forms.ControlTemplates.ListForm.OnInit(EventArgs e) 

at System.Web.UI.Control.InitRecursive(Control namingContainer) 

at System.Web.UI.Control.InitRecursive(Control namingContainer) 

at System.Web.UI.Control.AddedControl(Control control, Int32 index) 

at Microsoft.SharePoint.WebPartPages.ListFormWebPart.CreateChildControls() 

at System.Web.UI.Control.EnsureChildControls() 

at Microsoft.SharePoint.WebPartPages.WebPart.get_WebPartMenu() 

at Microsoft.SharePoint.WebPartPages.ListFormWebPart.CreateWebPartMenu() 

at Microsoft.SharePoint.WebPartPages.ListFormWebPart.OnLoad(EventArgs e) 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

The problem was definitely master page related, because it didn’t occur when we switched back to the default SharePoint master page.

The solution:

In the custom master page, look for the following code.

Move this code block from the Header in to the Body of the master page

<!–MS:<SharePoint:AjaxDelta id=”DeltaSPWebPartManager” runat=”server”>–>
<!–MS:<WebPartPages:SPWebPartManager runat=”server”>–>
<!–ME:</WebPartPages:SPWebPartManager>–>
<!–ME:</SharePoint:AjaxDelta>–>

Try opening the Nintex form again and with any luck your error will go away.

I believe this issue happens because Nintex forms ignore the header part of the master page. Someone with more developer knowledge than me might be able to explain further.

[Updated]

The HTML master page SPWebPartManager position can also be part of the problem. Make sure this is positioned in the <body> section too. I noticed that if this was in the wrong place, it could cause the error above for all users except Site Collection Admins.

See the reference section of this MSDN article for an example of correctly format HTML

How to: Convert an HTML file into a master page in SharePoint 2013

 

SharePoint Double Authentication Issue

I struck and interesting issue on a SharePoint 2013 web application. I had configured the site to allow anonymous access but started getting multiple login prompts when after signing in to the site.

Developer tools in the web browser revealed an access denied error on the URL http://sharepoint.domain.com/_api/contextinfo

The issue was resolved by disabling the “Require Use Remote Interfaces” setting on the web application as follows:

  • In Central Admin \ Web Applications
  • Select the web application
  • Choose Authentication from the ribbon
  • On each zone, remove the tick from “Require Use Remote Interfaces”
  • Click OK

Further details:

The double authentication prompt only occurred on specific activities e.g. editing pages.

In my case this problem occurred after extending a Web Application. In the primary web application I had customised the authentication settings (in IIS). These settings reverted back to defaults after I extended the web application via Central Admin.

SharePoint 2013

SharePoint 2013 “Preview” edition is now available to download.

I have posted an article on my company blog with links to various resources and other items of interest to SharePoint people.

SharePoint 2013 “Preview” – Download and resources

Here’s a couple of screenshots to get you started…

SharePoint 2013 – Home page

SharePoint 2013 – App Store

Overall SharePoint 2013 looks like a good step forward from SharePoint 2010. Microsoft have put a lot of effort into mobility, HTML 5 and cloud functionality.

Microsoft also released a preview of Office 2013. It will be a busy time getting up to speed on all these new things over the next few months. Nice work Microsoft.