How do I – Resolve the Powershell New-SPConfigurationDatabase command error – The pipeline has been stopped, This SharePoint farm currently has pending upgrades

Written by Cornelius J. van Dyk on . Posted in How Do I...

I was building a fresh SharePoint farm and issued the “New-SPConfigurationDatabase” Powershell commandlet when I was presented with the following error:

 

PS C:\Users\blog-spadm> New-SPConfigurationDatabase

cmdlet New-SPConfigurationDatabase at command pipeline position 1 
Supply values for the following parameters: 
DatabaseName: SharePoint_Config 
DatabaseServer: SPSQL.Crayveon.com 
FarmCredentials 
Passphrase: ********* 
New-SPConfigurationDatabase : The pipeline has been stopped. 
At line:1 char:28 
+ New-SPConfigurationDatabase <<<< 
    + CategoryInfo          : InvalidData: (Microsoft.Share…urationDatabase: 
   SPCmdletNewSPConfigurationDatabase) [New-SPConfigurationDatabase], Pipelin 
  eStoppedException 
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPCon 
   figurationDatabase

New-SPConfigurationDatabase : This SharePoint farm currently has pending upgrad 
es.  The cmdlet New-SPConfigurationDatabase cannot be executed until the upgrad 
e is completed. 
At line:1 char:28 
+ New-SPConfigurationDatabase <<<< 
    + CategoryInfo          : InvalidOperation: (:) [New-SPConfigurationDataba 
   se], SPException 
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPCon 
   figurationDatabase

PS C:\Users\blog-spadm> New-SPConfigurationDatabase

cmdlet New-SPConfigurationDatabase at command pipeline position 1 
Supply values for the following parameters: 
DatabaseName: SharePoint_Config 
DatabaseServer: SPSQL.Crayveon.com 
FarmCredentials 
Passphrase: ***************** 
PS C:\Users\blog-spadm> 

The really silly outcome of this was not related to any upgrade or stopped pipelines or anything of that sort.  Yet another case of the error message NOT having anything to do with the actual problem.  As it turns out, the solution was in the farm Passphrase I was specifying.  The GUI version of PSCONFIG gives you notification when the specified farm passphrase does not conform to domain password policies, but the Powershell version does not.

I reran the exact same command but this time specifying a more complex passphrase that conforms to domain security policies, and the problem was solved!



Cheers
C




image

Tags: , , ,

Trackback from your site.

Cornelius J. van Dyk

Born and raised in South Africa during the 70's I got my start in computers when a game on my Sinclair ZX Spectrum crashed, revealing it's BASIC source code. The ZX had a whopping 48K of memory which was considered to be a lot in the Commodore Vic20 era, but more importantly, it had BASIC built into the soft touch keyboard. Teaching myself to program, I coded my first commercial program at age 15.

After graduating high school at 17, I joined the South African Air Force, graduating the Academy and becoming a Pilot with the rank of First Lieutenant by age 20. After serving my country for six years, I made my way back into computer software.

Continuing my education, I graduated Suma Cum Laude from the Computer Training Institute before joining First National Bank where my work won the Smithsonian Award for Technological Innovation in the field of Banking and Insurance. Soon I met Will Coleman from Amdahl SA, who introduced me to a little known programming language named Huron/ObjectStar. As fate would have it, this unknown language and Y2K brought me to the USA in 1998.

I got involved with SharePoint after playing around with the Beta for SharePoint Portal Server 2003. Leaving my career at Rexnord to become a consultant in 2004, I was first awarded the Microsoft Most Valuable Professional Award for SharePoint in 2005, becoming only the 9th MVP for WSS at the time. I fulfilled a life long dream by pledging allegiance to the Flag as a US citizen in 2006. I met the love of my life and became a private consultant in 2008. I was honored to receive my ninth MVP award for SharePoint Server in 2013.

Leave a comment

You must be logged in to post a comment.