Psconfig exe upgrade database

I've run the Configuration Wizard again, run psconfig. The Health Analyzer is still reporting this error. Try running stsadm. Jason Warren Habanero Consulting Group habaneroconsulting.

I have seen the timer service crash repeatedly if there are multiple upgrade timer jobs one time , you can safely delete those. This is a new farm configuration so I'm a little confused as to why I would be getting this error in the first place. ThatGuyRyan: I checked for concurrency issues and that command just returned "Operation completed"- assuming this is ok then?

Not just the error? I deleted the error yesterday and it came back. This command is automatically executed when running the SharePoint Products configuration Wizard if SharePoint needs to be upgraded. The other option is v2v version to version. Is this the recommended approach? According to one user the last time they did this on the farm the workflows were gone. Is there a possibility of this happening after this command is ran on all farm servers?

When you install the executable for a Cumulative Update CU , you have not actually upgraded your servers yet. The PSConfig. Creating a farm backup prior to finishing the update is a good idea, as this will give you an environment to roll-back to in case of issues. On the positive side, these updates are published by Microsoft, and do include a level of testing. Having also waited this long, you will also have community reference for any issues that were encountered.

On the negative side, CU's are not as tested as Service Packs, and so you should not rush out and install a CU right when it comes out, as they are occasionally known to introduce bug regressions. A good site to stay on top of issues found per CU is the following by Todd Klindt:. In summary, you should definitely apply a CU in a QA environment first, test your critical business functionality, take a backup of Production, then apply the CU once you have tested in QA and been reassured there are no major regressions.

I personally prefer to use the GUI-based SharePoint Products Configuration Wizard when updating a farm, as it has more built-in intelligence to know what actions to perform more of a click Next, Next, Next experience , but you may prefer to use the command line tool. Clearly it is evident from logs that issue is with Search Administration Database. To get past this error, stop the Windows SharePoint Search service through windows services console in all the servers in which search is running.

Then try running PSConfig or configuration wizard. Configuration wizard starts all the services which are supposed to be running after upgrading all the databases and components.

Your email address will not be published. Post an article. Subscribe to Article RSS. Click Sign In to add the tip, solution, correction or comment that will help other users. Report inappropriate content using these instructions.