Sharepoint Blogs

Monday, October 21, 2013

Category: SharePoint 2010

To see which build your farm is, go to Central Administration > System Settings > Manage servers in your farm (/_admin/FarmServers.aspx)
Or using Windows PowerShell: (get-spfarm).buildversion
To see which build your products are, go to Central Administration > Upgrade and Migration > Check Product and patch installation status. (/_admin/PatchStatus.aspx)
To see which build your databases are, go to Central Administration > Upgrade and Migration > Review database status (/_admin/DatabaseStatus.aspx)
Patch terminology KB article.
Follow SP2010Patches on Twitter for immediate updates when this list changes or I add a regression to a patch.
ShortURL: http://www.toddklindt.com/sp2010builds

Build	Release	Component	Information	Download Link	Notes
14.0.4763.1000	RTM	All components		Download
14.0.4762.1000	RTM	Farm Build Version

14.0.5114.5003	June 2010 CU	SharePoint Foundation 2010		KB2028568
14.0.5114.5003	June 2010 CU	Microsoft Shared Components		KB2281364
14.0.5114.5003	June 2010 CU	Microsoft SharePoint Portal		KB983497
14.0.5114.5003	June 2010 CU	Microsoft User Profiles
14.0.5114.5003	June 2010 CU	Microsoft Search Server 2010 Core
14.0.5114.5003	June 2010 CU	Microsoft Web Analytics Web Front End Components		KB2204024

14.0.5123.5000	August 2010 CU	SharePoint Foundation 2010		KB2352346
14.0.5123.5000	August 2010 CU	SharePoint Server 2010		KB2352342

14.0.5128.5000	October 2010 CU	SharePoint Foundation 2010		KB2394323
14.0.5128.5000	October 2010 CU	SharePoint Server 2010		KB2394320

14.0.5130.5002	December 2010 CU	SharePoint Foundation 2010		KB2459125
14.0.5130.5002	December 2010 CU	SharePoint Server 2010		KB2459257

14.0.5136.5002	February 2011 CU	SharePoint Foundation 2010		KB2475880
14.0.5136.5002	February 2011 CU	SharePoint Server 2010		KB2475878

14.0.5138.5000	April 2011 CU	SharePoint Foundation 2010		KB2512804
14.0.5138.5000	April 2011 CU	SharePoint Server 2010		KB2512800
14.0.5138.5000	April 2011 CU	Project Server 2010		KB2512801

14.0.6029.1000	Service Pack 1	SharePoint Server 2010	KB2460045	Download
14.0.6029.1000	Service Pack 1	Office Web Apps	KB2460073	Download
14.0.6029.1000	Service Pack 1	Project Server 2010	KB2460047	Download
14.0.6029.1000	Service Pack 1	SharePoint Foundation 2010	KB2460058	Download
14.0.6029.1000	Service Pack 1	FAST Search Server	KB2460039	Download

14.0.6105.5000	June 2011 CU Mark 1	SharePoint Server 2010		KB2536599
14.0.6105.5000	June 2011 CU Mark 1	SharePoint Foundation 2010		KB2536601
14.0.6105.5000	June 2011 CU Mark 1	Project Server 2010		KB2536590

14.0.6106.5002	June 2011 CU Mark 2	SharePoint Server 2010	KB2536599	Download	Regressions
14.0.6106.5002	June 2011 CU Mark 2	SharePoint Foundation 2010	KB2536601	Download
14.0.6106.5002	June 2011 CU Mark 2	Project Server 2010	KB2536590	Download
14.0.6105.5000	June 2011 CU	Office Web Apps	KB2553919	Download

14.0.6109.5002	August 2011 CU	SharePoint Server 2010	KB2553048	Download	Regressions
14.0.6109.5000	August 2011 CU	SharePoint Foundation 2010	KB2553117	Download
14.0.6109.5000	August 2011 CU	Project Server 2010	KB2553047	Download
14.0.6109.5000	August 2011 CU	FAST Search Server	KB2553040	Download

