Archive

Archive for June, 2015

Install SharePoint 2010 Binaries on Windows Server 2012 R2

June 25, 2015 1 comment

I was in the process of building and configuring my SharePoint 2010 Disaster Recovery (DR) Continuity of Operations (COOP) environment and ran into some issues installing the SharePoint 2010 Binaries on a Windows Server 2012 R2 OS.  My current SP2010 Production environment is running on a Windows Server 2008 R2 system, and this is the first time I attempted to install SP2010 on a Windows Server 2012 R2 platform.

First and foremost the most important piece of information.  *You cannot install any version build below SharePoint 2010 SP2 Slipstream on a Windows Server 2012 R2 platform.

This is where I made my mistake.  Not really a mistake, but more a misunderstanding on my part.

When I usually install SharePoint 2010 I tend to extract the installation files, and place the latest extracted SP/CU binaries in the “Update” folder in my SharePoint 2010 extraction location and kick off the prereq installation.  I like to manually extract and slipstream my own SP installation files.  This has worked flawlessly for me in the past so why not now?

So I did just that for this build I took the SP2010 SP2 and December 2014 CU binaries and moved these files over to my Windows Server 2012 R2 environment, and kicked off the PrerequisiteInstaller.  The prereq immediately failed with a Configuration Error for Application Server Role, Web IIS role.  Everything else checked out “ok” with the PrerequisiteInstaller.  I then decided to manually install the Application Server Role and Web IIS role through Server Manager, and kick off the prereq installer again.  It immediately failed again with the same error.

Taking a look at the prereq log file it was pointing me to the PreXXX.xml file that was failing to execute located at:  c:\users\<username>\AppData\Local\Temp.

Opening up this file it lists all the required Application and IIS roles that need to be installed and configured for SharePoint 2010 to work.

For those that are interested in what Application and IIS Roles are needed I’ve listed them below:

<Feature Id=”Net-Framework”/>
<Role Id=”Web-Server”/>
<RoleServer Id=”Web-WebServer”/>
<RoleServer Id=”Web-Common-Http”/>
<RoleServer Id=”Web-Static-Content”/>
<RoleServer Id=”Web-Default-Doc”/>
<RoleServer Id=”Web-Dir-Browsing”/>
<RoleServer Id=”Web-Http-Errors”/>
<RoleServer Id=”Web-App-Dev”/>
<RoleServer Id=”Web-Asp-Net”/>
<RoleServer Id=”Web-Net-Ext”/>
<RoleServer Id=”Web-ISAPI-Ext”/>
<RoleServer Id=”Web-ISAPI-Filter”/>
<RoleServer Id=”Web-Health”/>
<RoleServer Id=”Web-Http-Logging”/>
<RoleServer Id=”Web-Log-Libraries”/>
<RoleServer Id=”Web-Request-Monior”/>
<RoleServer Id=”Web-Http-Tracing”/>
<RoleServer Id=”Web-Security”/>
<RoleServer Id=”Web-Basic-Auth”/>
<RoleServer Id=”Web-Windows-Auth”/>
<RoleServer Id=”Web-Filtering”/>
<RoleServer Id=”Web-Digest-Auth”/>
<RoleServer Id=”Web-Performance”/>
<RoleServer Id=”Web-Stat-Compression”/>
<RoleServer Id=”Web-Dyn-Compression”/>
<RoleServer Id=”Web-Mgmt-Tools”/>
<RoleServer Id=”Web-Mgmt-Console”/>
<RoleServer Id=”Web-Mgmt-Compat”/>
<RoleServer Id=”Web-Metabase”/>
<Role Id=”Application-Server”/>
<RoleServer Id=”AS-Web-Support”/>
<RoleServer Id=”AS-TCP-Port-Sharing”/>
<RoleServer Id=”AS-WAS-Support”/>
<RoleServer Id=”AS-HTTP-Activation”/>
<RoleServer Id=”AS-TCP-Activation”/>
<RoleServer Id=”AS-Named-Pipes”/>
<RoleServer Id=”AS-Net-Framework”/>
<Feature Id=”WAS”/>
<Feature Id=”WAS-Process-Model”/>
<Feature Id=”WAS-Net-Environment”/>
<Feature Id=”WAS-Config-APIs”/>

