SharePoint 2013: Standalone Installation Issue
Hey guys,
So the new SharePoint has arrived! Or has it? When I tried to install the standalone version of the new SharePoint Server 2013, I encountered a few issues. Let me show you the errors:
Before talking about the issues, let me first detail the setup.
- Windows Server 2012 RC
- SharePoint Server 2013
- Standalone install type
As I didn’t have a domain setup and didn’t want to install a full SQL server and , I choose for a standalone installation. This will install a SQL express instance for SharePoint to use.
Everything went pretty fine (the server vhd was a big time saver), until the configuration wizard. After 2 steps, the installation of the config db gave this error:
ErrorCode:SubStatus:
Service running under Network Service account in workgroup environment is not supported.
After reviewing the default SharePoint services, I found a reference to the AppFabric component. This service was indeed running under the NETWORK SERVICE account. After fiddling around with write permissions on the config file of the service, I managed to pass that step, only to hit another road block:
ErrorCode :SubStatus:
TCP port 22234 is already in use.
This error also related to the AppFabric component. However, when reviewing MSDN it mentioned installing the component on another machine… which I didn’t have.. and which I didn’t want. This actually gave me an idea. Instead of making each error pass, maybe instead I should just deactivate AppFabric. Distributed cache in a single environment is not really that useful.
After decompiling, I found that SharePoint, when joining the local machine to the farm, has a conditional cache host registration. This lead to further decompiling into psconfig.exe which lead me to the psconfig command variable “SkipRegisterAsDistributedCacheHost”. This means: not running the configuration wizard by clicking on it, but running it through the command prompt. Easy peasy:
PS C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>
.\PSCONFIG.EXE -cmd Configdb create SkipRegisterAsDistributedCacheHost
And just like magic, psconfig created my new config db in three wonderful steps. After this, I just needed to rerun the configuration wizard through the UI to finish off the complete configuration. (if you have an issue when creating the sample data, don’t worry too much: the central admin is up and running. You are good to go!)
And there you have it! The madness can begin, once again! Have fun discovering SharePoint 2013!
UPDATE: This little trick will deactivate AppFabric. Microsoft acknowledged the issue and are updating the info. In the meantime, be aware that some features might be disabled by applying this. (Thx Pieter) Now that the RTM bits are out, I hope the issue is solved.


July 17th, 2012 at 23:50
Thanks – worked a dream.
July 18th, 2012 at 0:00
[...] the the AppFrabic caching service. Well, “TomBlog””s already sorted the problem: http://tomblog.insomniacminds.com/2012/07/17/sharepoint-2013-standalone-installation-issue/comment-p…. Thanks – great work. Like this:LikeBe the first to like [...]
July 18th, 2012 at 0:22
Thanks man…This is exactly what i was looking for because i was running into the same issue.
The only thing that slipped my mind and you didn’t have in there is they need to run the PS with Admin Credentials…
Of course everyone should already know this,,i did,,but i had forgot until i got the error….
Anyways..im all good now… Thanks again
July 18th, 2012 at 0:44
Thanks, it saved me a lot of time.
July 18th, 2012 at 1:15
Thanks a lot! That did the trick in my environment as well!
July 18th, 2012 at 1:47
I had the same problem earlier, thanks for posting your solution!
July 18th, 2012 at 10:07
I had exactly the same issue, thx for the fix!
July 18th, 2012 at 21:01
[...] fresco si lo he hecho, y rápidamente he encontrado como solucionarlo tal y como se describe aquí: http://tomblog.insomniacminds.com/2012/07/17/sharepoint-2013-standalone-installation-issue/comment-p…. Vamos, que en el lugar de ejecutar el asistente de configuración de forma convencional lo [...]
July 18th, 2012 at 22:27
[...] searching and I found that a couple of other people have already run into this and solved it. Here is the best explanation I found. The error is for the AppFabric caching component. Once I followed the steps Tom lays [...]
July 19th, 2012 at 6:59
Amazing, worked like charm for me
July 24th, 2012 at 20:08
You’re the man, thanks for this.
July 25th, 2012 at 4:00
Thanks. This was invaluable.
July 25th, 2012 at 19:14
Hi – I came across this blog post, and I wanted to try to give some additional clarification. I’m a Supportability Program Manager at Microsoft for SharePoint, and we wanted to clarify the following (documentation will be updated in the next week or so).
- SharePoint 2013 Preview is not supported in workgroup environments or on domain controllers.
- The workaround of disabling velocity will limit the functionality and prevent full evaluation of all features.
I’d recommend standing up a domain controller separately, join the SharePoint server to the domain, then install SharePoint.
As I said, we’re updating our documentation now, but I stress that it’s important that people not disable the service as suggested earlier in the comments.
July 25th, 2012 at 22:31
Thanks Tom, this is exactly what I was looking for!
August 1st, 2012 at 8:29
[...] SharePoint 2013: Standalone Installation Issue [...]
August 1st, 2012 at 14:56
Really helpful thanks.
It wasn’t clear in your code sample that the commands were two separate lines (as I really don’t use PowerShell that often) but excellent advice and has saved me from giving up.
August 6th, 2012 at 22:33
[...] I could think of (including a full reinstall) I put my hopes on google. It turned out that someone encountered the same issue before me. The solution is pretty simple: create the configuration [...]
August 6th, 2012 at 23:03
Great post, super helpful, thanks
September 6th, 2012 at 22:49
Bless you
Many thanks!
October 5th, 2012 at 4:19
Thanks Tom. Nice work.
October 26th, 2012 at 8:42
Tom,
you do realize that you will not be able to use the new Activity Feeds when AppFabric is not correctly configured?
Did your workaround yesterday but unfortunately started all over again because to many faults with User Profile and stuff…