14.0.6112.5000	October 2011 CU	SharePoint Server 2010	KB2596505	Download	Bugs, Notes, and Regressions
14.0.6112.5000	October 2011 CU	SharePoint Foundation 2010	KB2596508	Download
14.0.6112.5000	October 2011 CU	Project Server 2010	KB2596506	Download

14.0.6114.5000	December 2011 CU	SharePoint Server 2010	KB2597014	Download	Bugs, Notes and Regressions
14.0.6114.5000	December 2011 CU	SharePoint Foundation 2010	KB2596998	Download
14.0.6114.5000	December 2011 CU	Project Server 2010	KB2597015	Download

14.0.6117.5002	February 2012 CU	SharePoint Server 2010	KB2597150	Download	Bugs, Notes and Regressions
14.0.6117.5002	February 2012 CU	SharePoint Foundation 2010	KB2597132	Download
14.0.6117.5002	February 2012 CU	Project Server 2010	KB2597152	Download
14.0.6117.5002	February 2012 CU	Office Web Apps	KB2598022	Download
14.0.6117.5002	February 2012 CU	FAST Search Server	KB2597131	Download

14.0.6120.5000	April 2012 CU Mark1	SharePoint Server 2010			Removed
14.0.6120.5000	April 2012 CU Mark1	SharePoint Foundation 2010			Removed
14.0.6120.5000	April 2012 CU Mark1	Project Server 2010			Removed
14.0.6120.5000	April 2012 CU	FAST Search Server	KB2598329	Download

14.0.6120.5006	April 2012 CU Mark 2	SharePoint Server 2010	KB2598151	Download	Bugs, Notes, and Regressions
14.0.6120.5006	April 2012 CU Mark 2	SharePoint Foundation 2010	KB2598321	Download
14.0.6120.5006	April 2012 CU Mark 2	Project Server 2010	KB2598152	Download

14.0.6123.5002	June 2012 CU	SharePoint Server 2010	KB2598354	Download	Bugs, Notes, and Regressions
14.0.6123.5002	June 2012 CU	SharePoint Foundation 2010	KB2598373	Download
14.0.6123.5002	June 2012 CU	Office Web Apps	KB2687273	Download
14.0.6123.5002	June 2012 CU	Project Server 2010	KB2598355	Download

14.0.6126.5000	August 2012 CU	SharePoint Server 2010	KB2687353	Download	Bugs, Notes, and Regressions
14.0.6126.5000	August 2012 CU	SharePoint Foundation 2010	KB2687355	Download
14.0.6126.5002	August 2012 CU	Project Server 2010	KB2687354	Download

14.0.6129.5003	October 2012 CU	SharePoint Server 2010	KB2687564	Download	Bugs, Notes, and Regressions
14.0.6129.5000	October 2012 CU	SharePoint Foundation 2010	KB2687566	Download
	October 2012 CU	Office Web Apps	KB2687562	Download
	October 2012 CU	Project Server 2010	KB2687615	Download
	October 2012 CU	FAST Search Server	KB2760395	Download

14.0.6131.5003	December 2012 CU	SharePoint Server 2010	KB2596955	Download	Bugs, Notes, and Regressions
14.0.6131.5001	December 2012 CU	SharePoint Foundation 2010	KB2596957	Download
14.0.6131.5003	December 2012 CU	Project Server 2010	KB2596956	Download
14.0.6131.5001	December 2012 CU	Office Web Apps	KB2726912	Download

14.0.6134.5000	February 2013 CU	SharePoint Server 2010	KB2767793	Download	Bugs, Notes, and Regressions
14.0.6134.5000	February 2013 CU	SharePoint Foundation 2010	KB2760791	Download
14.0.6134.5000	February 2013 CU	Project Server 2010	KB2767794	Download

14.0.6134.5003	February 2013 COD	SharePoint Server 2010	Blog Post	Download	Bugs, Notes, and Regressions

14.0.6137.5000	April 2013 CU	SharePoint Server 2010	KB2775353	Download	Bugs, Notes, and Regressions
14.0.6137.5000	April 2013 CU	SharePoint Foundation 2010	KB2794728	Download
14.0.6137.5000	April 2013 CU	Project Server 2010	KB2775426	Download
14.0.6137.5000	April 2013 CU	FAST Search Server	KB2794672	Download

