Issues Fixed by Service Pack 1 (SP1) in Office and SharePoint

Resources
List of all Service Pack 1 (SP1) updates for Microsoft Office 2013 and related desktop products (KB 2850036) List of all Service Pack 1 (SP1) updates for Microsoft SharePoint Server 2013 and related server products (KB 2850035)

Table of Contents
Access Audit and Control Management Server Excel Lync Office Shared (Affects Multiple Applications) Outlook PowerPoint Project Publisher SharePoint Visio Word

Notes
phrasing, SP1 fixes all of the issues listed. issues too specific to include in this list.

1. Service Pack 1 also includes a rollup of all Cumulative Updates through December 2013, and all Public Updates through shipping for the first time in SP1.

2. Text for some list items describes a problem now fixed by SP1, while other items describe both the problem and the new

3. SP1 also contains additional changes which are less visible, but improve various aspects of the product. This includes red

Fix Descriptions
Product Access
Access

KB Number
2817430

Access Access Access Access Access Access

2817430 2817430 2817430 2817430 2817430 2817430

Access Access Access Access Access Access Access Access Access Access Access Access Access Access

2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430

Audit and Control Management Server

Audit and Control Management Server 2863865

Excel
Excel Excel 2817430 2817430

Excel

2817430

Excel Excel Excel Excel Excel Excel Excel

2817430 2817430 2817430 2817430 2817430 2817430 2817430

Excel Excel Excel Excel

2817430 2817430 2817430 2817430

Lync
Lync 2817430

Office Shared
Office Shared Office Shared Office Shared Office Shared Office Shared Office Shared 2817430 2817430 2817430 2817430 2817430 2817430

Office Shared

2817430

Office Shared

2817430

Outlook
Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook Outlook 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430

Outlook

2817430

Outlook Outlook Outlook Outlook Outlook

2817430 2817430 2817430 2817430 2817430

Outlook Outlook Outlook Outlook Outlook

2817430 2817430 2817430 2817430 2817430

PowerPoint
PowerPoint PowerPoint PowerPoint PowerPoint PowerPoint PowerPoint PowerPoint PowerPoint PowerPoint PowerPoint PowerPoint 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817433; 2817434

Project
Project

Project Project

2817433; 2817434 2817433; 2817434

Project Project Project Project Project Project Project Project Project Project Project Project Project

2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434

Project Project Project Project Project Project

2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434

Project Project Project Project Project Project Project Project Project Project Project Project Project Project

2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817433; 2817434 2817430 2817430

Publisher
Publisher Publisher

SharePoint
SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint 2817429 2817429 2817429 2817429 2817429 2817429 2817429

SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint

2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429

SharePoint SharePoint SharePoint

2817429 2817429 2817429

SharePoint SharePoint SharePoint SharePoint

2817429 2817429 2817429 2817429

SharePoint SharePoint SharePoint SharePoint

2817429 2817429 2817429 2817429

SharePoint SharePoint

2817429 2817429

SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint SharePoint

2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429 2817429

Visio
Visio 2817443

Visio Visio Visio

2817443 2817443 2817443 2817430 2817430 2817430 2817430 2817430 2817430 2817430

Word
Word Word Word Word Word Word Word

Word

2817430

Word Word Word Word Word Word Word Word Word

2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430

Word Word Word Word Word Word Word Word Word Word

2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430 2817430

Word Word

2817430 2817430

Word

2817430

Word Word Word Word Word Word

2817430 2817430 2817430 2817430 2817430 2817430

(SP1) in Office and SharePoint 2013

13 and related desktop products (KB 2850036)

nt Server 2013 and related server products (KB 2850035)

dates through December 2013, and all Public Updates through January 2014. The list below is specific to changes SP1, while other items describe both the problem and the new behavior after installing SP1. Despite variations in

e, but improve various aspects of the product. This includes reducing crashes, improving security, and fixing other

Text
Currency values may become zero when importing an Excel file into Access.

