SharePoint Server 2013 known issues

Yammer App for SharePoint: App part doesn’t render and gives an iFrame error in Internet Explorer

Because the Service Manager component in Office programs automatically adds SharePoint tenant domains to Trusted Sites security zone in Internet Explorer whenever you open a document from a SharePoint site, you get an IFrame error. The login endpoint isn’t added to Trusted Sites. The user authentication to SharePoint still succeeds, but the iFrame itself isn’t rendered as it’s blocked by click jacking protection.

Workaround    Add following sites into your Trusted Sites list and restart the session.

• https://login.microsoftonline.com
• https://*.sharepoint.com

If adding these sites doesn’t solve the problem, please turn on Protected Mode for Trusted sites.

Yammer App for SharePoint: Blank dialog box pops-up on login when using Internet Explorer

Having *.yammer.com and *.sharepoint.com (like your SharePoint domain) in the Intranet Zone setting in Internet Explorer prevents you from logging into the Yammer from the Yammer App for SharePoint. You’ll see a blank dialog box after logging into Yammer from the app.

Workaround    Add following sites into your Trusted Sites list and restart the session.

• https://*.yammer.com
• https://*.assets-yammer.com

Context menus might not be available for PerformancePoint content on mobile devices

If your organization is using SharePoint Server 2013 running in SharePoint Server 2010 mode, context menus for PerformancePoint content might not be available when viewed on a mobile device such as a Windows 8 tablet or an Apple iPad. This is especially true when users are viewing content using the Internet Explorer app as opposed to running Internet Explorer from the Windows 8 desktop or when using the iOS 6 Safari browser on Apple iPad.

Workaround    We recommend running SharePoint Server 2013 in its default mode. Or have people open Internet Explorer from the Windows 8 desktop.

No workaround is currently available for the iOS Safari browser.

Delete the AverageRating property prior to upgrading from Preview

The upgrade from Preview to the released version will automatically add a new managed property called AverageRating. If you created this property in their Preview installation, the upgrade will fail.

My Site upgraded to 2013 but is set to run in 2010 mode, clicking Gear Menu >Add an App gives an error

When the My Site is upgraded to 2013 but is set to remain in 2010 mode, you will get an error message.

Workaround    There is currently no workaround available.

Indexer process doesn’t free up old memory after repartitioning

One reason to trigger repartitioning might be high memory pressure on index nodes. The issue is that after index repartitioning old index nodes are still at the same memory usage, which stays forever until the Index node restarts.

Workaround    We recommend you restart spsearchhostcontroller service on old index components and to run this step before doing $ssa.ResumeAfterIndexRepartitioning(). But before restarting hostcontroller it makes sense to check that old index replicas are in sync with their primaries.

Trying to retrieve fcocount when collapsing/grouping isn’t turned on causes the query to crash

If TrimDuplicates=False or TrimDuplicatesIncludeId is used while retrieving the managed property fcocount then the query fails.

Workaround    Don’t request for fcocount while TrimDuplicates=False or TrimDuplicatesIncludeId is used.

New-SPEnterpriseSearchIndexComponent checks the existence of RootDirectory in the wrong server

You want to add a new index component to the search topology, and want to specify a non-default root directory for the index files. For example:

New-SPEnterpriseSearchIndexComponent -SearchTopology $t -SearchServiceInstance $ssi -IndexPartition 1 -RootDirectory ""d:\index4"

The cmdlet might fail with the following error message because it incorrectly checks if the indicated root directory exists on the server the cmdlet is run on:

Cannot bind parameter 'RootDirectory' to the target. Exception setting ""RootDirectory"": ""Could not find a part of the path 'd:\index4'."

Workaround    You can create the new index component using the following procedure instead:

$host02 = (Get-SPServer"").Name

$ssa = Get-SPEnterpriseSearchserviceApplication

$t = $ssa.ActiveTopology.Clone()

$ic = (New-Object Microsoft.Office.Server.Search.Administration.Topology.IndexComponent $host02,1);

$ic.RootDirectory =""d:\index4"

$t.AddComponent($ic)"

PerformancePoint Dashboard Designer Help doesn’t open as expected

When you click Help in Dashboard Designer, Help for SharePoint Server opens, and there is no mention of Dashboard Designer on the page.

Workaround    Help is available for Dashboard Designer, even though it's not visible on the Home screen of the Help Viewer. To view content about Dashboard Designer, in the search box near the top of the Help window, type "Dashboard Designer." A list of resources for Dashboard Designer appears.

PowerPoint intent isn’t shown

PowerPoint intent isn’t shown as PowerPoint query rule condition is missing semicolon in Spanish build and results in incorrect behavior in OOB intent for PowerPoint. Also this happens only for Arabic and Spanish server, without any language packs.

Workaround    Administrators can copy the existing query rule condition for PowerPoint and insert the missing semicolon or correctly place the semicolons that were causing the issue. The old entry can then be deleted to ensure the updated query rule is picked up.

 TOP OF PAGE

SharePoint Server search

Trouble getting search to work with anonymous access

You might get the following error message when you try to use search with anonymous access.

An exception occurred when trying to issue security token: The security token username and password could not be validated.

Workaround    The workaround is to change the OS locale to a local language.

reference: http://office.microsoft.com/en-in/help/sharepoint-server-2013-known-issues-HA102919021.aspx#_SharePoint_Server