December 2014 CU for SharePoint 2010 has been released

December 2014 CU for SharePoint 2010 has been released

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

For December 2014 CU we again have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

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

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

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

The KB articles for December CU will be available at the following locations 

• KB 2899585 - SharePoint Foundation 2010
• KB 2899583 - SharePoint Server 2010
• KB 2899587 - Project Server 2010

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

• Download SharePoint Foundation 2010 December 2014 CU
• Download SharePoint Server 2010 December 2014 CU
• Download Project Server 2010 December 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.

Version :  14.0.7140.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.

December 2014 CU for SharePoint 2013 has been released

December 2014 CU for SharePoint 2013 has been released

ATTENTION:

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

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.

This CU includes all SharePoint 2013 fixes released since RTM. The CU does not include SP1. You can install SP1 before or after installing this CU.

The KB articles for December CU will be available at the following 

   

• KB 2910945 - SharePoint Foundation 2013 December 2014 CU
• KB 2910938 - SharePoint Server 2013 December 2014 CU
• KB 2910911 - SharePoint Server 2013 with Project Server December 2014 CU
• KB 2899574 - Office Web Apps Server 2013 December 2014 CU

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

• Download SharePoint Foundation 2013 December 2014 CU
• Download SharePoint Server 2013 December 2014 CU
• Download Project Server 2013 December 2014 CU
• Download Office Web Apps Server 2013 December 2014 CU

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.

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.4675.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.

SQL Server Setup or Installation Failure Errors

SQL Server Setup or Installation Failure  Errors 

Issue: SQL Server 2008 R2 setup failed with “Error 1406. Could not write value to key \SOFTWARE. System error. Verify that you have sufficient access to that key, or contact your support personnel”

Run setup as Administrator
Make sure Administrator has full control on the registry key reported in the error.
This issue can happen, if there are any kind of virus/adware/malware/Addons on the system. Scan the system and fix any such issues.
There is a connect bug raised for the same, please check of there are any latest updates.
https://connect.microsoft.com/SQLServer/feedback/details/998266/could-not-write-value-to-key-software-verify-that-you-have-sufficient-access-to-that-key-or-contact-your-support-personnel

Issue: Error 997. Overlapped I/O operation is in progress during SQL Server installation

– Check the account with which you logged on to the server, make sure it is not a account with temporary profile.
– Run the Setup locally on the server and make sure you run the setup, by right-clicking on the Setup file and choose Run-As-Administrator.
– Disable any Anti-virus and reboot the server.
– Check for any problems with the disk drive where you are installing SQL Server files.

Issue: Invalid license data. Reinstall is required Error while trying to connect to SQL Server Management Studio (SSMS)

– Try to repair the SQL Server shared components(If you cannot launch the setup from control panel, use the Setup.exe from setup media.
– After repair, if it SSMS still fail with the same error, then uninstall Visual Studio 2010 or 2012 and then attempt the repair of the shared components again.

 


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.

Microsoft® SQL Server® 2012 Service Pack 2 (SP2)

Microsoft® SQL Server® 2012 Service Pack 2 (SP2) 

Download SP2  for SQL 2012 from Below link.

http://www.microsoft.com/en-my/download/details.aspx?id=43340 


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.

How to change the session timeouts in SharePoint sites

How to change the session timeouts in SharePoint sites

SharePoint  allows you to set timeout of the user session so that your users are logged out after certain time of inactivity. Also, SharePoint allows you to configure the timeout for the current page state to expire. This is handy for forms which have to be filled within certain period of time before they expire.

Alternatively, if you want to extend the timeout – you can do that.

let’s take a look at how you can expire page content after a given time using Power Shell:

Open SharePoint Management Shell as administrator and execute the following:

$SPSite = Get-SPSite("[your site collection]")

$webApp = $SPSite.WebApplication

$webApp.Enabled = $true

$webApp.Expires = $true

$webApp.Timeout = New-TimeSpan -Hours 2 -Minutes 30

$webApp.Update()

This will effectively enable expiration and set page content to expire after users leave it hanging for over 2 hours and 30 minutes.

if you’re using claims authentication and would like for your provider to expire sessions after certain period of inactivity, here is how to do that with Power Shell:

$sts = Get-SPSecurityTokenServiceConfig

$sts.UseSessionCookies = $true

$sts.LogonTokenCacheExpirationWindow = New-TimeSpan -Minutes 5

$sts.Update()

This will set our logon expiration to 5 minutes.

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.