SharePoint Cumulative Updates “Error: Some farm products and patches were not detected

SharePoint Cumulative Updates “Error: Some farm products and patches were not detected”

Ran into an issue while recently patching a SharePoint 2010 farm from Service Pack 1 to Service Pack 2. Patching is a bit of a science and can be complex depending the number of servers and products installed in your farm. I applied Service Pack 2 and December 2013 Cumulative Update, KB2553400, for SharePoint and Office Web Applications, 4 total updates.

Note – I have found where customers have SharePoint and Office Web Apps on different patch levels or worse Office Web Apps has never been patched. It’s best practice to have SharePoint and Office Web Apps at the same patch level.

All 2 patches installed without error. At least the install wizard said they did.

I ran psconfig.exe, aka SharePoint Products Configuration Wizard, and boom Error: Some farm products and patches were not detected on this or other servers. If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard.”  SharePoint thinks the issue is that one of the servers is missing the Office Web Apps December 2013 Cumulative update




The kicker, these updates were installed and if you are wondering, no we did not run into this issue when we patched our test Farm. I verified these patches were installed in Programs and Features, recently installed updates.  Restarted each SharePoint server after the updates. Still SharePoint thought we hadn’t patched one of the servers.

I remembered running into a similar issue while applying updates on another large SharePoint Farm that had 10 plus language packs. Good Times!


  1. From SharePoint Shell, run the 2 commands below on each SharePoint server.
  2. Get-SpProduct – -Local
  3. (Get-SpServer $env:ComputerName).NeedsUpgrade
  4. Confirm “True” is returned Continue with running the SharePoint Products Configuration Wizard. If “false” no need to run configuration wizard




Thank you for the below post

Leave a comment

Posted by on March 2, 2015 in Uncategorized


Log Shipping with SQL Server 2012

Log Shipping in Simple Steps

Log Shipping was introduced in SQL Server 2000 , The main advantage of this is maintain multiple servers as standby server,robust ,we can decide the time interval.

Requirement for Implementing Log Shipping

Both the All the SQL Server Services should be started with the same domain User Name,if  individual server then Start them with Same User Name and Password.Folder level Sharing should be enabled between the Server, SQL Server Agent Services should be started . SQL Server Express Edition is not Possible For Implementing Log Shipping because SQL Server Agent Services are not available.User must be Sysadmin to configure Log Shipping

Internally  when Log Shipping is configured,there are 4 jobs create between Primary Server and Secondary Server, they are  Backup Job,Copy Job,Restore Job Alert Job

Backup job:

This job is created on Primary Server,this job takes the transaction log backup of the Database on a scheduled time

Copy Job:

This job is created on Secondary Server,this job Copies the transaction log Backup from Primary Server to the Standby/Secondary Server.

Restore Job:

This job is created on Secondary Server,this job restored the  copied transaction log backup on the Secondary Server.

Alert Jobs:

This job is created on Primary Server and Secondary Server.and gives the alerts as email, when there  is a delay in backup ,copy,restore jobs.

Log shipping has disadvantages too ,network usage consumption.

Step 1:

Take a Full Backup and a transaction log Backup from the Principle server and Restore it on the Standby by Server with No recovery mode or Standby Mode.

SQL Query command to take backup

1. Use Master
2. Go
3. Backup Database MyDatabase to Disk = ‘D:\MyDatabase_Full.bak’
4. Backup log MyDatabase to Disk = ‘D:\MyDatabase_Tran.trn’


Go to the Primary Server right click on the database ->Task_> Ship Transactin Logs..


Step 3:

Click in “Enable this as a primary Database in a Log Shipping configuration”


Step 4:

Give the network path and the Physical path of the shared folder of the database, to know the IP of your server run ipconfig /all command in the command prompt. give the backup time schedule,alert schedule, if using SQL Server 2008 you can even select the Compress Backup Option.Click on schedule and the windows opens as below


Step 5:

Click on the add Secondary Server button Option. connect to the Secondary server .As we have Restored a Full Backup and a transaction log backup. so leave the first tab.


Step 6:

click on Copy Files tab,give the physical path of the folder in Secondary Server.and set the schedule for restore Transaction log too.


Now Lo Shipping has been successfully configured ,to monitor the log shipping you can use

Step7 : To Recovery Log shipping database.

1          Use Master

2          Go

3          Restore database DBname with Recovery

Now, log shipping database is ready to use.

Thanks to the post:

Leave a comment

Posted by on April 21, 2014 in SQL Server


Error: “Could not retrieve backup settings for primary” in Log shipping Backup job

This one is simple but interesting…

Log shipping which was running for an year, suddenly stopped working. Log shipping monitor says that there are no backups restored for last 14849 minutes… Why?

We started figuring this out, the copy and restore jobs were running fine but only the backup job was failing.

What was the error generated by the Log shipping backup job?

*** Error: Could not retrieve backup settings for primary ID ‘abfb9a42-207e-451b-968c-3ac29edc16f9’.(Microsoft.SqlServer.Management.LogShipping) ***
*** Error: Failed to connect to server SQLSERVER2001.(Microsoft.SqlServer.ConnectionInfo) ***
*** Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)(.Net SqlClient Data Provider) ***

But the name of the SQL Server name is SQLSERVER2012, so why is it looking for SQLSERVER2001? This is because the server was renamed from SQLSERVER2001 to SQLSERVER2012 recently but the sys.servers was not updated with this change.

