You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps

You receive a "Sorry, there was a problem and we can’t open this document" error when you try to view an Office document in Office Web Apps and the primary reason for the behaviour are the following settings

  1. AllowOAuthOverHttp setting is set to False (It should be set to True)
  2. The SharePoint host domain is not in the allow list. Use the New-OfficeWebAppsHost command to add the domain to the allow list

However, you might also see the same error when your OWA server is not able to communicate with the SharePoint server. Check that both SharePoint and the OWA server are able to communicate with each other. Also see http://www.dhirendrayadav.com/2014/01/you-receive-this-document-cant-be.html

Service Pack 1 for SharePoint 2013

Update:

Microsoft has discovered some problem with SharePoint 2013 Service Pack 1. So do not update your environments until further notice

We have recently uncovered an issue with the following Service Pack 1 packages that may prevent customers with Service Pack 1 from deploying future Public Updates.  As a precautionary measure we have deactivated the download pages until new packages are published.

http://support.microsoft.com/kb/2817429

http://blogs.technet.com/b/office_sustained_engineering/archive/2014/02/25/announcing-the-release-of-service-pack-1-for-office-2013-and-sharepoint-2013.aspx

Service Pack 1 (SP1) for SharePoint 2013 family of products is now available! Service Pack 1 provides fixes to improve general stability, functionality, and security in Office, SharePoint Server, and other related products.Microsoft SharePoint Server 2013 Service Pack 1 (SP1) provides the latest updates for SharePoint Server 2013. This service pack includes two kinds of fixes:

  1. Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and security.
  2. All the monthly security updates that were released through January 2014, and all the Cumulative Updates that were released through December 2013.

The service pack for SharePoint can be downloaded here

List of issues fixed

SharePoint2817429​Metadata is lost when documents that use a custom content type with a “Description” field are opened for editing.
SharePoint2817429​When an item is deleted, restored from recycle bin, and then deleted again, there is a primary key constraint error.
SharePoint2817429​An error occurs when files are moved between document libraries and the web time zone is behind that of the server.
SharePoint2817429​Metadata filtering at list level always lists all metadata terms.
SharePoint2817429​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.
SharePoint2817429​Multiple-column, SummaryLinkWebParts with a group heading style of “Separator” are rendered incorrectly.
SharePoint2817429​A hash tag that contains a full width space does not get created successfully.
SharePoint2817429​Search schema compression is now enabled by default to allow larger search schemas.
SharePoint2817429​Highlighting for FQL queries is now enabled for FQL as well as KQL.
SharePoint2817429​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.
SharePoint2817429​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.
SharePoint2817429​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.
SharePoint2817429​SharePoint REST API does not return a well-defined error response for a duplicate key exception.
SharePoint2817429​Developers are unable to specify a Content Type ID when creating Content Types in the client object model.
SharePoint2817429​On list views in SharePoint sites, the Connect to Outlook button in the ribbon may be erroneously disabled.
SharePoint2817429​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.
SharePoint2817429​Copy and Paste in a datasheet does not work correctly with Internet Explorer 11.
SharePoint2817429​Pages do not render in Safari for iPad when private browsing mode is used.
SharePoint2817429​When editing rich text fields in SharePoint, if the editing session exceeds 30 minutes, the edits may not be saved.
SharePoint2817429​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.
SharePoint2817429​InfoPath may crash when a form that points to a SharePoint list, with a lookup to another SharePoint list, is opened.
SharePoint2817429​An InfoPath form with extended characters in its name fails to open.
SharePoint2817429​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.
SharePoint2817429​“Show document icon” remains unchecked and the document icon does not show in Edit Properties for a list item.
SharePoint2817429​A “Failed tagging this page” error occurs when the “I like it” button is clicked.
SharePoint2817429​The wrong term is removed when manually editing a multi-valued taxonomy field.
SharePoint2817429​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.
SharePoint2817429​An error that says “There was an error processing this request” may appear when editing the user profile.
SharePoint2817429​Times are missing from Date/Time results in certain filtered list web service calls.
SharePoint2817429​Minimal and no metadata are now enabled as supported JSON formats.
SharePoint2817429​Actions4 schema workflow actions can’t be deployed to SharePoint.
SharePoint2817429​Using Client Object Model, Stream.Seek() to seek to a particular position doesn’t seek at the proper offset.
SharePoint2817429​Refreshing a workflow status page generates the following error: “System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.”
SharePoint2817429​Setting custom, non-English outcomes in web pages on tasks in a workflow fails to set the value.
SharePoint2817429​Configurations of SharePoint using Azure Hybrid mode and Workflow Manager together can cause workflow callbacks to fail.
SharePoint2817429​Workflow task processes on wiki pages won’t start.
SharePoint2817429​Workflows won’t wait for changes to content approval status fields.
SharePoint2817429​E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows.
SharePoint2817429​Workflows may fail to send an e-mail or send too many e-mails.
SharePoint2817429​Association variables do not update correctly for auto-start workflows.
SharePoint2817429​A KeyNotFoundException error may occur in a workflow when the associated task list uses unique permissions.
SharePoint2817429​Incomplete tasks are deleted when workflow task activities complete.
SharePoint2817429​Task activity is suspended when the task is completed using app-only credentials.
SharePoint2817429​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.
SharePoint2817429​A workflow doesn’t respond properly when waiting for changes in specific types of list columns, such as Boolean, Date Time, and User.