I then thought….maybe I missed some required roles or features so I created a PS Script to install all the missing roles and features.  **I will blog on how to create this script later, but for this issue this script is not needed.

After installing the missing roles and features I again kicked off the prereq installer.  Yet again another failed attempt.  At this time I’m scratching my head.

I then took a look at the Event Viewer and saw this warning in the Application log:

“The application (Microsoft SharePoint Server 2010, from vendor Microsoft) has the following problem:  You must install Microsoft SharePoint Server 2010 with the most recent service pack.  Microsoft SharePoint Server 2010 without service packs has a known compatibility issue with this version of Windows.”

HUH!? But I do have the latest service pack (SP2) slipstreamed so why am I getting this message?

Come to find out all I actually needed to do was download the SharePoint 2010 SP2 bundled Package executable to successfully install and configure SharePoint 2010 SP2 on Windows Server 2012 R2.  You can download the executable at Microsoft. http://www.microsoft.com/en-us/download/details.aspx?id=24983

What upset me was there was no where that I read that mentioned that I needed to use this package.  I assumed that my SP2 slipstream would work just fine, nor did I know that the prereq installer needed to be ran from the SharePoint 2010 SP2 bundled package executable as well.

This would have saved me tons of time and eliminated my troubleshooting steps.

After I ran the executable I was then able to successfully complete the prereq checks and install the SP2010 SP2 binaries.

So if you run into a similar situation, just download the SharePoint 2010 SP2 binaries from Microsoft http://www.microsoft.com/en-us/download/details.aspx?id=24983 and you should then be able to install SharePoint 2010 SP2 on a Windows Server 2012 R2 platform  successfully without having to do any extra configuration.

====UPDATE====

The SharePoint 2010 SP2 Binaries link I provided is only good for SharePoint 2010 Foundation.  If you are looking to upgrade / install SharePoint 2010 SP2 Enterprise Edition you will have to download the binaries from either MSDN (https://msdn.microsoft.com/en-us/default.aspx) or Microsoft Volume Licensing Service Center (https://www.microsoft.com/Licensing/servicecenter/default.aspx).

 

===Update====

If you have Office Web Apps deployed you will need to do the same here as well.  Grab the latest Office Web Apps SP2 package from MSDN or Microsoft Volume Licensing Service Center.

SharePoint 2010: Cannot upgrade because Updates are missing.

June 9, 2015 Leave a comment

I recently ran into some issues when trying to upgrade my SharePoint 2010 Farm with the latest SharePoint 2010 Cumulative Update.   The last time I updated my SharePoint 2010 farm was back in October of 2013 so its was time for a much needed upgrade.

Following the same process I usually take when upgrading I first install the latest CU’s bits on my CA Server, then remove one WFE at a time out of the load balancer and lay the bits on them.  This helps to prevent downtime of the portal when applying.  Once all the bits are installed I run the config wizard on the CA Server first, and then follow the same process (remove WFE server from load-balancer) and then run the Config wizard on that server until all servers in the farm are patched.

For this scenario I was installing the latest Sept 2014 Cumulative Update bits on all my WFE servers, but for whatever reason even though the installation was successfully on the servers within (Central Administration -> Manage Patch Status) I noticed that two of my WFE servers were still showing missing CU patches, but on the physical server itself I see that the updates were applied.  When trying to reinstall the latest Sept 2014 CU on the server I get the message that “There are no products affected by this package installed on this system”.

I then attempted to run the Config Wizard to maybe see if for some reason CA was reporting incorrectly, but as expected the Config Wizard returned saying that patches were missing on the two servers and can’t continue until those servers were patched.

So now I’m stuck.  My WFE servers show the CU patches installed but SharePoint does not see them so I can’t continue with the upgrade.

To fix this problem you simply just need to run a single PowerShell command on each WFE that Central Administration is stating is missing the patches.

On each WFE server open up SharePoint 2010 Management Shell and type this command:

Get-SPProduct -Local

After running this command on each WFE server you can now run the Config Wizard.  This time it should complete successfully.

Hopefully this helps others who run into a similar situation.