Access app developers can now upgrade the apps they have made available in the Store or a corporate catalog. A crash may occur when opening a new connection using the Data Access Objects (DAO). A crash may occur when using Access as a DDE server and closing a database while a DDE conversation is in progress. Exporting to an Excel spreadsheet that uses named ranges can sometimes fail. Lookups to text don't have the expected field size. When creating an Access web app that uses currency fields on a computer with Windows 8.1 installed, the app may fail to load in the browser with the message "an error has occurred." Access may crash when running a query that invokes a user-defined function. An error may occur when an Access app is refreshed in Internet Explorer 10. Access cannot open a linked table or Access Services 2010 web database when the server URL changes protocols from http to https. A generic "error has occurred" message appears when a database has exceeded its maximum size limit. Access may crash when a new form is created while another object is open. Access may crash when the navigation control in Layout view is used. Buttons do not appear correctly when the screen resolution is set to anything other than 100% DPI. Exporting a multi-page report to HTML results in a lot of blank pages. An error appears when the "Preview Datasheet" feature is used on Windows 8.1. A view can't be duplicated if it contains an embedded query along with an embedded macro or an embedded named expression. A syntax error may appear if numbers containing trailing zeroes after the decimal point are entered into expressions in an Access app. Pressing CTRL+Arrow key on a tab control can cause Access to crash. Linking to SharePoint lists from an Access Services 2013 application fails if the list uses a locale other than English. When a Project file is saved as an Excel workbook, dates are saved in US English format instead of the user's regional settings. When monitoring files in a SharePoint document library, files are only tracked if they appear on the first page of the default view for the document library. On some machines, when a user switches to Page Layout View and then enters and exits print preview, Excel will run very slowly, potentially to the point of completely freezing. When a user opens an .xls file with an old password in it and then tries to assign another password to anything else in the workbook, like another sheet or a range, all of the existing passwords are overwritten with the new password. Comment text written in Arabic, Hebrew, Hindi, or Thai is cut off and can only be fully viewed if it is edited.

