An error occurred while running Configuration Wizard.

Upgrade a farm with multiple servers. After the binary files are installed, run the wizard. as a result, the application server (server B) runs the wizard, which starts on the server (server a) that stores the central admin site. then click Cancel. this is a nightmare.

 

Run wizard on server a with a management center site. Failed. the upgrade of server B is in progress and you cannot start upgrading.

 

Okay, run wizard on the old server and report an error saying that another upgrade is running on this machine.

 

Isn't that a solution?

 

Calm down.

 

The upgrade is run through a timer job. The first thing we can think of is to check the timer job. Because the management center can open it, we can view the status of the timer job in it.

 

It is found that an upgrade timer job on server B has been aborted.

 

So what we need to do is run the timer job again. What should we do?

 

The command-line-upgrade-running article contains the following description:

This property is provided as a fail-safe in case the upgrade process is abruptly stopped or if an error occurs during an upgrade process. while unlikely, it is possible to get into a state where the farm thinks that upgrade is running on one computer, but in reality the upgrade process has stop responding. in this unlikely scenario, the Administrator cocould resetCommand-line-upgrade-runningProperty so that the upgrade process cocould be run again.

 

If the upgrade process is accidentally terminated, the server farm enters the following State: all the machines in the server farm think that the upgrade is already running on one machine, but in fact the upgrade process has stopped responding. in this case, the administrator can setCommand-line-upgrade-runningAttribute, so that the upgrade process can run again.

 

In fact, the psconfig tool will check this attribute before running. If yes, an upgrade is running. If no, the upgrade can be executed. Therefore, the command to be run isStsadm-O setproperty-PN command-line-upgrade-running-PV No

 

However, note that the timer job has a cache. to restart, we need to clear the cache of the timer job. We have already introduced this step in the method of clearing the timer job cache of moss.

 

After that, we want to restore the timer job to normal, and the command to immediately execute all the timer jobs for management isStsadm-O execadmsvcjobs. Use!

 

Now we can force Sharepoint to execute the upgrade process. well, for the sake of insurance, use the command line. the psconfig command line has an option to specifically deal with this paused upgrade, called force. by specifying force, psconfig.exe will stop any running upgrade action and start again.

 

So the last trick isPsconfig-cmd upgrade-inplace B2B-wait-Force

 

Note: B2B refers to build. This should be used for patching. If it is upgraded from 03 to 07, V2V, that is, version to version, should be specified.

 

References:

Command-line-upgrade-running: stsadm property (Windows SharePoint Services)

Http://technet.microsoft.com/en-us/library/cc288357.aspx

Command-line reference for the SharePoint products and technologies Configuration Wizard (Office Sharepoint Server)

Http://technet.microsoft.com/en-us/library/cc263093.aspx