14.0.7011.1000	SP2 Public Beta	SharePoint 2010		Download	Bugs, Notes, and Regressions

14.0.7015.1000	Service Pack 2	SharePoint Server 2010	KB2687453	Download	Bugs, Notes, & Regressions
	Service Pack 2	SharePoint Foundation 2010	KB2687464	Download
	Service Pack 2	Project Server 2010	KB2687452	Download
	Service Pack 2	Office Web Apps	KB2687470	Download
	Service Pack 2	FAST Search Server	KB2687446	Download

14.0.7102.5000	June 2013 CU Mark 1	SharePoint Server 2010	KB2817363	Download	Bugs, Notes, and Regressions
14.0.7102.5000	June 2013 CU Mark 1	SharePoint Foundation 2010	KB2817392	Download
14.0.7102.5000	June 2013 CU Mark 1	Project Server 2010	KB2817368	Download


14.0.7102.5004	June 2013 CU Mark 2	SharePoint Server 2010	KB2817527	Download	Bugs, Notes, and Regressions
	June 2013 CU Mark 2	SharePoint Foundation 2010	KB2817552	Download
	June 2013 CU Mark 2	Project Server 2010	KB2817530	Download

14.0.7106.5000	August 2013 CU	SharePoint Server 2010	KB2817570	Download	Bugs, Notes, and Regressions
	August 2013 CU	SharePoint Foundation 2010	KB2817594	Download
	August 2013 CU	Project Server 2010	KB2817573	Download

14.0.7106.5002	August 2013 CU Mark 2	SharePoint Server 2010	KB2825949	Download	Bugs, Notes, and Regressions

14.0.7110.5000	October 2013 CU	SharePoint Server 2010	KB2825786	Download	Bugs, Notes, and Regressions
	October 2013 CU	SharePoint Foundation 2010	KB2825824	Download
	October 2013 CU	Project Server 2010	KB2825793	Download

110 Comment(s)

Migration Issue - Content Database is in compatibility range and upgrade is recommended?

I recently had to recover from a disaster with one of our SharePoint testing environments. (This happens to be the only testing environment that is not on virtual hardware.) Fortunately, I do quality assurance testing for a disaster recovery product and it wasn’t long before I had new hardware for the failing database server and could rebuild the farm. I did run into some interesting issues however. After I reinstalled the WFEs and had central administration working again, I reattached the content databases that I had recovered. After all of this my farm worked fine and I had access to all of my Site Collections again. Disaster averted. The health analyzer on the farm kept warning me about upgrading databases though. Specifically the error message that I got was the following; "Database is in compatibility range and upgrade is recommended." Seems simple enough. There are Powershell commands that I can use to upgrade the databases.
$contentdb = Get-SPContentDatabase | Where-Object {$_.Name -eq "WSS_Content"}
Upgrade-SPContentDatabase -Identity $contentdb
I ran those commands from a Powershell prompt (the SharePoint 2010 Management Shell since that one automatically loads the SharePoint snap-in.) I was then immediately irritated when the upgrade failed.
WARNING: Database [SPContentDatabase Name=WSS_Content] does not need to be upgraded.
So, Central Administration tells me that my database needs to be upgraded, and then when I try to update the database, it tells me that it doesn’t need to be upgraded. I was a little confused. I figured I would try a different approach, so I ran PSConfig on the farm with the “build to build” switch.
psconfig -cmd upgrade -inplace b2b -wait -force
This only resulted in more errors.
I then tried to detach and reattach the content databases, since, when attaching a content db, SharePoint should typically upgrade the database if it needs it. That didn’t work either.
I talked with Sean McDonough for a few minutes about the situation and he enlightened me that there is a chance that it is not my content databases that need upgrading. How do you really know though? Time to poke into your content databases to tell for sure. The first database you need to check is your SharePoint Config database since that is the one that shows you what version your farm is currently using, be it a service pack, or one of the myriad cumulative updates. Run the following in a Sequel Server Management Studio Query.
use SharePoint_Config
SELECT Version
FROM Versions
WHERE VersionId = ’00000000-0000-0000-0000-000000000000′
ORDER BY Id DESC
This will show you every version that your farm has evolved through. Mine showed one version; 14.0.4762.1000. (This is incidentally the RTM version of SharePoint 2010) I then ran the same query against one of my databases that supposedly needed to be upgraded and found more than one version. 4762 was there, but so was 5128. It would seem that it wasn’t my content databases that needed to be upgraded, but rather the rest of my farm. Now my problem was figuring out which version I needed to end up with after upgrading. Fortunately, Todd Klindt has an awesome reference page here that will tell you which Service Pack or Cumulative Update each version number means with a link to download what you need. I downloaded the Cumulative Update for October 2010, installed it on my farm, and then ran psconfig again to finish everything up. All of those “database needs upgrade” errors were gone and the health analyzer on my farm settled down again. Just to be sure I went to the Farm’s Central Administration, then to “Upgrade and Migration” and clicked on “Review Database status.” Every database stated “No Action required” instead of the upgrade message.
So, if you have to recover a farm and reattach your databases, or you are attaching your content databases to a new farm, keep in mind that if SharePoint tells you that databases need to be upgraded, it might not be the databases that are in need of an upgrade.
Many thanks to Sean McDonough for his input, and to Todd Klindt for his blog for reference.