At a high DPI setting, the checkbox in the filter menu does not appear. Incorrect results are returned when the language is set to Japanese and JIS function is used on certain strings. A runtime error occurs when the PageSetup.PrintArea property is set by string via a variable. Data validation that uses relative references may not be correctly saved to HTML file formats, which causes data validation to be broken when the file is reloaded. At a high DPI setting, the dashed border is hidden in the Borders tab of the Format Cells dialog box, and when it is applied to a cell, the border disappears. Excel may crash when a password-protected XLS file is opened. After inserting an IVS character (such as certain Japanese Kanji characters with slight differences from base characters), deleting the IVS character using the backspace key requires pressing the backspace key twice. FILTERXML parses numbers between 1900 and 9999 as the day before that year. A file may become corrupted if there are many merged cells and the user sorts the worksheet. At a high DPI setting, showing the print gridlines by either going into Print Preview or Print Layout and then going back to normal view, causes the gridlines to be drawn in white. A crash may occur when a shared, Information Rights Management (IRM) protected Excel workbook is saved. When the Lync client is used by a 3rd party application as an out-of-proc COM server showing no Lync UI ("UI suppression mode), the Lync process does not exit after the app is closed. List templates can't be retrieved using the Office client object model. It's not possible to move the cursor using only the keyboard when adding an Organizational ID in the Sign-in screen. EPS images are not properly embedded when they are inserted using the "Insert and Link" feature. JNLP file types are now blocked in Outlook, InfoPath, and SharePoint. OneNote warns users attempting to open JNLP files. Users who are not joined to a domain cannot configure Information Rights Management. A crash may occur when creating a digital signature in Word, Excel or PowerPoint, when the SignatureHashAlg, InvalidHashAlg, LegacyHashAlg values contain uppercase letters or don't match the expected list of values. By default, every Office user has the ability to activate/deactivate any add-in. However, there are some enterprise scenarios where an organization may want to require certain non-admin users to always have some specific add-ins activated. The Registry Key 'DisableLMAddinOverwrite' can be set in order to prevent non-admin users from activating/deactivate add-ins loaded by an admin.

When a digital signature is added to a Word, Excel or PowerPoint file Office 2013 was not respecting the SignatureHashAlg registry key under HKCU\Software\Microsoft\Office\15.0\Common\Signatures. This prevents Office 2013 from creating digital signatures that Office 2007 can validate when using a certificate that contains a SHA256 hash.

When an exact match name resolution is attempted using the equal sign, Outlook resolves the wrong name. Unexpected text is added when properties are changed in a shared mailbox. Outlook may crash when IMAP is used with a custom add-in. Outlook downloads duplicate e-mails when a POP profile is used. Mail gets stuck in Outlook when SaveReplies and NoOST is set on a cached mode profile. Exchange export fails after Outlook is updated to KB 2687623. Outlook may freeze for 45-60 seconds on the initial account setup screen. A message may be stuck in the Outbox indefinitely when the length of the legacyExchangeDN + the length of the server name exceeds 245 characters. Outlook sometimes shows an incorrect value in Quota Thermometer. The object model event, dispidEventOnWriteWhen, is not fired when a reminder is dismissed. In Cached Mode, "last modified by" is not set correctly for exceptions. A meeting request from Lotus Notes can crash Outlook. The Read/Unread count may not update in the folder tree. Favorites of public folders will occasionally disappear. Attachments may not be sent with a read-only e-mail. Custom Document Property values are not displayed in a SharePoint document library when saving an e-mail from Outlook. On high resolution screens, the LinkedIn entry in the Social Connector dialog box does not allowed the user to remove an account using the delete icon that appears on mouse hover. Quick Steps don't fire off any Object Model events. Rich text is incorrectly formatted as plain text when a custom form is used to create a new e-mail. Outlook crashes when attempting to access a user property on an exception item. A deleted inline picture will become an attachment when you save a "Do not forward" mail before sending it. An error occurs when custom actions are performed on custom MAPI forms that don't use IDispatch. The Zoom field in the Scheduling Assistant dialog box has no label for screen readers to read. A contact address field is overwritten instead of changed or appended. For example, if a street address is added to an address that already has a city and zip code, the city and zip code may be lost. A crash may occur if Ctrl + N is pressed when the Advanced Find dialog box is open.

In Modeless Simple MAPI, if an e-mail is sent via a secondary Exchange account, Outlook will leave the email in the wrong Sent Items folder. Outlook prompts for credentials if it is started in disconnected mode and then connects with a firewall public profile that blocks outbound traffic. Setting a resource(location) programmatically through the Outlook object model does not work properly. Default special folders may be duplicated if Outlook is started without an OST and while disconnected. When adding ambiguous names to the To: and Cc: fields and clicking between them on the custom form, the To: and/or Cc: box will shrink in size, making it impossible to add users or to see which users are there. A write event is not triggered properly when the "Mark as read" / "Mark as unread" commands are used. At high-DPI settings, images in e-mails may grow unexpectedly. Outlook crashes if a new e-mail containing a table with merged cells is left in the background. Outlook may crash when printing an e-mail with OLE objects in it. When using custom Outlook forms with plain-text, the user is prompted every time they send an e-mail, warning that formatting will be lost, even though there is no formatting in the e-mail.

PowerPoint may crash when the slide is advanced in slideshow mode, while another PowerPoint file is opened in protected view. A crash may occur when PowerPoint slides are previewed in the Windows Explorer preview pane. If a read-only PowerPoint file containing images is saved as another PowerPoint file, the images may be lost. When PowerPoint slides are copied and pasted into Word, the slide/page numbers change. It's not possible to undo the addition of tags to a presentation. It's not possible to switch to Reading View when a presentation is in protected mode. Presentations.Count may return incorrect value when trapping PresentationAdd, PresentationClose, PresentationOpen and PresentationClose events. Creating a presentation programmatically and attempting to save it, results in a .potx type file instead of the default type (which is usually .pptx). The preview pane in Windows Explorer does not show a PowerPoint slide show unless a Word document is previewed first. Presentation.Fullname does not return the full name (path and file name) when it is called from inside a PresentationSave event during shutdown. Bulleted text doesn't indent as expected when IndentLevel is set programmatically. If the view (resource or tasks) has one column that has a dependent read-only column, the paste action will try to override the read-only column and will generate an error message.

Close Tasks to Updates view disappears when switching to Project Server Permissions mode. When migrating projects with project-level calendars to Project 2013 from earlier versions, in some instances the default Project calendar can conflict with the calendars in the MPP file, leading to unexpected scheduling discrepancies. Additionally, when expanding a subproject inside of a master project, rollup custom fields can display the value "#ERROR" or no value at all until the subproject is opened and a recalc is forced. If a view uses an interactive filter, that filter will be removed from the view definition if a user cancels setting the filter when applying the view. Importing a project from Excel may fail to properly set the task progress. Documents, Issues, and Risks sections on the Task Details page don't display links. Certain tasks with very high work loads cannot be viewed in the Approval Center. If a project with subprojects is opened before it is completely saved on the server, it may become corrupted. Deleting a project created from the Project Ideas list can fail if the Project Ideas list was deleted. In some cases, time phased cost and work values entered for a baseline in Project do not properly appear in the reporting database. At a high DPI setting, the view names displayed on the left side of the screen may not appear correctly. Users cannot edit a task's work or remaining work in the Schedule Web Part when Protected Actuals is enabled on the server and the task already has actual work. Out-of-the-box Project web parts do not function outside of the Project Web App site collection. Resource costs are not calculated correctly when using the project update PSI for assignments that contain multiple cost rate table entries. When projects are created in PWA using template-based EPTs, notes that are associated with tasks are lost when the project is opened in the Project client. Project shows the error "The following job failed to complete. Job Type: Save. Error ID: 9000(0x2328)" when attempting to save changes in enterprise projects with more than 5000 tasks. If the user selects one (or more) cells and then right-clicks in a cell that requires the grid to scroll, the right-click selection is lost. When Project CSOM is used to return the collection of projects, the collection will now include subprojects. If a textbox is added to a Gantt chart with a number in front of the text, the number shows up after the text in printing/print preview. The Import Timesheets feature does not work properly when the language setting is not English. If the Gantt chart is split with the resource graph view, Project may crash when the bar styles for the resource graph are edited. When a baseline is saved from the context of a Master Project, Project may crash unexpectedly.

The number of calendar exceptions allowed for a single entity in Project has been increased. The main Project icons will now be displayed correctly at a high DPI setting. Project may not show the baseline data correctly if time phased baseline work and/or baseline cost is edited. Baseline Work calculations sometimes do not update correctly while the user is in the Resource Usage view. The Previous, Next and Select Period buttons are now enabled so that the user can move to a different period where there is an active time period. When leveling granularity is set to a value greater than Days (Weeks and Months, for example), leveling does not properly resolve over allocation issues. Saving and publishing a project on Project Server may take a long time. Publishing a project, when resources in the project have assignments in many other projects, may take a long time to complete. If the Office-wide profile setting turns off saving to either XPS or PDF, then the Project Save As dialog may not work correctly. Earned value calculations do not work correctly in Project when any baseline other than Baseline0 is used. Time phased Actual Cost and Baseline cost may not properly appear in the reporting database if there's no associated time phased work/baseline work with the cost. On some assignments with modified contours and small assignment unit values, it's not possible to set the % Work Complete field to 100%. Tasks deleted using the Gantt view on a SharePoint list do not go to the Recycle Bin of that site. CustomFieldValueListAdd method cannot write values over 127 characters long. Cursors, the ruler, and the Word Art gallery in Publisher appear pixelated on high DPI devices. The ruler is clipped in print preview when the user changes the display settings to view text at 200%.

Metadata is lost when documents that use a custom content type with a "Description" field are opened for editing. When an item is deleted, restored from recycle bin, and then deleted again, there is a primary key constraint error. An error occurs when files are moved between document libraries and the web time zone is behind that of the server. Metadata filtering at list level always lists all metadata terms. The hyperlink popup window drops the selected word to be linked when there is a delay of more than one second in opening the window. Multiple-column, SummaryLinkWebParts with a group heading style of "Separator" are rendered incorrectly. A hash tag that contains a full width space does not get created successfully.

Search schema compression is now enabled by default to allow larger search schemas. Highlighting for FQL queries is now enabled for FQL as well as KQL. Opening a custom SharePoint list in datasheet view and applying multiple custom filters, where each filter has more than one condition, can result in an incomplete set of list items. When the "Export to Excel" button is clicked in a SharePoint document library that has the Content Type field displayed, the Content Type field does not appear in the Excel workbook. An error occurs after changing the "Manager" property in EditProfile.aspx page when the My Sites WebApp is not in the same farm as the UPA. SharePoint REST API does not return a well-defined error response for a duplicate key exception. Developers are unable to specify a Content Type ID when creating Content Types in the client object model. On list views in SharePoint sites, the Connect to Outlook button in the ribbon may be erroneously disabled. In some non-English languages of SharePoint, the text displayed in the callout UI for a document or list item, describing who last edited the item, may not be grammatically correct. Copy and Paste in a datasheet does not work correctly with Internet Explorer 11. Pages do not render in Safari for iPad when private browsing mode is used. When editing rich text fields in SharePoint, if the editing session exceeds 30 minutes, the edits may not be saved. An error that says "SCRIPT12004: An internal error occurred in the Microsoft Internet extensions" may occur intermittently when users visit their SkyDrive Pro or other pages on their personal site. InfoPath may crash when a form that points to a SharePoint list, with a lookup to another SharePoint list, is opened. An InfoPath form with extended characters in its name fails to open. An error that says "Security Validation for the form has timed out" may occur when an InfoPath form is digitally signed and hosted in a SharePoint site collection that uses the SharePoint version 2010 user experience. "Show document icon" remains unchecked and the document icon does not show in Edit Properties for a list item. A "Failed tagging this page" error occurs when the "I like it" button is clicked. The wrong term is removed when manually editing a multi-valued taxonomy field. When tagging list items using a language that is different from the term store default language, suggestions for labels are offered in multiple languages. The suggestions appear confusing because both language suggestions are listed without any identification of the language. An error that says "There was an error processing this request" may appear when editing the user profile. Times are missing from Date/Time results in certain filtered list web service calls. Minimal and no metadata are now enabled as supported JSON formats. Actions4 schema workflow actions can't be deployed to SharePoint.

Using Client Object Model, Stream.Seek() to seek to a particular position doesn't seek at the proper offset. Refreshing a workflow status page generates the following error: "System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary." Setting custom, non-English outcomes in web pages on tasks in a workflow fails to set the value. Configurations of SharePoint using Azure Hybrid mode and Workflow Manager together can cause workflow callbacks to fail. Workflow task processes on wiki pages won't start. Workflows won't wait for changes to content approval status fields. E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows. Workflows may fail to send an e-mail or send too many e-mails. Association variables do not update correctly for auto-start workflows. A KeyNotFoundException error may occur in a workflow when the associated task list uses unique permissions. Incomplete tasks are deleted when workflow task activities complete. Task activity is suspended when the task is completed using app-only credentials. An error that says "This task could not be updated at this time" occurs when trying to complete a workflow task using the "Open this task" button in Outlook. A workflow doesn't respond properly when waiting for changes in specific types of list columns, such as Boolean, Date Time, and User. Connectors in UML sequence diagrams don't work properly. The message arrow shape gets converted into a return message arrow shape and vice versa, when the direction of the arrow is reversed. CAD drawings are blurry at high magnification (zoom). Certain BPMN diagram shapes may not render until the page is refreshed. At a high-DPI setting, the ribbon icons and other user interface elements appear blurry. Certain Word documents containing old diagrams can't be saved in the ISO Strict format. The Y axis label text in a chart may become unreadable if it is rotated. Setting document protection via the object model will fail when the document's current selection contains a grouped content control. When comparing documents with footnotes or endnotes that are formatted with custom styles, a whole footnote or endnote is incorrectly shown as being deleted and reinserted. Tables with merged cells may not render correctly when an 8-bit remote desktop connection is used to access Word. Word may freeze when opening a document that uses a font that is not available on the computer. If VBA is used to iterate through the revisions collection of a document, Word may get stuck in an infinite loop.

When selecting multiple disjoint cells in a table, querying Selection.End via Word's object model returns the character position of the first cell selected instead of the character position of the last cell selected. Printing documents in Booklet layout will cause some HP printers to print horizontal white lines across the content. Converting a document to PDF with Word Automatic Services could result in table indents being ignored in the PDF file partway through the document. Table captions with SEQ fields print incorrectly if the document is marked as final. Digits may fall outside the End of Ayah mark or other Arabic subtending marks, and the order of digits inside subtending marks is reversed. At high-DPI settings, the ruler and cursor appear pixelated. Word may become unresponsive when copy/pasting content with bullets, numbering, or styles on a touch screen device. The chevron of a collapsed heading is not fully visible. Text is duplicated with every keystroke when typing in a plain content control, where the text has range permissions on it and Track Changes is enabled. In the Japanese language version of Word, when a user creates or edits a paragraph style to have hanging indents and left indents defined in character units, the hanging indent is lost when the Modify Style, Paragraph dialog box is reopened. The bottoms of text boxes are cut off during printing, when those text boxes contain multiple paragraphs with horizontal borders applied to them. Converting a numbered list in a content control to plain text using the object model results in the number for the first list item falling outside of the content control. Using VBA to attach a template from a network share to a document, while populating a global variable, results in a run-time error. Users who are co-authoring a Word document are prompted to save too frequently. Opening quotation marks that are typed in Latvian are lowered incorrectly. Manipulating tables using Selection.Text takes too long to execute. Table of Figures does not update correctly after a user deletes tables or figures with sequential captions while Track Changes is enabled. A right-tab may incorrectly cause a line to break. Bookmarks near textboxes may not be loaded when opening RTF files. Programmatically setting the bounds of a floating shape results in incorrect bounds, when the document is in compatibility mode and when the "Show white space between pages in Print Layout view" checkbox in Options is unchecked. Getting or setting Document.PageSetup properties through VBA fails for documents that contain floating tables. When clicking on a hyperlink in the research pane for a location that is in the Local Intranet trusted zone in Internet Explorer's Internet Options, Internet Explorer will no longer immediately disappear after opening the link. Attempting to use Document.Repaginate when the selection is within a locked Content Control or within a coauthoring lock results in an error.

Documents may sometimes become corrupted when they contain equations. Using "Send as Attachment" results in the attached document having a duplicate extension, if the original document's extension is uppercase. Performance is slow when copying large amounts of content into a content control. When there isn't a good line break opportunity, Word sometimes breaks inside glyph clusters. Opening a document that contains a multi-line content control that itself contains a line break, results in digital signatures being declared invalid, as if edits were made to the document. Editing or undoing certain changes can change the way a run of text line-breaks.