This is a continuation of my first post http://techrevmarrell.com/Lists/Posts/Post.aspx?ID=17
So after a very exciting couple of day installing and playing around with these 2 new packages, I think I’ve got it good to go. After a smooth uninstall of the SharePoint 2013 package, I kicked off a Standalone installation on the server. Everything went well this time around, well until I got to the psconfig. The UI ran, but then I noticed that I was getting an error on step 3 of the config wizard.
Failed to connect to the configuration database.
An exception of type System.Management.Automation.CmdletInvocationException was thrown. Additional exception information: ErrorCode<NonDomainNWService>:SubStatus<ES0001>:Service running under Network Service account in workgroup environment is not supported.
My first thought was a really technical “Oh Come On!” but it just so happened that Neil Sly (@nrs) was having the same issue and posted a link to a technet post via yammer (are you using yammer yet?). http://social.technet.microsoft.com/Forums/en-US/sharepointitpropreview/thread/57dfc126-c730-4c9b-bb70-5e4a2acdddd5
Appears that one of the Pre-Req’s is a tool called AppFabric (more info later) which does something or the other with caching, and for some reason running it at Network Service gets it madder than a 2yr old in a candy store forced to practice restraint. Anyways the following powershell command will create the configdb manually then you can run the psconfig again and it will complete. (Sorta…)
psconfig.exe -cmd Configdb create SkipRegisterAsDistributedCacheHost
What do you mean sorta? Well PSCONFIG failed again for me. seemed to get much further this time and actually gave me a different error “The SDDL string contains contains an invalid sid a sid that cannot be translated”
Now I am absolutely certainly this is related to my “forced non domain” install, and this will give me something to troubleshoot and another blog post. But I went ahead and tried Central Administration and Viola, there it was in all it’s akward minimal glory. 🙂 SharePoint 2013.