Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article describes the issues that are fixed in the Microsoft SharePoint Server 2013 Client Components SDK hotfix package that is dated April 8, 2014.


Issues that this hotfix package fixes

  • Time zone definitions in SharePoint Server 2013 are not updated to accommodate changes in several countries.

  • When you access some SharePoint Server 2013 resource that you do not have the permission for, you receive the OOB access denied page instead of the customer access denied page.

  • When you configure Alternate Access Mapping (AAM) in SharePoint Server 2013, the links of a mentioned link is pointed to the default zone in the newsfeed Web Part.

  • You cannot send alerts to a security group instead of a user. 

  • When a SharePoint Server 2013 site collection is in the SharePoint Server 2010 mode, the picture URL in the "modified by" or "created by" columns in a discussion board or document library is incorrect.

  • When you try to edit content for HTML form Web Part in certain web browsers, you receive the following error message:

    Cannot retrieve properties at this time.

  • When you use a team site or project site template to create a site collection by running the New-SPSite PowerShell cmdlet, the cmdlet fails if there is no name that is specified for the site.

  • When the display name of a user contains a comma, people picker field in the synchronous event receiver displays an incorrect value.

  • When you try to install an app that requires tenant administrator permission on a SharePoint Server 2012 server, the Trust It button on the app is disabled and you receive the following error message:

    Sorry, only tenant administrators can add or give access to this app.

  • When you change the fallback language on a SharePoint Server 2013 server, you experience high CPU usage on the server.

  • When you configure Forms-Based Authentication (FBA) with active directory as back end for a SharePoint Server farm, the "Everyone" view on the Newsfeed page displays an error.

  • Assume that you create a publishing page that contains a friendly URL on a SharePoint Server 2013 site collection. Then, you select the Hide physical URLs from Search check box. When you try to filter the Web pages, the publishing page is filtered out.

  • When you try to update project-level fields such as owner or description in Project Web App on a project that contains multiple formulas, the update will time-out and you receive the following error message:

    An error has occurred when saving your project to the server. Please contact your administrator for assistance.

  • When you set the site locale to a language that uses the comma as a decimal separator, the average rating information on the rating stars does not appear.

  • Assume that you add a custom column to a document library. When you upload a document to the document library, you receive the following error message:

    SCRIPT5007: Unable to get property 'newFileUrl' of undefined or null reference

    sp.ui.rte.js, line 2 character 72027.

  • Assume that you upgrade an SharePoint Server 2010 site to SharePoint Server 2013. When you open a page that contains multiple value lookup fields, you receive the following error message:

    Sorry, something went wrong Attempted to use an object that has ceased to exist. (Exception from HRESULT: 0x80030102 (STG_E_REVERTED))

  • When you sort the items on a SharePoint Server 2013 list view that has the Asynchronous Updates and Server Rendering options enabled, the ribbon buttons for the list are disabled.

  • You cannot restore a site from recycle bin that has a copy in the same database.

  • When you do some activities on project database that has a long name in Project Web App, the activities fail.

  • You cannot create a form based crawl rule if the length of the security string is more than 5200.

  • On a list form that contains rich text fields, dropdown menus may sometimes close automatically in Internet Explorer.

  • After you check out, edit (that triggers a SharePoint 2010-style workflow), and check in a document in a SharePoint Server 2013 document library, the workflow's status column displays an incorrect status.

  • You experience issues when you use Data Protection Manager (DPM) on SharePoint Server 2013 sites that contains apps.

  • The "Reporting (Project Sync) job" queue job fails when you publish a project and the site to which the project is connected to has more than one issue list defined. You also see an error in the queue with details similar as follows:

    ReportingWSSSyncMessageFailed (24016) - RDS failed while trying to sync one or more SP lists.

More Information

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To install this hotfix package, you must have SharePoint Server 2013 Client Components SDK installed.

Restart requirement

You do not have to restart the computer after you install this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to resolve the issue that listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!