September 2014 CU for SharePoint 2010 has been released

September 2014 CU for SharePoint 2010  has been released

The KB articles for September CU will be available at the following locations in a couple of days:

• KB 2889932 - SharePoint Foundation 2010
• KB 2883103 - SharePoint Server 2010
• KB 2883006 - Project Server 2010

The Full Server Packages for September 2014 CU are available through the following links:

• Download SharePoint Foundation 2010 September 2014 CU
• Download SharePoint Server 2010 September 2014 CU
• Download Project Server 2010 September 2014 CU

Note:

1.     Be aware that the September Cumulative Update for SharePoint 2010 is a Post-SP2 hot fix. It is recommended to have SP2 installed before installing the September CU.

2.     This CU includes all SharePoint 2010 fixes released since SP1. The CU does not include SP2.

3.     After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

4.     Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.

5.     That means only one package has to be installed for the SharePoint 2010 product family.

Build Version: This is build 14.0.7132.5000

 


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.

September 2014 CU for SharePoint 2013 has been released

September 2014 CU for SharePoint 2013 has been released

The Full Server Packages for September 2014 CU are available through the following links:

1.       Download SharePoint Foundation 2013 September 2014 CU

2.       Download SharePoint Server 2013 September 2014 CU

3.       Download Project Server 2013 September 2014 CU

Note:

1.    Be aware that all Update for SharePoint 2013 require SharePoint Server 2013 SP1 OR March 2013 PU for SharePoint 2013 to be installed first.

2.    Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hot fix Download Available link in the KB article for the release.

3.    After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.

4.      Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.

Build Version: This is build 15.0.4649.1001 

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.

SQL remote blob storage must be installed on each web front end server and on the content database before it may be used

 SQL remote blob storage must be installed on each web front end server and on the content database before it may be used.

Issue: unable to create content database to use RBS with FILE STREAM in SharePoint 2013

Solution: While enabling Remote Blob Storage on SharePoint servers, we need to run these Power Shell commands to enable RBS.

$cdb = Get-SPContentDatabase WSS_Content_2500  #Set you database name
$rbss = $cdb.RemoteBlobStorageSettings
$rbss.Installed()
$rbss.Enable()
$rbss.SetActiveProviderName($rbss.GetProviderNames()[0])

When you run this line $rbss.Enable(), sometimes we get error and it says, “SQL remote blob storage must be installed on each web front end server and on the content database before it may be used.”

To resolve this problem, we need to restart all servers in the Farm. After restarting, it will work like a charm.

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 crawler has insufficient permissions to crawl file shares

SharePoint Server 2013 crawler has insufficient permissions to crawl file shares

Issue: SharePoint Server 2013 crawler has insufficient permissions to crawl file shares

Solution: Please follow the below steps to resolve the issue.

1.    Click Start, click Run, type gpedit.msc, and then click OK.

2.    Navigate to the following location in the Local Group Policy Editor:

Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment

3.    In the right pane, locate and right-click Manage auditing and security log, and then click Properties.

4.    Click the Add User or Group button in the Manage auditing and security log properties dialog box, and then add the crawl account that the SharePoint 2013 crawler uses.

5.    Click OK in the Manage auditing and security log properties dialog box.

Note: If you assign the Manage Auditing And Security Log permission by using a Group Policy Object (GPO), add the crawl account to the GPO.

 


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.