November 2014 CU for SharePoint 2013 has been released

November 2014 CU for SharePoint 2010 has been released

The product group released the November 2014 Cumulative Update for the SharePoint 2010 product family.

For November 2014 CU we again have full server packages (also known as Uber packages). Unlike August 2014 CU no other CU is required to fully patch SharePoint.

Attention: this is the first CU which no longer supports SP1! It is required to have SP2 installed for the base product and all installed language packs to install this November 2014 CU for SharePoint 2010.

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

• KB 2899468 - SharePoint Foundation 2013 November 2014 CU
• KB 2889944 - SharePoint Server 2013 November 2014 CU
• KB 2889949 - SharePoint Server 2013 with Project Server November 2014 CU
• No Office Web Apps Server 2013 CU released this month

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

• Download SharePoint Foundation 2013 November 2014 CU
• Download SharePoint Server 2013 November 2014 CU
• Download Project Server 2013 November 2014 CU

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

Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
That means only one package has to be installed for the SharePoint 2010 product family.

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

 
Version : 15.0.4667.1000

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.

Excel cannot connect to the SharePoint list

Excel cannot connect to the SharePoint list

Issue: Cannot connect to the server at this time. Changes to you Data cannot be saved

Solution: Follow the below steps to resolve the issue.

1.    Open Internet Explorer

2.    Go to Tools -> Options then go to Advanced Settings.

3.    Scroll and go to the Security Section.

4.    By default "Check for publisher's certificate revocation" option is checked. Uncheck that and click on OK.

5.    Now close the browser and open the SharePoint site in a new browser window.

 


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.

Error 1935.An error occurred during the installation of assembly component

Error 1935.An error occurred during the installation of assembly component

Issue: While installing any software in windows -2012 server, we see the error below.

Error 1935.An error occurred during the installation of assembly component

{837bf1eb-d770-94eb-a01f-c8b3b9a1e18e}.

HRESULT:0x80073712

Cause: The issue is due to the missing files of Windows in the Server.

Solution: please check the solution below to resolve the issue.

1.    Check the file Components in working server and Ensure the Size is Same.If not,Copy the File from server which is working and paste in Non working server(This should follow some procedures, steps)

Path :C:/windows/system32/config

File name : COMPONENTS

2.    If not worked the above, should re-image the 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.

No exact match was found People Picker error message

No exact match was found People Picker error message

Issue: Assume that you configure a forest trust between two Active Directory forests and that the Windows Internet Name Service (WINS) is not enabled for Net Bios resolution. In this situation, People Picker in a Microsoft SharePoint Server 2010 site works fine for users in the local forest. However, for users in any domain in the trusted forest, People Picker does not work.

Additionally, People Picker finds the user account and seems to resolve it. However, when user clicks OK to post back to the site, the user receives the following error message:

No exact match was found. Click the items that did not resolve for more options

Cause: This issue occurs because, when you click OK, People Picker makes a NetBIOS call to try to resolve the domain name. Because the customer does not have WINS set up, a Net Bios broadcast occurs. However, the broadcast cannot find the trusted domains because broadcasts are not enabled outside the subnet

Solution: Please check the below link from MS

 http://support.microsoft.com/kb/2874332

 


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 permissions in SP_DATA_ACCESS role by default.

The permissions in SP_DATA_ACCESS role by default.

The SP_DATA_ACCESS role replaces the db_owner role in SharePoint 2013.

The SP_DATA_ACCESS role is the default role for database access and should be used for all object model level access to databases.

1.   Grant EXECUTE or SELECT on all SharePoint stored procedures and functions

2.   Grant SELECT on all SharePoint tables

3.   Grant EXECUTE on User-defined type where schema is dbo

4.   Grant INSERT on AllUserDataJunctions table

5.   Grant UPDATE on Sites view

6.   Grant UPDATE on UserData view

7.   Grant UPDATE on AllUserData table

8.   Grant INSERT and DELETE on NameValuePair tables

9.   Grant create table permission 

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.