Home

Thursday, July 10, 2014

SPS NYC: Reporting and Data Integration Methodologies and Mechanics for SharePoint and SQL Server

Event:
SharePoint Saturday New York
Saturday, July 26, 2014

Session Title:
Reporting and Data Integration Methodologies and Mechanics for SharePoint and SQL Server

Abstract:
First, we’ll review the architecture of SharePoint with SQL Server Reporting Services (SSRS) and SQL Server Integration Services (SSIS) and define the role that the Business Intelligence capabilities play in an organization’s Enterprise Architecture (EA). From there, we will evaluate sample business scenarios and compare and contrast different possible solution approaches. We will design a reporting solution, and then build the solution step by step using SharePoint, SSRS, and SSIS. Finally, we will reflect on the overall approach that we followed and discuss further ideas and possibilities. This session covers high-level concepts as well as practical, hands-on instructions, tips, and tricks.

Slides:
To be posted after event.

Friday, June 06, 2014

SharePoint 2013: A State Service Application Has No Database Defined



Description

After configuring the State Service Application, Central Administration, Monitoring, Health Analyzer, Review Problems and Solutions shows an error; "A State Service Application has no database defined" even though a database does exist.



Solution

I've seen this problem occur when the the State Service Application was configured while logged into the server with an account different from the Farm Account.

1.  Log into the SharePoint Server using the Farm Account.
2.  In Central Administration, Application Management, Service Applications, Manage Service Applications, delete the State Service Application Proxy.
3.  Delete the State Service Application.
4.  Use PowerShell to find the Identity of the State Service Database you would like to remove; Get-SPStateServiceDatabase (Microsoft TechNet, 2012).
5.  Using PowerShell, remove the State Service Application Database; Remove-SPStateServiceDatabase -Identity 00000000-0000-0000-0000-000000000000, replace the zeros with the ID of the State Service Database retrieved from the prior cmdlet.
6.  Using PowerShell, create a new State Service Application.


References

Bisciotti, N. (November, 2012).  SharePoint 2013: How to Configure State Service Application using PowerShell. Retrieved June, 6, 2014 from http://njbblog.blogspot.com/2012/11/sharepoint-2013-how-to-configure-state.html

Microsoft TechNet (July, 2012).  Get-SPStateServiceDatabase.  Retrieved June 6, 2014, from http://technet.microsoft.com/en-us/library/ff608133(v=office.15).aspx

Monday, April 21, 2014

SQL Server Reporting Services, Conditional Formatting Using Switch Function



Description

This post explains how to configure conditional formatting in an SSRS report, for an example that has three conditions.

Solution 

In order to achieve the desired result, we can modify the Background Color property in the SSRS report with a formula, using the Switch function. As described in an MSDN article, "The Switch function returns the value associated with the first expression in a series that evaluates to true" (MSDN, 2012). In the example below we are setting the Variance field Red if the value is less than -100,000, Yellow if the value is between -100,000 and 0, and Green if the value is greater than or equal to 0.



References

MSDN (2012). Expression Examples (Report Builder and SSRS). Retrieved April 21, 2014 from http://msdn.microsoft.com/en-us/library/ms157328.aspx

Thursday, March 27, 2014

SharePoint 2013: How to Configure Visio Graphics Service Application using PowerShell

Last Updated March 28, 2014



Description

This post describes how to configure the SharePoint Server 2013 Visio Graphics Service Application using PowerShell.

Solution

1)  Document the Naming Convention

Determine a naming convention for each of the Visio Graphics Service Application components.  Document the naming convention.

Example:
Application Pool Service Account:  Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPVisioServiceApplication_01 

Service Application Proxy:  SvcApp_SPVisioServiceApplication_01_Proxy_01

2)  Open the SharePoint 2013 Management Shell as Administrator.

3)  Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name

4)  Set the Service Application Pool in a variable.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"

5)  Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPVisioServiceApplication -ApplicationPool $SvcAppPool02 -Name "SvcApp_SPVisioServiceApplication_01"
 
6)  Verify the Service Application.
Get-SPServiceApplication | Select Name

5)  Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPVisioServiceApplicationProxy -ServiceApplication SvcApp_SPVisioServiceApplication_01 -Name "SvcApp_SPVisioServiceApplication_01_Proxy_01"

7)  Verify Service Application Proxy.
Get-SPServiceApplicationProxy | Select Name



References

Microsoft TechNet (February, 2014).  New-SPVisioServiceApplication.  Retrieved March 27, 2014 from http://technet.microsoft.com/en-us/library/ff608096%28v=office.15%29.aspx

Microsoft TechNet (February, 2014).  New-SPVisioServiceApplicationProxy.  Retrieved March 27, 2014 from http://technet.microsoft.com/en-us/library/ff608020%28v=office.15%29.aspx

SharePoint 2013: How to Configure Work Management Service Application using PowerShell

Last Updated March 28, 2014



Description

This post describes how to configure the SharePoint Server 2013 Work Management Service Application using PowerShell.

Solution

1)  Document the Naming Convention

Document a naming convention for each of the Work Management Service Application components. 

Example:
Application Pool Service Account:  Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPWorkManagementServiceApplication_01

2)  Open the SharePoint 2013 Management Shell as Administrator.

3)  Verify the Name of the Application Pool.
PS C:\ Get-SPServiceApplicationPool | Select Name

4)  Set the Service Application Pool in a variable.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"

5)  Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPWorkManagementServiceApplication -ApplicationPool $SvcAppPool02 -Name "SvcApp_SPWorkManagementServiceApplication_01"
 
6)  Verify the Service Application.
PS C:\ Get-SPServiceApplication | Select Name



