Errors, Installation, Office web apps, OWA, SharePoint 2013

Office Web Apps 2013 patch issue – Windows Update KB2592525 must be installed

During an OWA 2013 installation on a Windows Server 2008 R2 Sp1 I got the following error,

The operation failed, The server did not meet the following prerequisites: – Windows Update KB2592525 must be installed.


It was strange since all prerequisites and patches were intalled, anyway I looked for the KB2592525 update, downloaded it but i couldnt install it, I got a “not applicable in your computer” error…

This update is not applicable to your computer


To resolve this Issue I tried a manual installation which was succesful for me, the steps are the following:

  1. Create a folder, I called mine “KB2592525” and  is located in C:
  2. Place the downloaded MSU file there
  3. Using CMD navigate to the folder “KB2592525”
  4. Manualy Extract the files in the MSU using the following command line:
    1. expand Windows6.1-KB2592525-x64.msu –F:* C:\KB2592525
    2. You should see something like this:
    3. owapa2
  5. Now, install the extracted cab file using the Pkgmgr command:
    1. pkgmgr /ip /
  6. After this I didn’t get any “Installation Succeeded”… just a new command line will tell you that everything is ok…

I tried to Install OWA again after running those command and this time it completed correctly


Errors, Installation, SharePoint 2013, Uncategorized

SharePoint 2013 Installation Error: The current server cannot be joined to this farm

A client ask me to add a new WFE server to his SharePoint farm, everything went well until I got this error during the Product Configuration Wizard

An exception of type System.InvalidOperationException was thrown. Additional exception information: The current server cannot be joined to the farm because the set of installed products does not match the products installed in the farm.

I looked at the logs and found this error:

The current server cannot be joined to this farm because the set of installed products does not match the products installed in the farm. The license state for the current server doesn’t match the farm’s license state

After validating the current and new servers products I found that the product key that was provided was for a SharePoint Enterprise and the current one was running Standar Edition. In order to join a server to the farm you need to have the same products installed on the new server.

Here is a quick way to validate the products installed on a server:

1.- run regedit

2.-Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\InstalledProducts

3.- Compare the products between the servers:


35466B1A-B17B-4DFB-A703-F74E2A1F5F5E – “Project Server 2013”
BC7BAF08-4D97-462C-8411-341052402E71 – “Project Server 2013 Preview”
C5D855EE-F32B-4A1C-97A8-F0A28CE02F9C – “SharePoint Server 2013”
CBF97833-C73A-4BAF-9ED3-D47B3CFF51BE – “SharePoint Server 2013 Preview”
B7D84C2B-0754-49E4-B7BE-7EE321DCE0A9 – “SharePoint Server 2013 Enterprise”
298A586A-E3C1-42F0-AFE0-4BCFDC2E7CD0 – “SharePoint Server 2013 Enterprise Preview”
D6B57A0D-AE69-4A3E-B031-1F993EE52EDC – “Microsoft Office Web Apps Server 2013”
9FF54EBC-8C12-47D7-854F-3865D4BE8118 – “SharePoint Foundation 2013”

Active Directory, Errors, PowerShell, SharePoint 2013

Access Denied for AD Group Users in SharePoint 2013

While trying control the site security using Active directory security groups I found this issue where users inside those groups were having an Access Denied Error. I realize that the next day they were able to get into the site but newly added users wont.

I assume this was some kind of synchronization problem, but it turns out is a default behavior, SharePoint will cache this group membership info for about 24 hours.

The time out can be configure to a lower value:

$sptokensvc= Get-SPSecurityTokenServiceConfig
$sptokensvc.FormsTokenLifetime = (New-TimeSpan -minutes 2)
$sptokensvc.WindowsTokenLifetime = (New-TimeSpan -minutes 2)
$sptokensvc.LogonTokenCacheExpirationWindow = (New-TimeSpan -minutes 1)

This script will tell the token service that the claims will be valid for 1 minute and after that it will get the latest membership information from the Active Directory.

IMPORTANT: DO NOT SET THE LIFETIME VALUES LOWER THAN THE CHACHE EXPIRATION. If you do that the users will experience a ‘The context has expired and can no longer be used’ Error.

Errors, Installation, SharePoint 2013

SharePoint 2013 Pre requisites install fail, Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.

SharePoint 2013 Pre requisites install fail, Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.

While installing SharePoint 2013 in a Windows 2012 Server I was getting the following error right after the prerequisites installation begins:

SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.

To solve the issue I set the following Local Policy:

1. – Windows Start

2. – run MMC


3. – Click File, Add/Remove Snap-in…


4. – Select Group Policy Object Editor and ADD it


5. – Navigate to Administrative templates / System


6. – Select and edit “Specify Settings for optional component installation and component repair”

7. – Enable and select “Contract Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)”


9.- Re run the prerequisite installation

Errors, Hashtag, Migration, SharePoint 2013

Click on Hash tag Issue – Sorry, something went wrong

After a SharePoint 2010 to SharePoint 2013 migration, whenever a user clicked on a hash tag the detail page had the following error.



After looking around for a while I realize that one of the scripts, Control_TagFeed.js was not been loaded, I went to the folder /_catalogs/masterpages/display templates/system and realize that the file was on check out status for some reason.



I was unable to find the reason for this check out status but after publish the file hash tags were working again.




Errors, SharePoint 2013

SharePoint 2013 Search Error: Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.

I had an issue while trying to crawl my sites content, even after reviewing that the account had enough permissions and also the FULL READ that the error message suggested… after a little research I found out that the issue was related to the LoopBackCheck

In case you are not familiar with this SharePoint headache, here is a Powershell script that will add the registry key needed for this fix.

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -Value “1” -PropertyType dword

After this just start a full crawl again.

Apps, Development, Errors, SharePoint 2013

AppMng.svc – The requested service could not be activated

So i was trying to develop an app in a small SharePoint 2013 farm,I use a Virtual Machine with only 4 GB of RAM.

When i tried to deploy the app i got this Error: The requested service, “Http://Blablalba/AppMng.svc” could not be activated

It happen to be that the server didn’t have enough memory to run the service… since this was a development machine I stopped some services that i didn’t use, one in particular the “SharePoint Search Host Controller” consumes a lot of resources.

After I stopped those services I was able to deploy my app