Microsoft SharePoint servers targets of attack!


According to ZDNet

Hacker groups are attacking Microsoft SharePoint servers to exploit a recently patched vulnerability and gain access to corporate and government networks, according to recent security advisories sent out by Canadian and Saudi Arabian cybersecurity agencies.” find out more in the ZDNet Post.


Microsoft SharePoint
Logo: Microsoft // Composition: ZDNet

SharePoint early versions, what to do with them?

One of the challenges that organizations have with SharePoint is with the evolution, it is a normal situation were an organization keeps the investment on the same version of SharePoint for several years, but them is faced with the product support lifecycle. This means that a specific SharePoint version will have Microsoft’s support end at a given time, so with this situation what to do with the content and applications that exist?

Read my article in LinkedIn, were I talk about this and provide some solutions.

You can find my article here:



SharePoint 2010: Search sorting with text properties problem

In SharePoint 2010 if you configure some text properties, or even properties like title, to be used for sorting on search results, you might end up with an error like:

error exception from hresult: 0x80040e60


The solution is to change the setting in the Managed Property Storage setting of the properties in question, and then perform a full crawl.


This solve my problem and the error disappeared.

What is the cause?

Aparently the setting of this option is directly linked the MaxCharactersInPropertyStoreIndex internaly, and for those that would like to dig a bit more, you can analyse the source code of the ManagedProperty.aspx page and understand the internally Sharepoint is performing a check that will fail if the setting is not to use the “Reduce storage requirements for tet properties by using a hash comparison

You can check more on this issue and solution from the following links:



SharePoint Support Lifecycle



One of the things that is critical to know for whoever has to manage software in an organization, is to know the lifecycle the specific software products. So in the case of SharePoint, this information is available for access.

Usually the mainstream support of a SharePoint version is around 5 years. It is important to have the version updated with the Service Packs / Cumulative updates to garantee the support extension (can be up to 10 years in total)


SharePoint Training – Online and On Premises

One of the most common questions I am asked is were can resources and training information be found for different levels. Well, the best option I can point you at is Microsoft 🙂 more specifically the Microsoft Virtual Academy (


You can choose the product or platform, and the level you need, so that it can fit several needs.

You can also define you own learning path, allowing you to choose the courses and do them at your own pace.


My story with Sharepoint – 10 years and counting

In January of 2004 I had my first contact with Sharepoint, at that time it was the 2003 version, and my first project was to implement an Intranet Portal for a Government Entity, related to the energy area.

I never heard of Sharepoint before, so when I started searching for information, the first thing that I realized was that there wasn’t that much!

So the beginning was learning to install, configure, administrate, manage and USE!

The first Intranet was implemented without any specific development, only adjusting the clients requirements to the way Sharepoint worked. I have to say that the project was a success, and ever since I have been working with Sharepoint almost constantly, not exclusively, but there seems to exist always another Sharepoint project to me 🙂

So after 10 years, I have followed, implemented and some times been the alpha and beta implementor of some of the Sharepoint versions. Currently I have implementations of 2003, 2007, 2010 and 2013 versions of Sharepoint.

  • Sharepoint Portal Server 2003 – Intranet builder, this version was purely for internal use! A very poor community with very few information.
  • Office Sharepoint Server 2007 – The merge between the Sharepoint 2003 and CMS 2002, it was an adventure to start using! a very exciting new approach, that for the first time allowed us to use the same platform for internal and external solutions. Nevertheless it was clear that the merge between the Sharepoint 2003 and the CMS 2002 capabilities was still to be ended. The boost of the Sharepoint community, because the information from Microsoft was limited, the community took for itself to create the information ans solutions, it was the start of one of the most “rich” communities in the IT industry.
  • Sharepoint 2010 Server – A much merged platform, giving the social enterprise boost, and with a real document management capability (instead of managing documents). The community keeps growing, beginning to include other products knowledge. A very timid approach to Sharepoint in the Cloud.
  • Sharepoint 2013 – The more recent version, were we are all at this moment! A very strong community is still growing, and with the reality of Sharepoint in the Cloud a new approach on implementation is being done.

After 10 years working with Sharepoint, sometimes I am asked if I don’t get bored with it and if Sharepoint’s life is reaching the end . . . well, there is no such thing as a Sharepoint project!!! believe me when I say that every project is unique 🙂

About the Sharepoint’s longevity it seems that for every new version that is released it becomes more of a core platform for Microsoft, some examples of this are the inclusion of Project Server and Commerce Server as services on Sharepoint, instead of standalone products.

A real threat to Sharepoint’s continuous use can be the licensing, because in these times of crisis one of the first cuts of costs that companies do is licensing, and if Microsoft doesn’t adjust to this “new” reality it will suffer, as well as the platform.






Workflow History Description field limitation 255 characters

Well we know that Sharepoint is a WORLD to be discovered, in my opinion is in fact many worlds if you want to really know about it. Another thing is that no matter how many years of experience you have on it, that are always new things to discover, some good some bad . . . this time is one of the bad ones 😦

One of my customers has as application of Ideas Management implemented in Sharepoint, the process os approval is based in Sharepoint 2010 workflows. When one idea is rejected it is written a justification text so that it stays associated to the Idea, in this specific case it stays associates to the workflow task.

Ok, so far no problem . . . the user types the justification of the rejection on the multiline field (Description) in the workflow task, and rejects.

So when the Idea author goes and tries to read the justification the text appears truncated … ??? Hum!!! so what is the problem?

The text fields in workflows are limited by design to 255 characters, so even though you can write more than 255 and it is stored (you can check this in the Workflow Tasks List) when it lists the workflow history in the workflow page it truncates the text to the 255 characters.

So the advice (Best Practices) from Microsoft in these cases are to ensure the text in the text fields in workflows do not exceed the 255 characters.

Sharepoint, always a surprise . . sometimes good sometimes bad!

spclaimsutility.authenticateformsuser : “The server was unable to process the request due to an internal error.”


If you have an error similar to this:

“System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo)”


This issue might be caused by the SecurityTokenServiceApplication being stopped in the IIS.


You can check by going to the IISManager-> Sites -> Sharepoint Web Services -> SecurityTokenServiceApplication.


You can start by checking if the Sharepoint Web Services are started.

After that you can check in the SecurityTokenServiceApplication providers if they include your membership providers configurations.


For me it was that the problem, once we started the Sharepoint Web Services and configured the membership providers all started to work again.

Free Microsoft E-Books

One of the most valueable thing is knowledge, therefore every way we can have access to it is most welcome.


Microsoft has over the years been releasing e-books for free on their technologies, and now we have a MONSTER list:

  • Sharepoint
  • Azure and Cloud
  • Development
  • Visual Studio and TFS
  • SQL Server
  • Windows
  • and more


you can find these e-books at this link:



Create a free website or blog at

Up ↑