Category Archives: Administration

Behold the new SharePoint Splash screen

With the new version of SharePoint 2013 that was released on MSDN last week as you can read here SharePoint 2013 has a new Installation screen to give power to the new Interface of SharePoint 2013.

Today I will start a new fresh installation of a development machine with the following specifications:

Microsoft Office 2013 Professional.
Microsoft Office Visio 2013.
Microsoft Office Project 2013.
Visual Studio 2012.
Windows Server 2012.
SQL Server 2012.

Every interesting thing I will discover will be posted on this blog, so stay tuned!

SharePoint 2013 Databases without the GUID

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part VI – Configuring SharePoint 2013 on Windows Server 2012 RC

2 Replies

Last week we finished the installation of SharePoint 2013. For us to test the new version off SharePoint we still have to do some configuration.

The first thing we will do is creating a couple of service accounts that we will use to create Service Application and Web Applications.

Open Active Directory Users or Computer by doing the following:

Go to the Start Menu by using the Windows button or by going to the low left corner with your mouse.
With the Start Menu open select “Active Directory Users and Computers”.

Open the Users OU and use your other mouse button to add a new user. When you have the “New Object – User” window open create the following user.

First name	Last name	User Logon name	User logon name
SharePoint	Application Pool	svc_spapppool	svc_spapppool
SharePoint	Services	svc_spservices	svc_spservices
SharePoint	Search	svc_spsearch	svc_spsearch
SharePoint	Content Access	spcontentaccess	spcontentaccess

Make sure you select the options, for all of the accounts:

User cannot change password.
Password never expires.

For us to create a new site we will also have to register a url within the DNS (You can also do this within your host file). To alter the DNS configuration do the following:

Go to the Start Menu by using the Windows button or by going to the low left corner with your mouse.
With the Start Menu open select “DNS”.

Select the forward lookup zone of your domain and add a new A Host record. For this machine I chose the following domain: sp2013.dev.local.

For us to access this URL this machine we will also have to disable the LoopBackCheck, this is because Windows Server 2012 also had the same security enabled as Windows Server 2008 R2. To disable the LoopBackCheck check this blog post:

http://msftplayground.com/2009/04/access-denied-while-crawling-sites/

Now that we have done these configurations we can start with the last configuration steps off SharePoint. First off we will create some managed accounts:

Create Managed Accounts

To create managed accounts follow the following steps:

Open “Central Administration”
Go to the Security section.
Select “Configure Managed Accounts” under “General Security”.
Then add managed accounts for all the accounts we created in the AD besides the spcontentaccess account.

With the managed accounts in place it is time to create our web application.

Create Web Application

To create a new web application follow these steps:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage web applications”.
On the toolbar select “New” within the toolbar.
Create the web application with the following information.

Setting	Value
IIS Web Site	Create a new IIS web site. Name: SharePont – SP2013 Port:80 Host Header: sp2013.dev.local Path: Keep the default value
Security Configuration	Allow Anonymous:false Use Secure Sockets Layer(SSL): false
Claims Authentication Type	Integrated Windows Authentication: NTLM
Sign In Page Url	Default Sign In Page
Public Url	URL: http://sp2013.dev.local:80 Zone: Default
Application Pool	Create new application pool: Name: SharePoint Web Application Configurable: DEV\sp_spapppool
Database Name and Authentication	Database Server: SQL2012_SP Database Name: WSS_Content_2013 Windows Authentication
Service Application Connections	Default

Press ‘Ok’ to create the web application.

When the web application is created we will define some managed paths to create site collections.

Define Managed Paths

With “Central Administration” opened go to the “Application Management” section.
Select “Manage web applications”.
Select the web application for which you want to define the managed paths.
On the toolbar select “Managed Paths” within the toolbar.
In the Define Managed Paths window add the following Managed Paths:

Path	Type
personal	Explicit
hub	Explicit
content	Explicit

With the Managed Paths in place it is time to create a few site collections.

