Using local accounts as a managed account in SharePoint 2013

A managed account is an account that is registered within SharePoint 2013 and can be assigned to SharePoint services. The advantage with managed accounts is that they are centrally managed and can be reused across services. However if you are on a SharePoint 2013 environment which is not connected to a domain and try to register a local account as a managed account from the central admin you will get an error

The specified user is a local account. Local accounts should only be used in stand alone mode

Registering local user account as a managed account can be accomplished by using the PowerShell command “New-SPManagedAccount” and passing the local account as the credential parameter. Below are the steps

1.    Get the credentials of local user account and assign to a variable

$AppPoolAct = Get-Credential <local user account>

2.    Execute the New-SPManagedAccount command and pass the variable to the credential parameter

New-SPManagedAccount –Credential $AppPoolAct

3.    The local account would be registered as managed account and warning message in yellow will be displayed.

Now we can use the managed account created in PowerShell for configuring service applications such as the secured store services in central administration.

Fix for Object reference not set to an instance of an object error when configuring SharePoint 2013 App URLs

When trying to configure App urls from SharePoint 2013 central admin you might encounter the dreaded error “Object reference not set to an instance of an object”.

 

 Most common reason for the error is that you are trying to configure App settings without creating service applications and corresponding proxies for App Management Service and Microsoft SharePoint Foundation Subscription Settings Service.

 Below are the steps to fix the issue

1.       Start the App Management Service from central administration.

2.       Start the Microsoft SharePoint Foundation Subscription Settings Service from central administration.

3.       Configure the App Management service application and proxy from central administration or PowerShell

4.       Configure the Subscription Settings service application and proxy from PowerShell

 

Detail steps for  configuring App environment is available in the technet article http://technet.microsoft.com/en-us/library/fp161236.aspx

Fix for disabled New Web Application button in SharePoint 2013

Sometimes after a new installation of SharePoint 2013 on a Windows 2008 R2 system you will see that the New Web Application button is in central administration is disabled even when you have logged in as system account.

The fix for enabling the new web application button is to turn off the notification settings for the system account in the windows server. Below are the steps for turning off notification
1.Open System and security in control panel
2.Under Action center click "Change user account control settings".
3.Move the scroll bar to never notify and click Ok.
4.Restart the server.

After the system has restarted and you navigate to the create web application screen you will now see that the new web application button will be enabled.