Monday, July 29, 2013

Sharepoint Patches Issues in Index Server

Issue

Unable to install the security patches , it gives , and error " Installation is not detected " We are trying to install KB2810059 , KB2760408 , KB2760777

Product / Version / Service Pack: SP 2010

Operating System / Service Pack: win 2008 R2

Farm Configuration: 14.0.6137.5002

Database Used:

Additional technologies:

Resolution

Once we are able to install the above mentioned patches on the STG Index server ,and complete the configuration wizard , we will consider this case to be resolved.

Troubleshooting Done

Ø Created the EA

Ø When we are trying to install the patches, we are getting error, installation is not detected.

Ø The patches were installed successfully on the other server of the farm

Ø We earlier tried to remove the server from the farm from CA

Ø We ran the configuration wizard , and removed the server from the farm

Ø We ran the ROI scan , and got the o/p

Review Items

============

Error: Product {90140000-1140-0411-1000-0000000FF1CE} - Microsoft Office Web Apps Shared Coms Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509144.msi

Error: Product {90140000-1080-0411-1000-0000000FF1CE} - Microsoft Shared Coms Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509152.msi

Error: Product {90140000-1080-0409-1000-0000000FF1CE} - Microsoft Shared Coms English Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\250904c.msi

Error: Product {90140000-10B0-0411-1000-0000000FF1CE} - Microsoft Project Server Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\250913d.msi

Error: Product {90140000-1103-0411-1000-0000000FF1CE} - Microsoft Document Lifecycle Components Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\25091a7.msi

Error: Product {90140000-1103-0409-1000-0000000FF1CE} - Microsoft Document Lifecycle Components English Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509098.msi

Error: Product {90140000-1123-0000-1000-0000000FF1CE} - Microsoft Access Services Server: Local cached .msi appears to be missing: C:\Windows\Installer\2509101.msi

Error: Product {90140000-10F3-0000-1000-0000000FF1CE} - Microsoft Visio Services Web Front End Components: Local cached .msi appears to be missing: C:\Windows\Installer\25090e6.msi

Error: Product {90140000-1014-0000-1000-0000000FF1CE} - Microsoft SharePoint Foundation 2010 Core: Local cached .msi appears to be missing: C:\Windows\Installer\25090a8.msi

Error: Product {90140000-1144-0000-1000-0000000FF1CE} - Microsoft Office Web Apps Web Front End Components: Local cached .msi appears to be missing: C:\Windows\Installer\25091ed.msi

Error: Product {90140000-1015-0411-1000-0000000FF1CE} - Microsoft SharePoint Foundation 2010 1041 Lang Pack: Local cached .msi appears to be missing: C:\Windows\Installer\250914a.msi

Error: Product {90140000-1015-0409-1000-0000000FF1CE} - Microsoft SharePoint Foundation 2010 1033 Lang Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509021.msi

Ø We see lot of missing installer file , we tried to install the same from a working server