Create Site Collections

First off we will create a MySite host site collection. To start creating site collections follow these steps:

With “Central Administration” opened go to the “Application Management” section.
Select “Create Site Collections”
Make the site collection with the following information:

Setting	Value
Web Application	Make sure the right web application is selected
Title and Description	Title: SP2013 MySite Description: MySite Host
Web Site Address	Url: http://sp2013.dev.local/personal
Template Selection	Enterprise – My Site Host
Site Collection Administrators	Choose the users you want to administrator the site collection. For this machine we will use dev\spadmin

Creating a site collection with these settings will create a my site host. We will also create a Team site and a Hub site.

Settings for the Hub site

Setting	Value
Web Application	Make sure the right web application is selected
Title and Description	Title: SP2013 Hub Description: Hub Host
Web Site Address	Url: http://sp2013.dev.local/hub
Template Selection	Enterprise – My Site Host
Site Collection Administrators	Choose the users you want to administrator the site collection. For this machine we will use dev\spadmin

Settings for the Team site

Setting	Value
Web Application	Make sure the right web application is selected
Title and Description	Title: SP2013 Description: Team site
Web Site Address	Url: http://sp2013.dev.local/
Template Selection	Enterprise – My Site Host
Site Collection Administrators	Choose the users you want to administrator the site collection. For this machine we will use dev\spadmin

With the site collections in place we can start creating the several Service Applications.

Create User Profile Service Application

To create a User Profile Service Application follow the following steps:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “User Profile Service Application”
Create the Application with the following settings.

Setting	Value
Name	User Profile Service Application
Application Pool	Create new application pool: Application pool name: SharePoint Service Application Pool Configurable: DEV\svc_spservices
Synchronization Database	Database Server: SQL2012_SP Database Name: Sync_DB
Profile Database	Database Server: SQL2012_SP Database Name: Profile_DB
Social Tagging Database	Database Server: SQL2012_SP Database Name: Social_DB
Profile Synchronization Instance	DEV_BETA
My Site Host Url	http://sp2013.dev.local/personal
My Site Managed Paths	/content
Site Naming Format	User name

Create Managed Metadata service Application

The following service application we will be creating is the Managed Metadata Service Application.

Follow these steps:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “Managed Metadata service application”
Create the Application with the following settings.

Setting	Value
Name	Managed Metadata Service
Database	Database Server: SQL2012_SP Database Name: SharePoint_Managed_Metadata
Application Pool	Use existing application pool: Application pool name: SharePoint Service Application Pool
Content Type Hub	http://sp2013.dev.local/hub Select, Report Syndication import errors from site collections using this service application.

Create App Management Service Application

Next up is a new service application called “App Management Service Application”. This service application will give you the ability to manage the new App solutions that are build into SharePoint 2013.

Follow these steps to create this service application:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “App Management Service”
Create the Application with the following settings.

Setting	Value
Name	App Management Service Application
Database	Database Server: SQL2012_SP Database Name: App_Managed_DB
Application Pool	Use existing application pool: Application pool name: SharePoint Service Application Pool
Create App Management Service Application Proxy	Select, create App Management Service Application Proxy and add it to the default proxy group.

Create Business Data Connectivity Service Application

A service application that was also in SharePoint 2010 is the BDC Application.

Follow these steps to create it:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “Business Data Connectivity Service Application”
Create the Application with the following settings.

Setting	Value
Name	Business Data Connectivity Service Application
Database	Database Server: SQL2012_SP Database Name: BDC_Service_DB
Application Pool	Use existing application pool: Application pool name: SharePoint Service Application Pool

When I was creating this service application I received multiple errors. Even when I retried to create at went wrong with the same errors. When I checked the application everything looked fine and seem to be working correctly.

Create Machine Translation Service Application

Another new Service Application is the Machine Translation Service Application. This application give you the option to translate all kind off documents. The texts that are in the documents will be translated by the online Bing translation services.

