SharePoint 2013 Archive

Errors Running New site collection

Posted May 20, 2014 By Kevin Bennett

I ran into an error running a new site collection on our new Server 2012 SharePoint 2013 Web Farm.

Here is the link to the error and ULS logs: Error in Sharepoint 2013

Although I have yet to figure out what is causing the error I was able to narrow it down to relating to Claims Based Authentication.

I worked around this by removing the Web Application that was using Claims Based and created a Windows Authenticated Web Application. You can not do this via the GUI and need to run a powershell command to complete.

The command I ran was:

New-SPWebApplication -Name -ApplicationPool -AuthenticationMethod -ApplicationPoolAccount -Port -URL

I will update if I ever figure out why Claims is not working. A few things I need to look into are Ports and Permissions, since these are managed by different departments than mine I suspect that used the least privilege/access which might be causing my issues.

Be the first to comment

How I installed SharePoint 2013 on Server 2012 R2

Posted February 28, 2014 By Kevin Bennett

Currently there is Service Pack 1 out for SharePoint 2013 and it can be found here

But as of the writing you still needed to install SharePoint 2013 onto Server 2012 R2 before applying the service pack, which is not support by Microsoft.

Attempting to do so would generate errors related to App Server Role not installing correctly. Below I will show step you through the steps I completed to successfully install SharePoint 2013 onto Server 2012 R2.

In my scenario I wasn’t able to access the internet from the Servers I was installing SharePoint on so I will cover this as an offline install.

1. To install the Roles and Features that are required by SharePoint 2013 on Windows Server 2012 in an offline environment, you must have access to the Windows Server 2012 installation media. You can then run the same Windows PowerShell commands that you used in Method 2, but you must use the -source parameter to specify the location of the required files on the installation media.

For example, assume that you mounted the Windows Server 2012 installation media (ISO) to drive D of the server. Then, the path to provide for the -source parameter is as follows:
Note Be aware that you can also copy the files locally or specify a UNC path where the installation files are stored.
Open an elevated Windows PowerShell prompt on the SharePoint server (that is, Run as Administrator), and execute the following commands:

Import-Module ServerManager
Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45
Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer -Source G:\Sources\sxs
2. Your server may require a restart after you run this Windows PowerShell code.
3. Install the other prerequisites that are required by SharePoint 2013. except App Fabric Setup (See #4) – Found a lot of direct links to download Pre’s here
4. as stated above you will need to run the following in powershell to install the App Fabric software because it requires special settings. In Powershell run .\WindowsServerAppFabricSetup_x64.exe /i CacheClient”,”CachingService”,”CacheAdmin /gac
5. Run App Fab Patch
6. Reboot
7. Run SP 13 Setup
8. Run SP12 SP1

And that will do it.

Good luck.

Be the first to comment

No Sharepoint Tasks

Posted January 9, 2014 By Kevin Bennett

As I have been working for a new agency I haven’t had the opportunity to work with SharePoint very much. Mainly because the Image they have available for Server 2012 is the Image with SP 1 installed. Now I have been able to get approval for and have built a farm out for internal department use of SharePoint I haven’t been able to actually deploy the project because of the incompatibility of SharePoint 2013 with Server 2012 SP 1 .. So as I wait till the SharePoint 2013 Update is published (sometime in first quarter 2014 per MS) I can just sit and twittle my thumbs.

Thank you MS.

Be the first to comment
%d bloggers like this: