Getting error Invoke-CimMethod : Value cannot be null. Parameter name: service for SPFarm resource

ISSUE TITLE:

SPFARM - Getting error Invoke-CimMethod : Value cannot be null. Parameter name: service for SPFarm resource

ISSUE DESCRIPTION (this template):

Getting error Invoke-CimMethod : Value cannot be null. Parameter name: service for SPFarm resource

Details of the scenario you tried and the problem that is occurring

Verbose logs showing the problem

VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Detected Version: SharePoint 2016 - c onfiguring server as Application VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] The SharePoint config database ‘Share Point_Config’ already exists, so this server will join the farm. VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] The database exists, so attempt to jo in the server to the farm VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] The server will attempt to join the f arm now once every 60 seconds for the next 15 minutes. VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Leaving BeginProcessing Method of Con nect-SPConfigurationDatabase. VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Entering function SPMountSPConfigurat ionDatabase.InternalProcessRecord VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Creating connection string for config db SharePoint_Config server SQLServer VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Creating connection string for admin content db admincontentdatabase server SQLServer VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Using NTLM for sql connection string VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Openning configdb so that I can join it at server SQLServer database SharePoint_Config in farm mode VERBOSE: [ComputerName]: [[SPFarm]SharePointFarm] Now joining to farm at server SQLServer database SharePoint_Config Invoke-CimMethod : Value cannot be null. Parameter name: service At char:9

•     Invoke-CimMethod @parameters @PSBoundParameters
  

•     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidData: (Microsoft.Share…urationDatabase:) [Invoke-CimMethod], CimException
  • FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletConnectSPConfigurationDatabase,Microsoft.Mana gement.Infrastructure.CimCmdlets.InvokeCimMethodCommand

Suggested solution to the issue

The DSC configuration that is used to reproduce the issue (as detailed as possible)

# insert configuration here

The operating system the target node is running

Version of SharePoint that is used (e.g. SharePoint 2016) Sharepoint 2016

Version and build of PowerShell the target node is running

Name Value

---

PSVersion 5.1.17763.503
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
BuildVersion 10.0.17763.503
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Version of the DSC module that was used (‘dev’ if using current dev branch) 3.3.0.0

[VerdonTrigance]

Do you mean the Central Administration application pool, which is created a timestamp in the name? That is a left over from leaving and rejoining a farm. During the leave process, the CA application pool isn’t deleted. When you then rejoin the farm and SharePoint tries to create the application pool, it detects it already exist and adds the timestamp. To prevent this issue, recreate the farm (including databases) and make sure all websites and application pools are deleted in IIS.

This Install-SPService issue doesn’t ring a bell. Can you please create a new issue and provide any debugging info (ULS or any other log)?

Issue with app pool’s account I resolved with cleaning everything out and deleting pools, dbs and others. restarting everything and beginning from the start. Issue with names of databases I open as another topic.

Now lets return to ‘The type initializer for ‘Microsoft.Office.Access.Services.BrandStrings’ threw an exception.’ error. It was years ago and still here. I faced with it when used AutoSPInstaller too. Case is simple - running Install-SPService from powershell leads to error above (and SPFarm resource call it), but running psconfig.exe looks like workaround for now.

[VerdonTrigance]

@VerdonTrigance Are you 100% sure all of the used accounts are in the domain\account format? The example you shared above unfortunately doesn’t show this.

Khm, some of them are not. I’ll check it again.