To create this application use the following steps:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “Machine Translation Service Application”
Create the Application with the following settings.

Setting	Value
Name	Machine Translation Service Application
Application Pool	Use existing application pool: Application pool name: SharePoint Service Application Pool
Partition mode	Don’t select this option.
Add to default proxy list	Select this option to add it to the default proxy list.
Database	Database Server: SQL2012_SP Database Name: Machine_Translation_Service_DB

Create Search Service Application

The Search Service Application is the next service application we will create. There changed a couple off small things to the search service application but creating is still the same.

Follow these steps:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “Search Service Application”
Create the Application with the following settings.

Setting	Value
Name	Search Service Application
Search Service Account	DEV\svc_spsearch
Application Pool for Search Admin Web Service	Create New Application Pool. Application pool name: SharePoint – Admin Search Service. Configurable: DEV\svc_spsearch
Application Pool for Search Query & Site Settings Web Service	Create New Application Pool. Application pool name: SharePoint – Query and Site Settings Pool. Configurable: DEV\svc_spsearch

Create Secure Store Service

We will also create a Secure Store Service for when we would like to test connections to other systems like CRM.

Follow these steps to create the application:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “Secure Store Service Application”
Create the Application with the following settings.

Setting	Value
Name	Secure Store Service Application
Database	Database Server: SQL2012_SP Database Name: Secure_Store_Service_DB
Application Pool	Use existing application pool: Application pool name: SharePoint Service Application Pool
Enable audit	Enable the audit log and set the days until purge to 30.

Create Work Management Service

The work management service is the last service application we will create trough the UI. This is also one off the new service applications. The work management service application will give users the ability to edit and change there tasks on one single place within the SharePoint farm. This service will take care of changing values on other places and aggregating the tasks. One off the great things it is also possible to synchronize exchange tasks!!!

To create the Work Management Service follow these steps:

With “Central Administration” opened go to the “Application Management” section.
Select “Manage Service Applications”.
On the toolbar select “New” and select “Work management Service Application”
Create the Application with the following settings.

Setting	Value
Name	Work Management Service Application
Application Pool	Use existing application pool: Application pool name: SharePoint Service Application Pool
Service Application Proxy	Select create proxy for this service application.

This were all off the service application we will create trough the UI will will have to create the State Service Application with PowerShell.

Create State Service application with PowerShell

Run the “SharePoint 2013 Management Shell” as Administrator.
Type: “New-SPStateServiceApplication”
Next enter the name for the service application “Name : State Service Application”

With all the Service applications in place we will perform a IISReset make sure that all settings are refreshed.

After the IISReset we can start the service by going to the following screen:

Open “Central Administration”
Select “Application Management”
Then select “Manage services on server”

With the Services screen open start the following services:

App Management Service
Business Data Connectivity Service
Claims to Windows Token Service
Machine Translation Service
Managed Metadata Web Service
Request Management
Secure Store Service
User Profile Service
Work Management Service

When these services are started we will make the farm account (svc_spfarm) local administrator. This is because off the same problem with SharePoint 2010.

To make the svc_spfarm account local administrator do the following:

Open Active Directory Users or Computer by doing the following:

Go to the Start Menu by using the Windows button or by going to the low left corner with your mouse.
With the Start Menu open select “Active Directory Users and Computers”.
With Active Directory Users and Computers open open the domain and select the Builtin OU.
Within the Builtin OU find the administrators group and add the farm account to it.

Perform a reset off your VM to reset the security of the farm account. Then go back the “Manage services on server” and start the “User Profile Synchronization Service”.

When you will start this service you will have to connect it to a Service Application. Connect it to the User Profile Service application we created above.

With all these service applications and web applications in place you have a great environment to start testing SharePoint 2013. If you have any further question just leave a comment and I will get back to you!!

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part V – Installation of SharePoint 2013 on Windows Server 2012 RC

4 Replies

Now that the prerequisites are done it is time to start the installation of SharePoint 2013. First off we will have to some configuration changes.

