I got a question from a colleague the other day. He was sad that I could see online presence in SharePoint, but his presence icon was just a white rectangle.
The lync and SP servers are in the same domain, so there should not be any issues related to SIP adresses etc.
After some troubleshooting we discovered that it worked for me because I'd added the SharePoint URL to my Trusted Sites zone. Problem solved!
onsdag 15 oktober 2014
onsdag 1 oktober 2014
Dodging silverlight when streaming media from SharePoint 2013
I uploaded a video for my colleagues the other day to our SP2013 intranet.
Some hours later I got complaints that the video required Silverlight to play, which got all our linux and mac users to go home and cry.
Googling for a solution I found several threads talking about user agents, document types, changing browser compability mode etc etc. All of the solutions seemed way to complicated to implement. Why isnt the browser choosing HTML5?
There must be an easier solution out there, I thought.
And surely enough I just had to change the Browser File Handling option to Permissive in Web Application General Settings.
This will skip adding headers to the websites, so that the browser chooses how it should display content.
From IE9 and newer versionis of other browsers aswell, the browser will choose HTML5 over Silverlight.
Great success!
Some hours later I got complaints that the video required Silverlight to play, which got all our linux and mac users to go home and cry.
Googling for a solution I found several threads talking about user agents, document types, changing browser compability mode etc etc. All of the solutions seemed way to complicated to implement. Why isnt the browser choosing HTML5?
There must be an easier solution out there, I thought.
And surely enough I just had to change the Browser File Handling option to Permissive in Web Application General Settings.
This will skip adding headers to the websites, so that the browser chooses how it should display content.
From IE9 and newer versionis of other browsers aswell, the browser will choose HTML5 over Silverlight.
Great success!
torsdag 20 februari 2014
Connecting SP2013 to OWA2013
Hi guys,
Just managed to successfully connect my SharePoint 2013 farm to an Office Web Apps 2013 farm using SSL! Woopidoo :)
Used the following articles:
http://technet.microsoft.com/en-us/library/jj219455.aspx
http://technet.microsoft.com/en-us/library/ff431687.aspx
I had issues tho (or else I would not write this post ;) )
When trying to connect SP to OWA, I kept getting this error:
Browsing the ULS revealed the following:
Critical An operation failed because the following certificate has validation errors: Subject Name: CN=abc, O=abc, L=abc, C=abc Issuer Name: CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US Thumbprint: abc Errors: PartialChain: A certificate chain could not be built to a trusted root authority. RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate. OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline. .
EUREKA! Another lovely SSL issue.
Checking the certificate... seems fine! No errors in browser... hmmm..
Then I came to think about the revocation list and all the issues it brings to SharePoint.
Checked the policy setting just for the fun of it.
"Allow issuer certificate (AIA)" was not checcked due to "Define these policies" was not checked.
After checking both of them, i retested creating the WOPIbinding and voila - it worked! :) "Happy camper".
I just hope changing this setting won't cause any other SP issues later on...
Just managed to successfully connect my SharePoint 2013 farm to an Office Web Apps 2013 farm using SSL! Woopidoo :)
Used the following articles:
http://technet.microsoft.com/en-us/library/jj219455.aspx
http://technet.microsoft.com/en-us/library/ff431687.aspx
I had issues tho (or else I would not write this post ;) )
When trying to connect SP to OWA, I kept getting this error:
New-SPWOPIBinding -ServerName kor-st-spowa01.kor.osl.basef
arm.net
WARNING: The server did not respond. Trying again (attempt 1 of 5).
WARNING: The server did not respond. Trying again (attempt 2 of 5).
WARNING: The server did not respond. Trying again (attempt 3 of 5).
WARNING: The server did not respond. Trying again (attempt 4 of 5).
WARNING: The server did not respond. Trying again (attempt 5 of 5).
New-SPWOPIBinding : Sorry, we have encountered an error and New-SPWOPIBinding h
as failed. If you are using a server configured with HTTP, you must include the
-AllowHTTP parameter.
At line:1 char:1
+ New-SPWOPIBinding -ServerName kor-st-spowa01.kor.osl.basefarm.net
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.Share...tNewWOPIBinding
:SPCmdletNewWOPIBinding) [New-SPWOPIBinding], SPCmdletException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewWOPIB
inding
Browsing the ULS revealed the following:
Critical An operation failed because the following certificate has validation errors: Subject Name: CN=abc, O=abc, L=abc, C=abc Issuer Name: CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US Thumbprint: abc Errors: PartialChain: A certificate chain could not be built to a trusted root authority. RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate. OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline. .
EUREKA! Another lovely SSL issue.
Checking the certificate... seems fine! No errors in browser... hmmm..
Then I came to think about the revocation list and all the issues it brings to SharePoint.
Checked the policy setting just for the fun of it.
"Allow issuer certificate (AIA)" was not checcked due to "Define these policies" was not checked.
After checking both of them, i retested creating the WOPIbinding and voila - it worked! :) "Happy camper".
I just hope changing this setting won't cause any other SP issues later on...
tisdag 14 januari 2014
SharePoint 2013 Post-Installation: Missing Server side dependencies
After installing SharePoint 2013 you see the following Health Analyzer Rule:
Title Missing server side dependencies.
Severity 1 - Error
Category Configuration
Explanation
I resolved the issue by following these steps:
1. Visit the Farm Search Administration site
2. Click the shortcut links to the right on SSA site
3. Visit the pages on your other servers with Central Admin in the farm.
3. If you have stopped the SharePoint Foundation Web Application service on a server, problem can be resolved by provisioning the service again. If however you do not want the service on this service, obviously this is not a valid solution.
In my case the problem was due to provisioning Central Admin on another server (by accident) and removing the AAM to this server was not sufficient.
I had to remove the server from farm and then re-add it again. While server was out of the farm, i ran an IISRESET + resettet SP Timer service on my current CA server. Voila! Rule dissapeared.
Title Missing server side dependencies.
Severity 1 - Error
Category Configuration
Explanation
[MissingWebPart] WebPart class [8307a780-2546-f10b-551f-0e692d0fce39] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationShortcutsList] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.This issue usually occurrs when you have Central Admin on several servers and/or you have disabled the SharePoint Foundation Web Application Service on servers in the farm.
[MissingWebPart] WebPart class [63104819-a32f-88b6-ab4a-7bbd4fbb40e8] (class [Microsoft.Office.Server.Search.WebControls.FarmSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9328cc53-be2c-1cca-f310-ddd573a106a5] (class [Microsoft.Office.Server.Search.WebControls.FarmSearchApplicationList] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [4465f30a-0604-4d3c-39fd-ecdb8812f3f3] (class [Microsoft.Office.Server.Search.WebControls.SearchTopologyOverview] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [a9bc1035-cf56-e003-8a4d-fff0bb3da148] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
I resolved the issue by following these steps:
1. Visit the Farm Search Administration site
2. Click the shortcut links to the right on SSA site
3. Visit the pages on your other servers with Central Admin in the farm.
3. If you have stopped the SharePoint Foundation Web Application service on a server, problem can be resolved by provisioning the service again. If however you do not want the service on this service, obviously this is not a valid solution.
In my case the problem was due to provisioning Central Admin on another server (by accident) and removing the AAM to this server was not sufficient.
I had to remove the server from farm and then re-add it again. While server was out of the farm, i ran an IISRESET + resettet SP Timer service on my current CA server. Voila! Rule dissapeared.
Prenumerera på:
Inlägg (Atom)