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.

Document farm configuration settings in SharePoint 2013

Check the below link from MS which will give you details on the existing farm. This would be useful when we are building up the Replicas of farm.

 

 http://technet.microsoft.com/en-us/library/ff645391%28v=office.15%29.aspx

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.

Is possible to attach the same Content DB in two sites in Same farm

Is possible to attach the same Content DB in two sites in Same farm.

Issue: I am getting many questions from the SharePoint community that” Is possible to attach the same Content DB in two sites in Same farm”

Solution: I say answer as Yes and No.

1)   We can attach but, The expected behavior as the Site Collections have the same GUID, so the second website which has same content attached  will not be able to see all data of them. In this case we can consider the below steps to overcome this.

2)   Restore the Content Database to a Web Application on another farm

3)   Use Backup-SPSite/Restore-SPSite which assigns a new GUID to the Site Collection so you can 'duplicate' it within the same farm

4)   Use Export-SPWeb/Import-SPWeb

 


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.

SharePoint Server 2013 Demo site

SharePoint Server 2013 Demo site

 

 http://www.spsdemo.com/

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.

Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)

Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)

Issue: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)

Description: once the update for windows is done, we see the error in logs:

Solution: This could be of many reasons, please find the solution from MS.

Solution 1 : http://support.microsoft.com/kb/2557533

solution 2: Please try to add <trust level =”Full”/> to the application web.config file, and do iisreset to check whether it works

Solution 3: https://support.microsoft.com/kb/2282372?wa=wsignin1.0

Solution 4 : first stop the site in IIS, then clear out the ASP.NET Temporary Files folder that relate to your site (default location is under C:WindowsMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Files). Then start IIS and try browsing the site.

  
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.