Troubleshooting SharePoint

On August 21, 2011, in sbsblog, by

Put these two PowerShell commands in your noggin.  When you have SharePoint issues, your first knee jerk should be to NOT rip out SharePoint but to try one of these commands instead.

(edit – I forgot the NOT in there)

Remember after SharePoint updates, you need to run psconfig to complete the updates.

[Today’s post comes to us courtesy of Justin Crosby from Commercial Technical Support]

Today’s post is going to cover two commands you should always run when troubleshooting CompanyWeb (SharePoint) on SBS 2011 Standard. These two commands take less than a minute to run and will catch two of our most common CompanyWeb issues.

The commands must be ran as an administrator from the SharePoint 2010 Management Shell. You can launch the shell from All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell.

From the shell you should first run:


This command will return nothing if the SharePoint service accounts are synced with Active Directory. If you receive an error here please use the following blog post to fix it:

The second command you should run is:

(get-spserver $env:computername).NeedsUpgrade

If this command returns True you must run PSCONFIG as described in the following blog post: If the command returns false you will need to troubleshoot your SharePoint issue as normal.


2 Responses to Troubleshooting SharePoint

  1. Dean says:

    “your first knee jerk should be to rip out SharePoint”


  2. Dean says:

    “your first knee jerk should be to rip out SharePoint”

    Actually yes. Rip it out and leave it out. It’s too much of a hassle for what it gives you.