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

4 Comments

  1. Darrin says:

    Thanks for the great info. I used the PS equivalent of the psconfig command to get around the distributed cache issue:
    New-SPConfigurationDatabase -DatabaseServer $([System.Environment]::MachineName + “\SharePoint”) -DatabaseName SP2013_ConfigDB -AdministrationContentDatabaseName SP2013_AdminDB -FarmCredentials $(Get-Credential $([System.Environment]::MachineName + “\Administrator”)) -SkipRegisterAsDistributedCacheHost

    Running PSConfig UI I got the following SDDL stack trace :
    07/18/2012 22:10:51 23 ERR Exception: System.ArgumentException: The SDDL string contains an invalid sid or a sid that cannot be translated.
    Parameter name: sddlForm
    at System.Security.AccessControl.RawSecurityDescriptor.BinaryFormFromSddlForm(String sddlForm)
    at System.Security.AccessControl.RawSecurityDescriptor..ctor(String sddlForm)
    at Microsoft.SharePoint.Win32.SPNetApi32.CreateShareSecurityDescriptor(String[] readNames, String[] changeNames, String[] fullControlNames, String& sddl)
    at Microsoft.SharePoint.Win32.SPNetApi32.CreateFileShare(String name, String description, String path)
    at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.CreateAnalyticsUNCShare(String dirParentLocation, String shareName)
    at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.ProvisionAnalyticsShare(SearchServiceApplication serviceApplication)
    at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.CreateDefaultStoreLocation(SearchServiceApplication serviceApplication)
    at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.ProvisionRawEventStore(SearchServiceApplication serviceApplication)
    at Microsoft.Office.Server.Search.Administration.AnalyticsServiceAdministration.Provision()
    at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision()

    Digging into the code, I was only able to get past this by manually creating a file share with the UNC path: “\\” + [System.Environment]::MachineName + “\” + “Analytics” + ‘_’ + $(Get-SPEnterpriseSearchServiceApplication).ApplicationName

    The file share points to the local folder: “C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Analytics” + ‘_’ + $(Get-SPEnterpriseSearchServiceApplication).ApplicationName

    I gave permissions to the service account running the OSearch15 service (in my case local administrator), and to the WSS_ADMIN_WPG and WSS_WPG local groups.

  2. Toni says:

    Thank you very much!

  3. Venky says:

    Followed your tip from as afore said: But I am getting below error. I am running in Windows server 2012 and not added to domain.

    PS C:\Users\Administrator> new-spmanagedaccount -Credential $SearchServ
    WARNING: The specified user win12\spsearch is a local account. Local accounts
    should only be used in stand alone mode.

    UserName PasswordExpiration Automatic ChangeSchedule
    Change
    ——– —————— ——— ————–
    WIN12\spsearch 12/5/2012 10:18:52 PM False

  4. reggie says:

    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.
    How do i create the search service user.?thanks

Trackbacks/Pingbacks

  1. SharePoint Daily » Blog Archive » CMS with SharePoint 2013; Office 2013 Web Apps Dependent on the Desktop; Do Enterprises Need Microsoft Office? - [...] SharePoint 2013 Standalone Installation Issues (ARB Security Solutions) Installing SharePoint 2013 customer preview under a standalone instance is a …
  2. CMS with SharePoint 2013; Office 2013 Web Apps Dependent on the Desktop; Do Enterprises Need Microsoft Office? - SharePoint Daily - Bamboo Nation - [...] SharePoint 2013 Standalone Installation Issues (ARB Security Solutions)Installing SharePoint 2013 customer preview under a standalone instance is a pain …
  3. SharePoint: Recopilatorio de enlaces interesantes (I)! - Blog del CIIN - [...] SharePoint 2013 Standalone Installation Issues [...]

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>