kamagra how much to take

SharePoint 2013 Standalone Installation Issues

Installing SharePoint 2013 customer preview under a standalone instance is a pain in the ass. There are a couple of things that you are most likely going to run into if this is the route that you are going, here is how to solve a couple of them. I am sure there are others.

First error you are probably going to hit is related to AppFabric’s Distributed Caching. The error that I kept getting was:

ErrorCode:SubStatus: Service running under Network Service account in workgroup environment is not supported.

or

ErrorCode<NonDomainNWService>:SubStatus<ES0001>:Service running under Network Service account in workgroup environment is not supported.

This one is pretty easy to interpret and get around since you really only need to change where AppFabric is running. No biggie.

1) Open up a PowerShell instance

2) Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN or use the SharePoint Administration Shell in Step 1.

3) Execute the following command:

  1. psconfig.exe -cmd Configdb create SkipRegisterAsDistributedCacheHost

Now just a few things to change on the SQL end. Since we are in a standalone instance, using SQL Express, you have to download a set of the SQL management tools from here:

http://www.microsoft.com/en-us/download/details.aspx?id=29062

or use the full SQL media installation whatever works you just need the tools from somewhere.

Once the management tools are installed, connect to the SharePoint instance, named SHAREPOINT. If you are confused on instance names you can also find them in the Services MMC snapin. Find the Security node once connected, and expand it out. Find the user under Logins that you are installing SharePoint with, then ensure they have the following roles:

  1. setupadmin
  2. sysadmin
  3. serveradmin
  4. dbcreator

Now it will install, and you can bring up WCAM. However, the next error you will see is:

Exception: System.ArgumentException: The SDDL string contains an invalid sid or a sid that cannot be translated.

Yeah! More errors. This one you will see when trying to work with the Search Service most likely.

To fix this error, login with your Administrator account and create a search service user and add them to the WSS_ADMIN_WPG group. Following, flip open the SharePoint Management Shell, first you need to get a credential object based on a user name and password by using Get-Credential so that a new managed account can be built. To do this, replace your [Your Search Account] with the one just specified.

Paste the following into PowerShell.

  1. $SearchServ = Get-Credential [Your Search Account]
  2.  
  3. New-SPManagedAccount -Credential $SearchServ

New-SPManagedAccount, as the name implies, simply registers a new managed account for the specified Credential or Username, and Password. Then we have to assign this account to the search service, so just open up WCAM, click on Security, and then Service Accounts. Once in the Service Accounts screen, you can change the Search Service to use the new account. Following, run the configuration wizard again, and you should be good to go!

Share

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>