I was setting up a standalone SharePoint 2013 Server in the Windows Azure Cloud when I encountered this error message while attempting to set up the Search Service Application:
The SDDL string contains an invalid sid or a sid that cannot be translated.
I found an article that seems to address this issue: http://social.technet.microsoft.com/wiki/contents/articles/17933.sharepoint-2013-the-sddl-string-contains-an-invalid-sid-or-a-sid-that-cannot-be-translated.aspx
However, this did not apply to me because I had already run through the Product Configuration Wizard successfully by using the New-SPConfigurationDatabase PowerShell command.
I tried the solution anyway, and as you can probably guess, it did not work for me.
After doing a bit more digging through some MSDN Forums, it seems that there does not appear to be any solution to this problem other than setting up a SharePoint 2013 Farm in a domain.
So, unlike SharePoint 2010 where you could get a fully functional environment as a standalone server, this does not appear to be the case with SharePoint 2013. You will ABSOLUTELY need a Domain/Domain Controller in order to get a fully functional SharePoint 2013 environment.
If you think that Microsoft should provide the ability to run SharePoint/SharePoint 2013 as a fully functional standalone environment, you can vote for this UserVoice feedback item here: http://officespdev.uservoice.com/forums/224641-general/suggestions/5926223-provide-ability-to-setup-a-complete-standalone-fun
The SDDL string contains an invalid sid or a sid that cannot be translated.
I found an article that seems to address this issue: http://social.technet.microsoft.com/wiki/contents/articles/17933.sharepoint-2013-the-sddl-string-contains-an-invalid-sid-or-a-sid-that-cannot-be-translated.aspx
However, this did not apply to me because I had already run through the Product Configuration Wizard successfully by using the New-SPConfigurationDatabase PowerShell command.
I tried the solution anyway, and as you can probably guess, it did not work for me.
After doing a bit more digging through some MSDN Forums, it seems that there does not appear to be any solution to this problem other than setting up a SharePoint 2013 Farm in a domain.
So, unlike SharePoint 2010 where you could get a fully functional environment as a standalone server, this does not appear to be the case with SharePoint 2013. You will ABSOLUTELY need a Domain/Domain Controller in order to get a fully functional SharePoint 2013 environment.
If you think that Microsoft should provide the ability to run SharePoint/SharePoint 2013 as a fully functional standalone environment, you can vote for this UserVoice feedback item here: http://officespdev.uservoice.com/forums/224641-general/suggestions/5926223-provide-ability-to-setup-a-complete-standalone-fun
No comments:
Post a Comment