1

Closed

Changeset 98528 have multiple broken spots

description

  1. After setting the power option with High Performance a big red text appears with the following text
    You cannot call a method on a null-valued expression.
    At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:5068 char:116
  2. foreach ($serverElement in $node.CrawlComponent.Server) {$crawlSe
    rvers += @($serverElement.GetAttribute <<<< ("Name"))}
    • CategoryInfo : InvalidOperation: (GetAttribute:String) [], Runt
      imeException
    • FullyQualifiedErrorId : InvokeMethodOnNull
You cannot call a method on a null-valued expression.
At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:5069 char:116
  • foreach ($serverElement in $node.QueryComponent.Server) {$querySe
    rvers += @($serverElement.GetAttribute <<<< ("Name"))}
    • CategoryInfo : InvalidOperation: (GetAttribute:String) [], Runt
      imeException
    • FullyQualifiedErrorId : InvokeMethodOnNull
  • When Setting administration component, The following errors and installation will be stucked at waiting for the Search Administration Component.
    Set-SPEnterpriseSearchAdministrationComponent : The search service instance on
    this server is not online
    At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:3394 char:66
  • Set-SPEnterpriseSearchAdministrationComponent <<<< -Sear
    chApplication $searchApp -SearchServiceInstance $searchSvc
    • CategoryInfo : InvalidData: (Microsoft.Offic...rationComponent:
      SetSearchAdministrationComponent) [Set-SPEnterpris...rationComponent], Inv
      alidOperationException
    • FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchA
      dministrationComponent
Closed Apr 18, 2013 at 5:08 AM by brianlala
Closing pending any follow-up.

comments

prawnz wrote Mar 8, 2013 at 5:19 AM

I did a compare and a lot of places $appConfig.CrawlComponent.Server is used instead of $appConfig.CrawlServers.Server which may have cause the administration component to break.

brianlala wrote Mar 15, 2013 at 5:12 AM

Are you installing SP2010 or SP2013? Can you post some of your XML - I've never run into any of these issues and I suspect it may have gotten hung up on something in the XML.

Brian

brm013 wrote Jul 1, 2013 at 5:43 AM

I had this issue pop up, and it was because I had removed a server name from the WorkManagement element.

I was performing a SP2010 install so I went through my scripts and removed features which are 2013 specific. So as part of the Get-FarmServers function it was failing because one of the elements it is looping through didn't have 'true', 'false' or 'servername'. It was empty.

Moral of the story is, if you don't want it, set it to 'false'

Brett