Office documents open in read-only mode in Sharepoint

Office documents open in read-only mode in SharePoint

Issue: I have a SharePoint 2013 installation and clients with IE 11 and Office 2013. When clients navigate to a document library and click to open an Office document, the document opens in read-only mode with an information bar stating "We opened this document read-only from the server" and with a button to enable editing.

Cause: there could be many reasons for the issue like Not having proper permission to user to Edit DOC in site, IE compatibility issues, Client system issues.

Solution: I am providing the solutions below to solve the problem. Ensure one should resolve the issue.

Solution 1:Ensure the user is having a proper permissions on the site to edit the documents at least the contribute.

Solution 2:Ensure the IE is in compatible with the SharePoint and no issues with the IE.IE11 having some compatible issues with the SharePoint so I would recommend to check with other browsers.

Solution 3:please follow the steps below in client computer to resolve the issue.

1.    On the client computer experiencing the issue click on "RUN" then type "RegEdit".

2.    go to this path HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\14.0\Common\Internet

Note:For sharepoint 2013 the path is 15.0
 

3.    Right click and create new "DWORD" entry and give it a name of "FSSHTTPOff"

4.    Double click the new entry and enter 1 for the value.

5.    Once done you need to reboot the computer.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Content databases contain orphaned items. 'proc_SecRepairOrphanRoleAssignments'

 Content databases contain orphaned items. 'proc_SecRepairOrphanRoleAssignments'  

Issue : having an issue with the health analyzer rule 'Content databases contain orphaned items’. It seems to be no longer able to run without causing a rule execution failure and showing up under review problems and solutions. Content databases contain orphaned items. 

Error in Health Analyzer:

Severity
0 - Rule Execution Failure  

Category
Availability  

Explanation
Procedure or function 'proc_SecRepairOrphanRoleAssignments' expects parameter '@fix', which was not supplied.

Remedy 
Enabling automatic repair for this rule will delete the orphaned items. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142694".

Cause: The issue seems to be the bug from April CU 2014 for SharePoint 2013.

Solution: The fix for the issue available with the Sept-CU 2014 released for SharePoint 2013.

Install the Sept-CU to fix the issue. Download the CU from below link.

  http://expertsharepoint.blogspot.de/2014/09/september-2014-cu-for-sharepoint-2013.html

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation

Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation

Issue: After installing SharePoint 2013 Server Service Pack 1, I cannot open my sites. Also the Central Admin isn't working 100%.I cannot open 'Manage Service Applications' . The upgrade also end with an error message. When I open the SharePoint Management shell it shows the below error. 

Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.


Cause: This could of missing binaries of SP1.

Solution: This issue could be of many reasons, In this article I am providing the most common to check.

Solution 1:Ensure to have disk space available on the Drives of server.

Solution 2: Ensure to check the below for confirmation.

1.   Go to C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SharePoint.WorkflowServices\v4.0_15.0.0.0__71e9bce111e9429c\-> Right click on the DLL and go to Details. Ensure the File version should be as below(15.0.4569.1501)

                        

2.   Check in the Control Panel -> Programs and Features -> View Installed Updates->SP1,If it’s not there.

Re-install the SP1 to that problem server

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

The operation cannot be performed on database "WSS_UsageApplication .

The operation cannot be performed on database "WSS_UsageApplication .

Issue: The operation cannot be performed on database "WSS_UsageApplication" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.  ALTER DATABASE Statement failed.

Description: The issue occurrers when we install the CU for SharePoint 2013 and runs the PSconfig.PSCONFIG failed with an error. When we check the Upgrade log we see the error” The operation cannot be performed on database "WSS_UsageApplication"

Solution: As In my environment we put the WSS_UsageApplication under high availability. Once, I removed it from the high availability group and run the PSconfig it worked successfully.

Ensure to  remove “WSS_UsageApplication” from the availability group before applying a CU and add it when the upgraded is completed if necessary.

Ensure  to remove “WSS_UsageApplication” under high availability from the Primary node only.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.