SPSearchServiceApp: test returns False, "FixFarmAccountPermissions is set to True..."
See original GitHub issueDetails of the scenario you tried and the problem that is occurring
Trying to install a SharePoint Subscription Edition farm with search service app.
Set
works well, but Test
returns False, with error “FixFarmAccountPermissions is set to True, but the Search databases do not have the correct permissions”
Verbose logs showing the problem
VERBOSE: [SWAZSP00]: LCM: [ Start Resource ] [[SPSearchServiceApp]SearchServiceApp]
VERBOSE: [SWAZSP00]: LCM: [ Start Test ] [[SPSearchServiceApp]SearchServiceApp]
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Testing Search service
application 'Search Service Application'
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Getting Search service
application 'Search Service Application'
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Executing as the local run as
user C0NT0S00\_spadm
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving BeginProcessing Method
of Get-SPServiceApplicationPool.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving ProcessRecord Method of
Get-SPServiceApplicationPool.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving EndProcessing Method of
Get-SPServiceApplicationPool.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving BeginProcessing Method
of Get-SPServiceApplication.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving ProcessRecord Method of
Get-SPServiceApplication.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving EndProcessing Method of
Get-SPServiceApplication.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving BeginProcessing Method
of Get-SPServiceApplicationProxy.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving ProcessRecord Method of
Get-SPServiceApplicationProxy.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving EndProcessing Method of
Get-SPServiceApplicationProxy.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Checking Farm account
permissions
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving BeginProcessing Method
of Get-SPFarm.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving ProcessRecord Method of
Get-SPFarm.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Leaving EndProcessing Method of
Get-SPFarm.
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Checking Admin Database
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Checking Analytics reporting
Database
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Checking Crawl Database(s)
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Checking Links Database(s)
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Current Values:
AlertsEnabled=True; ApplicationPool=SharePoint Search App Pool; CloudIndex=False; DatabaseName=SP_00_Search;
DatabaseServer=SPDB; DefaultContentAccessAccount=C0NT0S00\_spcrawler; Ensure=Present; FixFarmAccountPermissions=True;
Name=Search Service Application; ProxyName=Search Service Application Proxy; SearchCenterUrl=
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] Target Values:
ApplicationPool=SharePoint Search App Pool; DatabaseName=SP_00_Search; DefaultContentAccessAccount=C0NT0S00\_spcrawler;
Ensure=Present; FixFarmAccountPermissions=True; Name=Search Service Application; Verbose=True
VERBOSE: [SWAZSP00]: [[SPSearchServiceApp]SearchServiceApp] FixFarmAccountPermissions is set
to True, but the Search databases do not have the correct permissions
VERBOSE: [SWAZSP00]: LCM: [ End Test ] [[SPSearchServiceApp]SearchServiceApp] False in 1.0150 seconds.
VERBOSE: [SWAZSP00]: LCM: [ End Resource ] [[SPSearchServiceApp]SearchServiceApp]
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
SPSearchServiceApp SearchServiceApp
{
Name = "Search Service Application"
DatabaseName = "SP_00_Search"
ApplicationPool = "SharePoint Search App Pool"
DefaultContentAccessAccount = $SPCrawlerAccountCredential
PsDscRunAsCredential = $SPInstallAccountCredential
DependsOn = "[SPServiceAppPool]SharePointSearchServiceAppPool"
}
The operating system the target node is running
Windows Server 2019
Version and build of PowerShell the target node is running
Version of the DSC module that was used
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
SharePointDSC
Ignoring this because we need to generate a stub credential to return up ... Only check and correct when Ensure=Present, FixFarmAccountPermissions=True and ...
Read more >PowerShell
Set works well, but Test returns False, with error "FixFarmAccountPermissions is set to True, but the Search databases do not have the correct...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
A PR that fixes this issue is submitted here: https://github.com/dsccommunity/SharePointDsc/pull/1331
This will not trigger a new release of the SPSE package. In the meantime, you can implement that update on your end: https://github.com/dsccommunity/SharePointDsc/pull/1331/files -> Specifically the changes on the file SharePointDsc/Modules/SharePointDsc.Search/SPSearchServiceApp.psm1
Fix has been implemented and tested. Will be included in my next Bugfix PR