References

Microsoft TechNet (February, 2014).  New-SPWorkManagementServiceApplication.  Retrieved March 27, 2014 from http://technet.microsoft.com/en-us/library/fp161254%28v=office.15%29.aspx

Monday, March 03, 2014

SPS Boston: Reporting and Data Integration Methodologies and Mechanics for SharePoint and SQL Server

Event:
SharePoint Saturday Boston
Saturday, April 12, 2014

Session Title:
Reporting and Data Integration Methodologies and Mechanics for SharePoint and SQL Server

Abstract:
First, we’ll review the architecture of SharePoint with SQL Server Reporting Services (SSRS) and SQL Server Integration Services (SSIS) and define the role that the Business Intelligence capabilities play in an organization’s Enterprise Architecture (EA). From there, we will evaluate sample business scenarios and compare and contrast different possible solution approaches. We will design a reporting solution, and then build the solution step by step using SharePoint, SSRS, and SSIS. Finally, we will reflect on the overall approach that we followed and discuss further ideas and possibilities. This session covers high-level concepts as well as practical, hands-on instructions, tips, and tricks.

Slides:
Reporting and Data Integration Methodologies and Mechanics SP2013 SQL2012.pdf
Note:  the instructional slides begin at slide #23

SharePoint Server or Project Server Patch Installed Patch Missing



Description

After installing a SharePoint Server or Project Server Service Pack or Cumulative Update, the Configuration Wizard shows that the Patch is missing from servers in the farm.  In this case, the Configuration Wizard on Server 1 is showing that the Project Server 2013 SP1 Patch is missing, yet it was already installed.

Error:  Some farm products and patches were not detected on this or other servers.  If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard.  If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again.




Attempting to run the Project Server 2013 SP1 Patch installation again from the .exe verifies that the Patch is already installed on the system.  Herein lies the problem.  On one hand, the Configuration Wizard will not run because it thinks the patch is missing.  On the other hand, it is not possible to install the patch because it is already installed on local server.  Patch installed, patch missing, patch installed, patch missing.



Solution

The solution to this problem is to run a PowerShell cmdlet on each of the servers that the Configuration Wizard is reporting, patch missing.

1.  Log into the SharePoint Server

2.  Open the SharePoint Management Shell as Administrator

3.  Get-SPProduct -local

This cmdlet retrieves a list of the SharePoint-related products installed in the farm.  It also retrieves the version information for updates installed.  Using the -Local switch retrieves information for local server only.


It may take some time for the cmdlet to run, but once it completes on the servers, you can do a refresh on the Configuration Wizard and the Configuration will recognize that the patches are, in fact, installed on the servers and it will advance automatically to the next screen.  You can continue run the Configuration Wizard upgrade procedure.



References

Microsoft TechNet (May, 2010).  Document farm configuration settings (SharePoint Foundation 2010).  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645390%28v=office.14%29.aspx

Microsoft TechNet (January, 2014).  Document farm configuration settings in SharePoint 2013.  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645391.aspx

Microsoft TechNet (July, 2012).  Get-SPProduct.  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff607885.aspx

Friday, February 14, 2014

SharePoint 2013: How to Increase Shutdown Time Out on Central Administration Application Pool




Description

The Process Model, Shutdown Time Limit setting determines how long a worker process is allowed to stay alive.  The default value is 90 second, however, if a process does not finish in time, it will be shutdown.  In a sluggish environment that does not have adequate RAM, then it is common to see issues when interacting with Central Administration.

For example, when creating a Web Application using Central Administration, the process may only partially complete before it is shutdown, leaving a Web Application in Central Administration, a content database in SQL Server, a Virtual Directory folder in the file system, but no corresponding Web site in IIS.  In this case, you have to delete the Web Application from Central Administration and recreate it.


Solution

If possible, meet the minimum hardware requirements for RAM (Microsoft TechNet, 2014).

Additionally, it is possible to increase the value of the Shutdown Time Limit to allow Central Administration more time to process the types of changes that are prone to timeout in an environment that is resource-challenged.

To make this configuration change, open Internet Information Services (IIS) Manager and then expand the server node and click on Application Pools.



Right-click the SharePoint Central Administration Application Pool and select Advanced Settings.



The default Shutdown Time Limit (seconds) is 90.


 Increase the Shutdown Time Limit (seconds) as you see fit.  The example below shows the setting at 480 seconds.



References

Microsoft TechNet (2014).  Hardware and software requirements for SharePoint 2013.  Retrieved February 14, 2014 from http://technet.microsoft.com/en-us/library/cc262485.aspx



Wednesday, February 12, 2014

SharePoint 2013: Web Application General Settings: Error, Something Went Wrong...



Description

When attempting to modify the Web Application General Settings of a particular Web Application, an error occurs and it is not possible to view the Web Application General Settings page in Central Administration.

Error:  Sorry, something went wrong.  Updates are currently disallowed on GET requests.  To allow updates on a GET, set the 'AllowUnsafeUpdates' property on SPWeb.




Solution

1.  Open the SharePoint Management Shell

2.  Type $WebApp = Get-SPWebApplication http://host.domain.com and press Enter

3.  Type $WebApp.HttpThrottleSettings and press Enter

4.  Type  $WebApp.Update() and Press Enter

5.  Attempt to open the Web Application General Settings from Central Administration.  The page should work at this point.



References

Microsoft TechNet (July, 2012).  Get-SPWebApplication.  Retrieved February 12, 2014 from http://technet.microsoft.com/en-us/library/ff607562.aspx



Blog Archive

Followers