The first thing we will do is creating a farm account to run Central Administration and the farm services.

Open Active Directory Users or Computer by doing the following:

Go to the Start Menu by using the Windows button or by going to the low left corner with your mouse.
With the Start Menu open select “Active Directory Users and Computers”.

Open the Users OU and use your other mouse button to add a new user. When you have the “New Object – User” window open create the following user.

First name	Last name	User Logon name	User logon name
SharePoint	Farm	svc_spfarm	svc_spfarm

Make sure you select the options:

User cannot change password.
Password never expires.

Next up is the configuration of a SQL Alias. We will create a SQL alias to be able to migrate the SQL Databases to another Virtual machine if we want.

Go to the Start Menu by using the Windows button or by going to the low left corner with your mouse.
With the Start Menu open use your other mouse button and select “All apps”.
Open “Command Prompt” and type in cliconfg.
Within SQL Server Client Network Utility go to the Alias tab and click add.
Type in a Alias Name (SQL2012_SP) and fill in the server name of the server that host SQL in our case it will be the local machine.
Also select the following Network library type : TCP/IP.
Select “Ok” to add the alias and select “Apply” and “Ok” to close the configuration wizard.

With these configuration steps done it is time to mount the image and start the setup of SharePoint 2013.

During the first step of the installation you will have to insert you product key. I received my product key to mail. Fill it in and press “Continue”.

Accept the license terms and select “Continue” again.

The next screen will give you the option to change the file location. For this machine we will leave it to default and start the installation.

When the installation is finished the “Run the Configuration Wizard” screen will open. Leave the check box checked and click “Close”.

The configuration wizard will be opened. On the welcome screen click “Next”.

When you click next the same warning screen will appear as it did with SharePoint 2010 since this is a new installation we can ignore this message and click “Ok”. The next step gives you the option to connect to an existing farm or to create a new server farm. Since this is a new installation we will select “create a new server farm”.

In the next step we will to specify the SharePoint SQL server and the name for the configuration database. We also need to specify the Database access account.

Fill in the following information:

Database server: SQL2012_SP (This is the alias we created)

Database name: SharePoint_Config

Username: dev\svc_spfarm

Password: *********

On the next step we need to specify the passphrase we want to use when we want to add another server to the farm. Use a a known password that you will remember and click next.

The next step in the wizard will allow you to configure Central Administration. Use a port number u find handy and select NTLM authentication for this demo machine.

A summery of the configuration will follow. Check all of the settings and click on “Next” to start the configuration.

When the configuration is finished the successful window will be shown. Click finish to close the wizard, automatically a explorer window will be opened that opens Central Administration. With a model dialog asking if you want to help improve SharePoint. Select “Yes, I am willing to participate” and click “Ok”.

When the model dialog is closed you will get the option to start the configuration wizard to configure the farm. Select the option “No, I will configure everything myself”.

The Central Administration home screen will be opened.

In the next post we will start the configuration of the different SharePoint 2013 Services.

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part III – Installation of SQL Server 2012 on Windows Server 2012 RC

1 Reply

With the new version of SharePoint almost in Public Beta (I have hopes it will be this month) it is time to show how you can install it on the Release Candidate of Windows Server 2012.

Since the new version of SharePoint isn’t there yet this series of blog post will continue with the Installation of SQL Server 2012 on Windows Serve 2012 RC. After this post the following post will follow:

Part IV – Installation of the Prerequisites on Windows Server 2012 RC
Part V – Installation of SharePoint 2013 on Windows Server 2012 RC
Part VI – Configuring SharePoint 2013 on Windows Server 2012 RC

So let us begin with booting up the Virtual Machine we got this far and add the ISO of SQL Server 2012 to the machine.

When continuing from the previous blog post the “Server Manager” will be opened. Close the Server Manager and open “Active Directory Users and Computers” to create the service accounts we need for the installation of SQL Server:

