Installing SharePoint 2013 on Hyper V for development (some gotchas)

Yesterday I was sitting trying to prepare a SharePoint 2013 development environment. I try to install and patch all software.

This is not a complete install guide. For a complete installation guide I recommend this one (http://blog.anuragg.com/2012/12/install-and-configure-sharepoint-server_25.html) or this one (http://nakedalm.com/install-sharepoint-2013-on-windows-server-2012-without-a-domain/) if you don’t have or want to setup a AD. Instead its some notes about whats needed and the some challenges I had during the process.

The software you need is Windows server 2012 r2, Visual Studio 2013, MS SQL server 2012 SP1 and SharePoint 2013 SP1. Its important that you have the SharePoint 2013 with sp1 since its the lowest version supported to install on windows server 2012 r2.

So here is a list of some gotchas to look out for.

1. During installation make sure that the virtual machine has at least 2 virtual processor
2. Turn off dynamic memory handling during installation and make sure that is has
at least 8Gb of memory.
3.  After installing the SQL server, set Max Degree of Parallelism to 1.

If you done all this and still get the message “SharePoint Server 2013 encountered an error during setup” then there is one last thing you can try! This is NOT ever recommended for a production environment.

1. Before exiting setup, examine the log file in \users\{user}\appdata\local\temp\sharepoint server*.log.
2. See if there is an error where ARPWRITE returns result code 3
3. If so, download the ORCA tool from the Windows SDK (ORCA allows you to modify MSI files)
4. Copy the installation from the DVD to a local folder.
5. In Explorer, locate the global\oserver.msi file in your SharePoint 2013 install tree.
6. Right-click the MSI and specify ‘Edit with Orca’
7. Select the InstallExecuteSequence table.
8. Locate the ArpWrite action, right-click, Drop Row
9. File->Save
10. Rerun SP2013 Setup as usual.

This worked for me. What the ARPwrite does in simplified terms that it writes to the registry that SharePoint is installed. I haven’t seen any negative effects yet.

Other solutions I’ve seen and tested (but didn’t work for me) where:

*Apply KB2768703 and KB2770917 should be applied and may resolve this issue on Windows Server 2012. Although, in looking at the two the KB2768703 patch seems more related to DRM / media issues. I’d recommend trying KB2770917 first as it is a roll-up of many.
* Install office on the server.
* Change license key from Enterprise to standard.

 


Advertisements

About tomasnorin

I’m a developer that’s been working with web development for some 20 years. I have mostly been working with Microsoft Technologies
This entry was posted in SharePoint and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s