SharePoint 2013設定ウィザードが無効なSIDエラーを与えることができますか?
-
10-12-2019 - |
質問
ウェルI:
VMware仮想マシン上のWindows Server 2008 R2 SP1
SP 2013の前提条件をインストールしました SP 2013を蒔くことができます
設定ウィザードの実行ステップ
System.ArgumentExceptionが投げられました。追加の例外情報:SDDL文字列には無効なSIDまたは翻訳できないSIDが含まれています。
しかし、それは現在ページ見つけられないようになっています
PLZヘルプ
解決
as you are installing as standalone, service running under Network Service account in workgroup environment is not supported.
check these two blogs and fix the issue.
http://kancharla-sharepoint.blogspot.com/2012/07/service-running-under-network-service.html http://kancharla-sharepoint.blogspot.com/2012/07/the-sddl-string-contains-invalid-sid-or.html
他のヒント
This forum article helped me but I have to substitute for the missing "C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server" - C:\Program Files\Windows SharePoint Services\15.0\Data\Analytics_{some guid}
Hi All,
Recently an issue was reported to me where some of my site admins were facing an issue in setting up a SharePoint 2013 stand alone environment. They were facing this error in the step 8 of SharePoint configuration wizard "The SDDL string contains an invalid sid or a sid that cannot be translated".
After spending significant amount of time this issue was finally resolved in this way:
- Add the account you want to use for search service in WSS_Admin_WPG group. If you are going to use built in administrator account this should be present by default.
- Then execute this command from sharepoint powershell console: $SearchService = Get-Credential Domain\UserName in our scenario of standalone installation the Domain should be the machine name.
- Then execute this command New-SPManagedAccount -Credential $SearchService
- Now Go to "C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server" and find the folder that starts with Analytics with a postfix guid.
- Right-click --> Properties-->Sharing-->Advanced Sharing
- Check the "Share this folder' check box and click on Permissions
- Add the Search Service account created in step 2 and select Full Control. Do the same for WSS_ADMIN_WPG
- Run the SharePoint Configuration Wizard again. It should now complete successfully.
Rahul Rashu