To open Active Directory Users or Computer do the following:

Go to the Start Menu by using the Windows button or by going to the low left corner with your mouse.
With the Start Menu open select “Active Directory Users and Computers”.

Open the Users OU and use your other mouse button to add users:

When you have the “New Object – User” window open create the following users:

First name	Last name	User Logon name	User logon name
SQL	DB Engine	svc_sqldbengine	svc_sqldbengine
SQL	Reporting	svc_sqlreporting	svc_sqlreporting
SQL	Agent	svc_sqlagent	svc_sqlagent

Make sure you select the options:

User cannot change password.
Password never expires.

This will make sure the password of the accounts will not be reset or be disabled.

When the accounts are created it is time to start the installation of SQL server. Run the Setup wizard that’s on the SQL Server 2012 CD / DVD.

When you run the setup the SQL Server Installation Center will open. Press the Installation option on the left and then select “New SQL Server stand-alone installation or add feature to an existing installation”.

The installation setup will start with running a few startup rules. When you have passed all of the rules click Ok to continue with the installation.

A new window will open and ask for your product key. If your product key hasn’t been filled in yet fill it in and continue by clicking next. On the next step accept the license terms and click next again.

The wizard will now start installing the required files for the installation and will start up another wizard. This wizard will automatically check the conditions of the server.

Most of the the the wizard will give two warnings:

Computer domain controller: You can ignore this warning because we will use this pc as a development pc. For production servers never install SQL on a domain controller this is for security reasons.
Windows Firewall: This warning states that the Firewall is blocking SQL server. Because the machine will be a one machine farm we can ignore this warning. When you are creating a farm with multiple pc’s you will have to open the SQL server port. By default this is: 1433.

Because we can ignore the warnings we will click next and proceed to the next step. The next step will give us the option to select the installation type. You will have three options:

SQL Server Feature Installation: This option will give you the possibility to install specific features of SQL Server.
SQL Server PowerPivot for SharePoint: This option will give you the possibility to install PowerPivot for SharePoint.
All Features with Defaults.

We will select the first option: “SQL Server Feature Installation” because we want to install SQL server and select the features we want. We do not want to install everything because this can downgrade the performance of our virtual machine.

In the next step we can select the features we want to install. We will select the following features:

Database Engine Services.
- SQL Server Replication
- Full-Text and Semantic Extractions for Search
- Data Quality Services
Management Tools – Basic
- Management Tools – Complete

At the moment we will not install “Reporting Services Add-in for SharePoint Products” because we do not have a instance running of SharePoint server. Click next to continue with the installation.

The wizard will perform a couple of checks based on the features you have selected. If you pass all of the Rules click next to continue to the Instance Configuration. On the instance configuration screen you have the option to change the name of the SQL Server Instance. We will keep the default settings and click “next” to continue.

The Disk Space Requirements Step will show you if you have enough hard drive space to install SQL server if you pass this step click next to continue. This will bring us to the “Server Configuration” step. In this step we will have to fill in the accounts and passwords for the services.

Fill in the accounts that we have created in the first step:

Service	Account Name
SQL Server Agent	svc_sqlagent
SQL Server Database Engine	svc_sqldbengine

When you proceed you will have the option to select the authentication mode off SQL Server and were the data files are saved. For now we will leave it to the default settings and we will only fill in the SQL Server Administrators. I always fill in the BUILTIN\Administrators group but because were are installing it on a domain controller it cannot find this group that’s why we will just add the current user.

Now that we have configured these last steps we are almost finished with the installation. The next step can be ignored and you can simple click next. The wizard will again check a few rules, when you pass these rules click next to go to the confirmation screen.

In the confirmation window check every setting and click “Install” to start the installation.

When the installation is complete you can close the wizard. You can then op SQL Server management studio by following these steps:

Go to the Start Menu by using the Windows button or by going to the low left corner with your mouse.
With the Start Menu open select “SQL Server Management Studio”.