As a result, SELECT @@SERVERNAME still points to old name so we ran commands given below to update sys.server entry and then RESTARTED SQL Server:

EXEC sp_dropserver ‘Your_OLD_Computer_Name’


EXEC sp_addserver ‘Your_NEW_Computer_Name’, ‘local’


Now we reconfigured log shipping to make it work. You can either do this or update the Log shipping backup with correct SQL Server instance name or create a SQL Server alias pointing back to new server name to make it work. Still not working? Leave the error message in the comments here….

Thanks to the post



Rename a Computer that Hosts a Stand-Alone Instance of SQL Server –

Leave a comment

Posted by on April 21, 2014 in SQL Server


Unable to load DLL Microsoft.VisualStudio.QualityTools.RecorderBarBHO100.dll. The specified module could not be found

Working on a new environment trying to perform an new Web Test I was faced two issues:

1. Web Test Recorder doesn’t show up

Problem :When I start my recording Internet Explorer comes up but the Web Test Recorder doesn’t show up.

Solution: In IE enter Tools menu Select Explorer Bars and Click “Web Test Recorder 10.0” – (This will work for Web Test 8.0 and 9.0)


2. Cannot Stop Web Test Recording Without Getting Exception


Problem: When I clicked “Stop” in the end of Web Test Recording I get the following Exception: “Unable to load DLL ‘Microsoft.VisualStudio.QualityTools.RecorderBarBHO100.dll’: The specified module could not be found”


Copy Microsoft.VisualStudio.QualityTools.RecorderBarBHO100.dll (For older versions RecorderBarBHO90.dll  etc)

Located under C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\

To – C:\Program Files\Internet Explorer and for 64bit machines also Copy To – C:\Program Files (x86)\Internet Explorer

Please refer:

Leave a comment

Posted by on March 14, 2014 in Visual Studio


moving content db for a site collection to another db server


Here are the steps you will need to take Lets call content DB “MyTESTContentDB”

  1. Do a database backup for the content db “MyTESTContentDB” from sql management studio
  2. Go to target DB Server and create a empty database naming “MyTESTContentDB” after the content DB
  3. Restore the backup from step 1 to empty database create in step 2 “MyTESTContentDB”
  4. Go to SharePoint server and run following script Dismount-spcontentdatabase “MyTESTContentDB” and type “Y” to confirm
  5. Run the following script

    stsadm -o addcontentdb -url -databasename MyTESTContentDB -databaseserver TARGETDBSERVER

You will have to input actual URL, actual db name and correct target db server name

Please refer this:

Leave a comment

Posted by on March 12, 2014 in SharePoint


How To Repair A Suspect Database In MSSQL Server Database

How To Repair A Suspect Database In MS SQL

You have a database in MS SQL that is tagged as (suspect) and you are unable to connect to the database.

Possible Causes

  • The database could have become corrupted.
  • There is not enough space available for the SQL Server to recover the database during startup.
  • The database cannot be opened due to inaccessible files or insufficient memory or disk space.
  • The database files are being held by operating system, third party backup software etc.
  • There was an unexpected SQL Server Shutdown, power failure or a hardware failure.

These steps require you to have Microsoft SQL Server Management Studio installed on your computer.  If you do not have this installed please install Microsoft SQL server Management Studio to connect database server.

 Open Microsoft SQL Server Management Studio and connect to your database

  1. Click the New Query button
  2. Paste the following SQL script into your New Query page replacing [YourDatabase] with the name of your database.
    EXEC sp_resetstatus [YourDatabase];
    DBCC checkdb([YourDatabase])
    DBCC CheckDB ([YourDatabase], REPAIR_ALLOW_DATA_LOSS)
  3. Click Execute

Your database should no longer be tagged as (suspect) and you should be able to access it.

Please refer this:


Leave a comment

Posted by on February 24, 2014 in SQL Server


Restrict normal users joining computer Default limit to number of workstations a user can join to the domain

Please refer Microsoft URL  


By default, Windows 2000 allows authenticated users to join ten machine accounts to the domain. If a user attempts to join an eleventh machine account, the error messages listed in the following Microsoft Knowledge Base Article are displayed:

251335 Domain users cannot join workstation or server to a domain

This default was implemented to prevent misuse, but can be overridden by an administrator by making a change to an object in Active Directory. 

Note that users in the Administrators or Domain Administrators groups, and those users who have delegated permissions on containers in Active Directory to create and delete computer accounts, are not restricted by this limitation.


The number of workstations currently owned by a user is calculated by looking at the ms-DS-CreatorSID attribute of machine accounts. 

To modify Active Directory to allow more (or fewer) machine accounts on the domain, use the Adsiedit tool. 

WARNING Using Adsiedit incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Adsiedit can be solved. Use Adsiedit at your own risk.

  1. Install the Windows Support tools if they have not already been installed. This is necessary only for Windows 2000 and Windows Server 2003. For Windows Server 2008 and Windows Server 2008 R2, Adsiedit is installed automatically when you install the Active Directory Domain Services role.
  2. Run Adsiedit.msc as an administrator of the domain. Expand the Domain NC node. This node contains an object that begins with “DC=” and reflects the correct domain name. Right-click this object, and then click Properties.
  3. In the Select which properties to view box, click Both. In the Select a property to view box, click ms-DS-MachineAccountQuota.
  4. In the Edit Attribute box, type the number of workstations that you want users to be able to maintain concurrently.
  5. Click Set, and then click OK.
Leave a comment

Posted by on February 21, 2014 in Active Directory