Sorry,we can’t open this document because there was a problem talking to the service – Office Web Apps 2013

Farm Information:

  1. Web Application published internally and externally (so make sure both URLs added to Alternate Access Mapping)
  2. Office Web Apps 2013 (Published externally via TMG 2010 and internally)

I have a farm which connected to Office Web Apps 2013 and It’s working fine internally so then we decided to enable it to open Office Web Apps externally by the following steps :

1- In Office Web Apps Server , Open Power Shell and run this command to add the External URL to existing Farm:

Set-OfficeWebAppsFarm -ExternalURL http://test.com/

OfficeWebApp2013

2-In SharePoint Server , Open SharePoint 2013 Management Shell and run the following commands:

Remove-SPWOPIBinding –All:$true

New-SPWOPIBinding -ServerName OfficeWebAppServer.com -AllowHTTP
Set-SPWopiZone internal-http
$c = Get-SPSecurityTokenServiceConfig
$c.AllowOAuthOverHttp = $true
$c.Update()

then when I tried to access the Office documents from External URL I got the following error :

“Sorry,we can’t open this document because there was a problem talking to the service”

OfficeWebApp2013_1

This issue related to TMG publishing rule so to fix it :

1- Open TMG Management Console

2- Go to Publish rule for Office Web Apps

3- Right click on the rule and choose Configure HTTP

4- Uncheck  Verify Normalization

5- Click ok

6- Click Apply

7- Wait the sync process

OfficeWebApp2013_2

Ref:

http://technet.microsoft.com/en-us/library/jj204665.aspx

http://blogs.technet.com/b/dodeitte/archive/2013/11/10/issue-with-office-web-apps-server-2013-published-externally-using-tmg-2010.aspx

New WCM Features in SharePoint 2013

This SQLServer instance does not have the required “max degree of parallelism” setting of 1

I have got this error while trying to install SharePoint 2013

max degree of parallelism

What is Max Degree of Parallelism ?
When an instance of SQL Server runs on a computer that has more than one microprocessor or CPU, it detects the best degree of parallelism, that is, the number of processors employed to run a single statement, for each parallel plan execution. You can use the max degree of parallelism option to limit the number of processors to use in parallel plan execution. SQL Server considers parallel execution plans for queries, index data definition language (DDL) operations, and static and keyset-driven cursor population.
Read this for more details
http://technet.microsoft.com/en-us/library/ms189094.aspx

How to fix it ?

  1. Open Microsoft SQL Server Management Studio
  2. Login with sysadmin user
  3. Right Click on instance name and select properties >> Advanced
  4. Change Max Degree of Parallelism to 1
  5. Restart the SQL Service