With SQL Server installed we can start the Installation of SharePoint 2013. We will start this fourth part of the blog series when the SharePoint 2013 Public Beta is released.

Do not start Server Manager automatically at Logon – Windows Server 2012

3 Replies

After the installation of the new Windows Server version (Windows Server 2012 RC) it was annoying for me that the “Server Manager” started every time when I logged in to the machine.

In Windows Server 2008 R2 you could disable the auto start option from the home screen. I started searching for the option but couldn’t find it. After half an hour I found the solution:

Open the “Server Manager”.
Select “Manage” on the top bar.
Select “Server Manager Properties” from the drop down menu.
Select the option “Do not start Server Manager automatically at logon”.

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part I – Installation of Windows Server 2012 RC

2 Replies

With the new version of SharePoint almost in Public Beta (I have hopes it will be this month) it is time to show you how you can install it on the new Release Candidate of Windows Server 2012.

Since the new version of SharePoint isn’t there yet this series of blog post will begin with installing Windows Server 2012 RC on a Virtual Machine. After this post the following post will follow:

Part II – Installation of Active Directory and DNS Services on Windows Server 2012 RC
Part III – Installation of SQL Server 2012 on Windows Server 2012 RC
Part IV – Installation of the Prerequisites on Windows Server 2012 RC
Part V – Installation of SharePoint 2013 on Windows Server 2012 RC
Part VI – Configuring SharePoint 2013 on Windows Server 2012 RC

So let us begin with the installation of Windows Server 2012 RC. First off make sure you have a ISO available of Windows Server 2012 RC. If you don not have the image already download it from the Microsoft site:

http://www.microsoft.com/en-us/server-cloud/windows-server/2012-default.aspx

When you have downloaded the image you can create a new virtual machine and assign a appropriate amount of memory. I have created my VM with 6 GB of memory.

Attach the image file to the virtual machine and then boot it. It will automatically boot the installation wizard of Windows Server 2012 with the language selection screen.

With the right language selected click ‘Next’ to proceed to the next step. The next step is easiest step of the installation. You only have to press the button “Install now”.

When “Install now” is pressed the installation medium will load the actual setup files. In the mean time it will show you a dark blue screen with the waiting mouse cursor and the text “Setup is Starting”.

When all the files are loaded it is time to begin the actual setup of Windows. Basically the complete setup really look like the installation of Windows Server 2008 R2 so I think you can guess what is coming next.

Yep…. It is the Operating System selection screen. The only version available at the moment is the Windows Server 2012 Release Candidate Datacenter edition. You still have to take a good look because the installation disc also has the Server Core Installation. Choose the “ Server with a GUI” option and click next. Accept the license and again click next to go to the installation type screen.

Like the installation of Windows 7 and Windows Server 2008 R2 you have the option to upgrade your current Operation System. Since this is a complete new installation we choose for “Custom: Install Windows Only (Advanced)”.

In the next screen you will be asked to select the disk you would like to use for your installation. Select the right disk and click on “Next” .

After you selected the disk Windows will start installing the files to the specified disk.

When the installation is done the server will reboot and starts preparing Windows. Just like the old version you then will be asked to give in your Administrator password.

When you click the “Finish” the setup will finalize. After the finalization you will see the new ctrl+alt+delete screen.

Press ctrl+alt+delete and login to the server the desktop will be loaded and you are ready to start installing new windows component with the new Server Manager.

Like described at the top of the post this is the first post in a series of 6 posts. In the next post I will show you how to install the Active Directory component and the DNS component on Windows Server 2012 RC.

Windows PowerShell command builder

System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.

1 Reply

For one of our clients we are working with a claims based web application. This web application has a custom membership provider that is registered at the web application, central administration and security token service level.

When we navigate to the site everything works perfectly but when we try to login with valid credentials we would receive an error like below:

Server Error in ‘/’ Application.

Runtime Error Description: An application error occurred on the server. The current custom error

