Extending the Enterprise Content Management Capabilities of Microsoft SharePoint 2010

Microsoft SharePoint has become a key tool in increasing productivity, however many organizations are either still evaluating the product, have purchased it but leave it sitting on the shelf, or have deployed it but not unlocked the full potential of SharePoint in their organizations.

Join us for this special North American tour in which you will learn and see what SharePoint’s true potential can be in your organization. .

Microsoft, K2, KnowledgeLake, AvePoint and NewsGator invite you to a special event focused on learning how SharePoint can improve your organization. Learn about innovative solutions that drive value and cost savings for your organization. Experience product demonstrations, in-depth presentation on SharePoint and how you can extend its capabilities beyond a typical "out-of-the-box" deployment and create real value for your organization. Seating for the event is first come-first serve, so please arrive early and join us for complimentary morning refreshments.

Agenda

  • 8:30 – 9:00 AM – Registration & Breakfast Amenities
  • 9:00 AM – Build Your Business Around SharePoint
  • 9:45 AM – – Intelligent SharePoint Architecture and Optimizing Storage
  • 10:45 AM – Leveraging ECM, Workflow, and SharePoint to build business processes
  • 11:45 AM – Demo: Human Resources Employee On/Off-Boarding & Accounts Payable Process in SharePoint
  • 12:15 AM – Working Lunch
  • 12:30 PM – Leveraging Social Computing in the Enterprise with SharePoint
  • 1:30 PM – Tips & Tricks with SharePoint
    or SharePoint Training & Certification (varies by city)

Register Now

How to Use the Content Query Web Part When Publishing Feature is Disabled

If you want to use the Content by Query Web Part (CQWP), you may have noticed this is only available when you have the Publishing Feature enabled.

If you deal with things like evil site templates, you may not want to enable this feature.  In order to successfully use this webpart without the Publishing Feature follow the following steps:

  1. Save the web part from a site that does have the Publishing Feature enabled
  2. Upload it to your new site
    1. Edit the page
    2. Go to Insert > Web Part and under the categories, you should see "Upload a Web Part"
    3. When you upload a web part, you should see it listed in "Imported We Parts" category.
  3. Once you have done this, the next step is copy the Style%20Library/XSL%20Style%20Sheets/*.xsl files from the site with the Publishing Feature enabled across to the current site
    1. The easiest way to do this is to open the Style Library folder with SharePoint Designer 2010 on the current site, and another copy of SharePoint Designer 2010 open with the Style Library folder from the site with Publishing Feature enabled, and then drag and drop the "XSL Style Sheets" folder from one SharePoint Designer 2010 to the other (ignore the error about needing to be checked out).

This will allow you to be able to add the Content Query Web Part to a page on your site without enabling the Publishing Feature.

April 2012 CU for SharePoint 2007 and 2010 has been released

The product group released the April 2012 Cumulative Update for the SharePoint 2007 and 2010 product family.

The April Cumulative Update for SharePoint 2010 is a Post-SP1 hotfix. That means that you should ensure that SP1 is installed before the April CU.
The April Cumulative Update for SharePoint 2007 is a Post-SP3 hotfix. That means that you should ensure that SP3 is installed before the April CU.

The KB articles for April CU can be found at the following locations (they should be available in a couple of days):

  • KB 2598130 – WSS 3.0
  • KB 2598129 – MOSS 2007
  • KB 2598321 – SharePoint Foundation 2010
  • KB 2598151 – SharePoint Server 2010
  • KB 2598152 – SharePoint Server 2010 with Project Server
    As you see there is a separate Full Server Package for SharePoint Server 2010 with Project Server which simplifies patching of this common installation.

The Full Server Packages for April 2012 CU are available through the following links:

Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU. And the SharePoint Server 2010 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.
That means only one package has to be installed for the SharePoint 2010 product family.

If you need other April 2012 fixes from the Office 2007 and Office 2010 product family have a look at these KB articles:

  • KB 2685445 – Office 2007 April CU
  • KB 2685449 – Office 2010 April CU

Related Update Centers:

SharePoint 2010–BDC Database Response Throttled by Maximum Rows

I was recently working on setting up an external content type to read from a SQL view and ran across this issue.  This error is thrown by SharePoint and will show up in the ULS viewer as one of several messages, the most common is:

Database response throttled. Maximum number of rows that can be read through the database system utility is 2000.

This feature is enabled by default to protect your SharePoint farm from Denial of Service Attacks, either by affecting your farm performance or by affecting the external system’s health due to large transactions.  You cannot make these changes from the farm Central Admin, but you can make them from PowerShell.  However, realize that this change happens at the service application proxy level, meaning that it’s all or nothing for the farm unless you’ve gone through the hassle of creating unique proxies for each tenant and associated those proxies to their web application.

Once you have the handle on the Proxy and the Rule, you can see what rules are set by typing $dbRule in the shell.

Here is the cut and paste for changing the limits:

$bdcProxy = Get-SPServiceApplicationProxy | where {$_.GetType().FullName -eq (‘Microsoft.SharePoint.BusinessData.SharedService.’ + ‘BdcServiceApplicationProxy’)}
$dbRule = Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottleType Items -ServiceApplicationProxy $bdcProxy
Set-SPBusinessDataCatalogThrottleConfig -Identity $dbRule -Maximum 10000 -Default 10000

And here are the fun things you can do and various rules can you set.  There are four ThrottleTypes and five Scopes:

ThrottleType

Meaning

Items

The number of records returned

Size

The amount of data returned, in bytes

Connections

The number of connections opened to the database, web service, or .NET assembly

Timeout

The time until an open connection is terminated, in milliseconds

Scope

Meaning

Global

Applies to Database, Web Service, WCF, and .NET Assembly Connectors (not to Custom Connectors)

Database

Applies to Database Connectors

WebService

Applies to Web Service Connectors

Wcf

Applies to WCF Connectors

Custom

Applies to Custom Connectors

Here’s a table of the rules that exist:

Global

Database

WebService

Wcf

Items

X

 

Size

X

X

Connections

X

     

Timeout

X

X

 

More information about the cmdlets can be found here:

Get-SPBusinessDataCatalogThrottleConfig

Set-SPBusinessDataCatalogThrottleConfig