Ø Cscript Oputil.vbs /repaircache /srestorelocation=\\servername\c$\windows\installer

Ø After which the same got copied successfully

Ø We ran the config wizard , which was successful with some error.

Ø We checked the upgrade log and it was referencing to a content database

Ø We detached the content database , and ran the upgrade , we still got some error about the logs been full in the database

Ø We changed the recovery model from simple full

Ø Ran the configuration wizard and it was successful.

Additional Information

http://blogs.technet.com/b/patrick_heyde/archive/2010/08/30/sharepoint-2010-patching-upgrade-part-2-which-patch-level-build-level-is-installed-amp-what-s-their-history.aspx

http://technet.microsoft.com/en-us/library/ff607813.aspx

USER PROFILE CONFIGURATION IN PRODUCTION SERVER

In the previous implementation, the profile import job, that was carried out during SharePoint user profile service had some inconsistencies due to which the address book on SharePoint showed up mixed names like instead of displaying . This operation is required to fix the same. This task does not require any outage and can be included within the same nightly batch job.

SharePoint 2010 Production Server User Profile Services Configuration Steps

Note: Before going to make any change in User Profile Application first disabled the My Sites Scheduler from Central Administration Monitoring.

Step 1: Login to the SharePoint 2010 Production Application Server.

Server Name: SharePoint Application Server

Step 2: Open the Central Administration à Go to “Application Management” à Click “Manage Service Application” à Click “User Profile Service Application”

Step 3: In “User Profile Service Application” à Click “Configure Synchronization Connections” under “Synchronization”

Step 4: Delete Existing Connect ion.

Note: If unable to delete the use below command to delete the Connection.

1. PS C:\Users\ServiceAccount> Get-SPDatabase > C:\Database.txt

2. PS C:\Users\ServiceAccount> $syncdb=Get-SPDatabase

Note: Find out Sync database name using first command path

3. PS C:\Users\ServiceAccount>$syncdb.Unprovision()

4. PS C:\Users\ServiceAccount>$syncdb.Status='Offline'

5. PS C:\Users\ServiceAccount>$upa=Get-SPServiceApplication

Note: Using Get-SPServiceapplication command to find out user profile application ID

6. PS C:\Users\ServiceAccount> $upa.ResetSynchronizationMachine()

7. PS C:\Users\ServiceAccount> $upa.ResetSynchronizationDatabase()

8. PS C:\Users\ServiceAccount> $syncdb.Provision()

Step 5: Change NetBIOS Setup from False to true

1. Using below Power Shell command to find out User Profile Application Name.

Command: PS C:\Users\ServiceAccount> Get-SPServiceapplication

2. Using below command to find out Netbios setup true or False.

Note: If output false then using PS command to change.

PS C:\Users\ServiceAccount> (Get-SPServiceApplication ).NetBIOSDomainnamesEnabled

3. PS C:\Users\ServiceAccount> $upsa = Get-SPServiceApplication -Id

4. PS C:\Users\ServiceAccount> $upsa.NetBIOSDomainNamesEnabled=1

5. PS C:\Users\ServiceAccount> $upsa.Update()

6. PS C:\Users\ServiceAccount> (Get-SPServiceApplication ).NetBIOSDomainnamesEnabled

Step 6: Stop and Start the User Profile Synchronization Service

1. Go to Central Administration à Click “Manage Services and Server” under System Settings

2. Stop and Start the “User Profile Synchronization Service” Services.

Step 7: Create the new Connection in User Profile Services

1. Go to the User Profile Application (Refer Step 1)

2. Click “Create New Connection” and parameter information as below.

1.1 Connection Name – DOMAIN NAME

1.2 Forest name: ********

1.3 Specify a domain controller: DomainName.corp.nai.org

1.4 Account Name: DomainName\ServiceName

1.5 Account Password: xxxxxxxxx

3. Click to “Populate Containers”

4. Find out NAI and select and uncheck Windows7.0 Machines.

5. Finally Click Ok

Step 8: Back to the User Profile Application Page and click Start Full Profile Synchronization.

Step 9: Two times you have complete the full start Profile Synchronization and one time Incremental.