The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.]
   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response) +1161205
   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) +73
   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst) +36
   Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo) +26405809
   Microsoft.SharePoint.SPSecurityContext.SecurityTokenForFormsAuthentication(Uri context, String membershipProviderName, String roleProviderName, String username, String password) +26406316
   Microsoft.SharePoint.IdentityModel.Pages.FormsSignInPage.GetSecurityToken(Login formsSignInControl) +188
   Microsoft.SharePoint.IdentityModel.Pages.FormsSignInPage.AuthenticateEventHandler(Object sender, AuthenticateEventArgs formAuthenticateEvent) +123
   System.Web.UI.WebControls.Login.AttemptLogin() +152
   System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +124
   System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +70
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +29
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2981

In our situation this error occurs within in the “Security Token Service Application”. The problem with this error message is that it isn’t the exact message of what is going wrong. To receive that error message that is occurring do the following:

Open IIS and navigate to “SharePoint Web Services” under “Sites”. Click the node open and select “SecurityTokenServiceApplication” use your other mouse button to open the context menu and select “Explore”.
Windows explorer will open a new window. In this window you will see a web.config file. Open this file within a text editor and look for the following section:

<behaviors>
  <serviceBehaviors>
    <behavior name="SecurityTokenServiceBehavior">
      <!-- The serviceMetadata behavior allows one to enable metadata (endpoints, bindings, services) publishing.
           This configuration enables publishing of such data over HTTP GET.
           This does not include metadata about the STS itself such as Claim Types, Keys and other elements to establish a trust.
      -->
      <serviceMetadata httpGetEnabled="true" />
      <!-- Default WCF throttling limits are too low -->
      <serviceThrottling maxConcurrentCalls="65536" maxConcurrentSessions="65536" maxConcurrentInstances="65536" />         
    </behavior>
  </serviceBehaviors>
</behaviors>

In this section we will place a extra debug tag to include the errors that are occurring. The tag looks like this:

<serviceDebug httpHelpPageEnabled="true" includeExceptionDetailInFaults="true" />

This tag needs to be placed in the behavior tag. After you place the tag in the section it will look like this:

<behaviors>
  <serviceBehaviors>
    <behavior name="SecurityTokenServiceBehavior">
      <!-- The serviceMetadata behavior allows one to enable metadata (endpoints, bindings, services) publishing.
           This configuration enables publishing of such data over HTTP GET.
           This does not include metadata about the STS itself such as Claim Types, Keys and other elements to establish a trust.
      -->
      <serviceMetadata httpGetEnabled="true" />
      <!-- Default WCF throttling limits are too low -->
      <serviceThrottling maxConcurrentCalls="65536" maxConcurrentSessions="65536" maxConcurrentInstances="65536" />
      <serviceDebug httpHelpPageEnabled="true" includeExceptionDetailInFaults="true" />
    </behavior>
  </serviceBehaviors>
</behaviors>

After changing the “web.config” we received the correct message and we saw that we mistyped the role provider name.

Server Error in ‘/’ Application.

Cannot get Role Manager with name Empty. The role manager for this process was not properly configured. You must configure the role manager in the .config file for every SharePoint process.

Slow file transfer from Windows Explorer view to another Windows Explorer view of SharePoint.

Microsoft Playground

debug.write("Microsoft Playground");

Category Archives: Administration

Behold the new SharePoint Splash screen

SharePoint 2013 Databases without the GUID

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part VI – Configuring SharePoint 2013 on Windows Server 2012 RC

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part V – Installation of SharePoint 2013 on Windows Server 2012 RC

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part III – Installation of SQL Server 2012 on Windows Server 2012 RC

Do not start Server Manager automatically at Logon – Windows Server 2012

Install SharePoint 2013 Public Beta on Windows Server 2012 RC – Part I – Installation of Windows Server 2012 RC

Windows PowerShell command builder

System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.

Slow file transfer from Windows Explorer view to another Windows Explorer view of SharePoint.