InfoPath is dead (not for now)

We all have been wondering about the future of InfoPath and SharePoint forms, and now we’ve some information on the next generation of Office forms. Microsoft is bringing in new intelligent, integrated forms experience that will span across devices. The new forms can be easily designed, deployed, and will use intelligent, integrated forms across Office clients, servers, and services—forms that everyone can use on their PC, tablet, or phone. Some FAQ’s Is InfoPath 2013 is the last release?
Yes InfoPath 2013 is going to be the last release of the desktop client What about InfoPath Form Services?
InfoPath Forms Services in SharePoint Server 2013 is the last release of InfoPath Forms Services What about InfoPath in Office 365?
The InfoPath Forms Services technology within Office 365 will be maintained and it will function until further notice. What should I use to build and complete forms?
You should continue to use InfoPath technology. What are the alternatives?
Microsoft investing in new forms technology across SharePoint, Access, and Word I use InfoPath, how will I get impacted?
Microsoft working on migration guidance in parallel to their their next generation forms technology. InfoPath 2013 desktop client and InfoPath Forms Services for SharePoint Server 2013 will continue to be supported through 2023. What next?
More details will emerge as the year progresses. A sneak peak will be available at the SharePoint Conference

Power BI for Office 365 now available

Microsoft has made Power BI available for all Office 365 customers. Power BI for Office 365 brings self-service BI solutions to everyday business users through the familiar tool they already use – Excel. Power BI for Office 365 is a cloud-based business intelligence (BI) solution that enables our customers to easily gain insights from their data, working within Excel to analyse and visualize the data in a self-service way. It works with Office 365 to help customers share insights, find answers and stay connected to their data from their favourite mobile devices. Power BI for Office 365 includes:

  • Power Query, enabling customers to easily search and access public data and their organization’s data, all within Excel (formerly known as “Data Explorer“).
  • Power Map, a 3D data visualization tool for mapping, exploring and interacting with geographic and temporal data (formerly known as product codename “Geoflow“).
  • Power Pivot for creating and customizing flexible data models within Excel.
  • Power View for creating interactive charts, graphs and other visual representations of data.

visual studio Bing Code Search

Bing Code Search for Visual Studio 2013 helps developers find and reuse code samples on the web more easily by bringing the code search experience directly into Visual Studio. With this extension, a developer can search sites such as MSDN, Stack Overflow, CSharp411 and Dotnetperls and find, copy and use C# code samples directly inside the IDE. Bing Code Search works currently for C# solutions only, more languages to follow.All the snippets in the index were automatically checked to ensure they compile, but in the search, the algorithms also look at votes from the given community that the snippet comes from and other quality signals. The best thing, though, is that it doesn’t just copy and paste the snippet into the code, but it will also try to modify the code to fit the variables you already use in your own code. Even if you don’t have Visual Studio installed, you can try a web-based version (with a slightly different interface) here. Here is a video demonstration of the Bing search add-on   Source: http://blogs.msdn.com/b/visualstudio/archive/2014/02/17/introducing-bing-code-search-for-c.aspx