All postings, articles, and other content on this blog are provided ”AS IS” with with no warranties, and confer no rights. Any sample on this blog is subject to the terms specified at Microsoft
When checking the prerequisites for a migration to SPS 2013 in order to identify missing features, assemblies or webpart please execute it from one of WFE instead of the Central Admin because if not you will have false positives if you have customer code.
Héctor Calvarro Martín. SharePoint. Microsoft Premier Field Engineer for EMEA
I would like to tak about a experience that happened to me during a migration at a customer.
It turned out that the UPA was totally stuck starting and after a while stopped. When we were checking the SharePoint logs we found the following
UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_CONFIG_DB at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result) at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage2() at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).
Cheking on our internal Knowledge Base we found that April 2014 CU solved the issue and when you go directly to the KB article page, it states
If you have Microsoft SQL Server 2014, you cannot run profile synchronization in SharePoint Server 2013 SP1 by using the Forefront Identity Management engine.
So if you are in a considering to migrate to SPS 2013 SP1 from SharePoint 2010 or 2007 and you want to use SQL Server 2014, you must install SPS 2013 SP1 + April 2014 CU to have user synchronization.
Please I would like to highlight the new policy statement concerning .NET Framework and Internet Explorer
Microsoft .NET Framework Support Lifecycle Policy
Internet Explorer Support Lifecycle Policy
Héctor Calvarro Martín. SharePoint. Microsoft Premier Field engineer for EMEA
There is a new version of ULS viewer ,as Bill Baer announced, with so many new features.
To download it please do it from here
Héctor Calvarro Martín. EMEA SharePoint PFE
It's ready to download June 2014 CUs for SPS 2010. Please there is a major change from now on there will be a CU EVERY MONTH. SO FORGET ABOUT THE 2 MONTHS CADENCE.
SharePoint 2010 (Build 14.0.7128.5001 )
(REMEMBER TO INSTALL FIRST SP2)
After installing the updated you should run the SharePoint Config Wizard in every server of the farm.
If SPS 2010 installed you must only install the SPS 2010 CU because it includes the Foundation one.
It's ready to download July 2014 CUs for SharePoint 2013. Please there is a major change from now on there will be a CU EVERY MONTH. SO FORGET ABOUT THE 2 MONTHS CADENCE.
BTWPlease as in April Exe and cabs are split so you will need to download several files
SharePoint 2013 (Build 15.0.4631.1001)
REMEMBER TO INSTALL FIRST SharePoint 2013 SP1
If SPS 2013 installed you must only install the SPS 2013 CU because it includes the Foundation one.
Lately, I see on customers farm topologies drawn by hand, with strange icons etc
The truth must be told, my point is the most elegant way to draw those topologies is via Visio and the New Office Stencils. For instance, the following one extracted from a Product group white paper
BTW, these stencils are not only limited to SharePoint any product related to New Office has its own icon like Lync v.g.
In order to have them you have to download them from
and set them up following the next guide
I hope it will like you.
Héctor Calvarro Martín. EMEA SharePoint Premier Field Engineer.
It's ready to download June 2014 CUs for SPS 2010
SharePoint 2010 (Build 14.0.7125.5002)
It's ready to download June 2014 CUs for SharePoint 2013. Please as in April 2014 Exe and cabs are split so you will need to download several files
SharePoint 2013 (Build 15.0.4623.1001)
I was updating a farm to SP 2013 SP1 and OWA SP1 and after that I had an error when browsing files on OWA. When I put the OWA ULS logs to Verbose I found the following call stacks :
The toplogy XML file exists but has invalid XML. Returning 0 machines. System.InvalidOperationException: There is an error in XML document (3, 4). ---> System.Xml.Schema.XmlSchemaValidationException: The required attribute 'FullyQualifiedDomainName' is missing. at System.Xml.Schema.XmlSchemaValidator.SendValidationEvent(XmlSchemaValidationException e, XmlSeverityType severity) at System.Xml.Schema.XmlSchemaValidator.CheckRequiredAttributes(SchemaElementDecl currentElementDecl) at System.Xml.Schema.XmlSchemaValidator.ValidateEndOfAttributes(XmlSchemaInfo schemaInfo) at System.Xml.XsdValidatingReader.ProcessElementEvent() at System.Xml.XsdValidatingReader.Read() at System.Xml.XmlReader.ReadStartElement() at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderFarmTopology.Read3_FarmTopology(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderFarmTopology.Read4_FarmTopology() - -- End of inner exception stack trace --- at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at Microsoft.Office.Web.Apps.Environment.WacServer.XmlReaderWriter.ReadStructuredDataFromXml[T](String filePath, String schemaFile) at Microsoft.Office.Web.Apps.Environment.WacServer.LocalFarmTopology.Refresh()
ServiceInstanceFinderAdapter.FindAllServiceInstances() threw an exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at Microsoft.Office.Web.Apps.Environment.WacServer.AFarmTopology.GetMachine(String machineName) at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter..ctor() - -- End of inner exception stack trace --- at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at Microsoft.Office.Web.Common.EnvironmentAdapters.HostEnvironment.LoadAdapterInstance(AdapterLoadInformation adapterInfo, Boolean readAppConfigOnly) at Microsoft.Office.Web.Common.EnvironmentAdapters.HostEnvironment.AdapterLoadInformation`1.<>c__DisplayClass17.<BuildInstance>b__16() at System.Lazy`1.CreateValue() at System.Lazy`1.LazyInitValue() at Microsoft.Office.Web.Common.EnvironmentAdapters.HostEnvironment.get_ServiceInstanceFinderAdapter() at Microsoft.Office.Web.Common.ServiceInstanceFinder.RefreshList(Object state)
After thinking about it turned out that the FullyQualifiedDomainName in the topology.xml archive in C:\ProgramData\Microsoft\OfficeWebApps\Data\FarmState at OWA server. Please check also if the HEALTH status is set to "Healthy" if not change it from "Unhealthy" to "Healthy".
1. Modify your OWA farm topology.xml to below:
<?xml version="1.0" encoding="utf-8"?><FarmTopology xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/office/services/WacServerTopology.xsd"> <Machine Health="Healthy" LastHealthUpdate="2014-06-09T10:43:31.1131267Z" Name="IO-OWA" FullyQualifiedDomainName="IO-OWA.MyDomain.COM" Id="81df187e8a034557b878b7a181404f1c"> <Role>WordBackEnd</Role> <Role>FrontEnd</Role> <Role>PowerPointBackEnd</Role> <Role>ExcelBackEnd</Role> </Machine></FarmTopology></FarmTopology>
2. Restart your OWA server3. Check if you can browse any document using OWA
Héctor Calvarro Martín. SharePoint Dev/Core. EMEA Premier Field Engineer.
Please check Stefan Gossner's link
Today Product group announces that Autohosted apps will end on June 30 2014
We’re announcing today that the Office 365 Autohosted Apps Preview program will end on June 30, 2014. After June 30th, developers will not be able to create new autohosted apps in SharePoint. Apps that are currently running in the service will not be affected or shut down.
If you are currently using autohosted preview apps in a production environment, we recommend that you follow this step-by-step on how to transition autohosted preview apps to provider-hosted apps.”
Please bear it in mind if you will develop new ones because it's the time of considering to create an autohosted app. If you had one deployed please follow the guide provided here http://msdn.microsoft.com/EN-US/library/office/dn722449(v=office.15).aspx
I wanted to highlight the following document to everybody how is considering to install SharePoint in Windows Azure IAAS.
Moreover, I would like to recall to your mind the supported and not supported scenarios of SharePoint and Windows Azure:
- SharePoint 2010 SP1 + CU and onwards.
- SharePoint 2013 RTM and onwards.
- Fast Server over SPS 2010
- WSS 3.0, MOSS 2007.
For more info http://blogs.msdn.com/b/calvarro/archive/2013/04/29/support-of-sharepoint-over-windows-azure.aspx
It's ready to download April 2014 CUs for SharePoint 2013. We added support for SQL Server 2014 :)
CAVEAT => Now the hotfix is not a single file due to the high weight of the cab files. So you have to download the exe file and cab files and put them in the same folder. It's quite easy when you'll click on the hotfix you will see more than one check boxes to be clicked. So clicked all and ,as said. put hem in the same folder.
SharePoint 2013 (Build 15.0.4605.1004)
Today Tuesday April 8th 2014 has ended the support for the products SharePoint 2003, WSS 2.0 and Office 2003.
So, it's a good moment to try and migrate to SharePoint Server 2013 u Office 365 (Cloud service that contains Sharepoint Online) and get into in a new age of content management, app development and intranet and extranet creation.
Héctor Calvarro Martín. EMEA SharePoint Premier Field Engineer.
It has been found a problem with SP 2013 SP1 that prevent users to install new updates. Please read the official info from the KB
Recomended to not install SP1 until future notification
We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.
Recomended to not install it until future notification
I would like to highlight some points concerning Distributed Cache and SharePoint 2013:
The Distributed Cache service can end up in a nonfunctioning or unrecoverable state if you do not follow the procedures that are listed in this article. In extreme scenarios, you might have to rebuild the server farm. The Distributed Cache depends on Windows Server AppFabric as a prerequisite. Do not administer the AppFabric Caching Service from the Services window in Administrative Tools in Control Panel. Do not use the applications in the folder named AppFabric for Windows Server on the Start menu.
On a server that has more than 16 GB of total physical memory, allocate a maximum of 16 GB of memory to the Distributed Cache service. If you allocate more than 16 GB of memory to the Distributed Cache service, the server might unexpectedly stop responding for more than 10 seconds.
The Distributed Cache service can run on either a physical or virtual server. When using virtualization, do not use Dynamic Memory to manage shared memory resources among other virtual machines and the Distributed Cache servers. The memory allocation for virtualized Distributed Cache servers must be fixed.
When your server farm has a dedicated Distributed Cache server. Use the following method to calculate how much memory can be assigned to the Distributed Cache service:
Determine the total physical memory on the server. For this example, we will use 16 GB as the total physical memory available on the server.
Reserve 2 GB of memory for other processes and services that are running on the cache host. For example, 16 GB – 2 GB = 14 GB. This remaining memory is allocated to the Distributed Cache service.
Take half of the remaining memory, and convert it to MB. For example, 14 GB/2 = 7 GB or 7000 MB. This is the cache size of the Distributed Cache service
Use the following procedure to update the memory allocation accordingly.
After installing the update you should do the following in all the servers that are holding the distributed cache
After you apply this cumulative update, AppFabric uses a nonblocking garbage collection (background server garbage collection). Nonblocking garbage collection is a new feature in the .NET Framework 4.5.
To apply this fix, follow these steps:
1. Upgrade the servers to the .NET Framework 4.5.2. Install the cumulative update package.3. Enable the fix by using the following setting <appSettings><add key="backgroundGC" value="true"/></appSettings> in the DistributedCacheService.exe.config file between
<appSettings><add key="backgroundGC" value="true"/></appSettings>
<dataCacheConfig>4. Restart the AppFabric Caching service for the update to take effect.Note By default, the DistributedCacheService.exe.config file is located under the following directory:
%ProgramFiles%\AppFabric 1.1 for Windows Server
Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache $DLTC = Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache$DLTC.maxBufferPoolSize = "1073741824"$DLTC.maxBufferSize = "33554432"$DLTC.requestTimeout = "3000"$DLTC.channelOpenTimeOut = "3000"$DLTC.MaxConnectionsToServer = "100"Set-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache $DLTCRestart-Service -Name AppFabricCachingService
Product Group update how to tune the Distributed cache please follow Fine-tune the Distributed Cache service by using a Windows PowerShell section https://technet.microsoft.com/en-us/library/jj219613.aspx
As you can read on the Official Office Sustained Enginering blog SharePoint 2013 SP1 has been released (amoung other Office products SP1s)
What's new in SP1?
SP1 provides fixes to improve general stability, functionality, and security in Office, SharePoint Server, and related products. Among the functionality improvements and changes are the following:
How to download them?
You can download them from http://www.microsoft.com/en-us/download/default.aspx or via Microsoft Update and the Windows Server Update Services (WSUS) catalog. After a 30-day period, SP1 will begin releasing as an automatic update through Microsoft Update.
For Office 365 they will be installed in the next regular update.
In theory it includes all PUs, Security updates and CUs until January 2014 (So FEB 2014 CU is not included)
The kbs for them are
Project Server (IT'S NEEDED TO INSTALL BEFORE SPS 2013 SP1 BECAUSE IS NOT INCLUDED)
Office Web Apps
BTW, I'll create an update guide as I did with SPS 2010 SP1 and SP2 to clarify the steps of installing the SP1.
It's ready to download February 2014 CUs for SPS 2010
SharePoint 2010 (Build 14.0.7116.5000)
After you install this hotfix, you must restart the User Profile Synchronization Service for profile synchronization to function correctly.
To work around this issue, follow these steps:
1.Visit Central Administration. 2.Click Manage Services on the System Settings section. 3.Find User Profile Synchronization Service in the list of services and then click Stop if its status is Started. Click Start and provide the credentials to start the User Profile Synchronization Service as soon as its status is Stopped.
For more information, see the Start the User Profile Synchronization service section in the Configure profile synchronization article in the library.
After almost two years working as a Support Escalation Engineer SharePoint for developers and administrator support (5 years in Customer Technical Support), Two weeks ago I joined the Premier Field Engineer team within GBS. So henceforth, all my beloved customers that ended working with me in Severity As or escalated cases to tier 3 will miss me because I'm leaving the Technical Support team. It has been a pleasure working with all of you and now I'm pretty sure that we will meet each other in the future doing on-site proactive services.
See you soon.
Después de casi dos años trabajando como Support Escalation Engineer SharePoint para desarrolladores y administradores (5 años en soporte técnico), hace dos semanas me uní al grupo Premier Field Engineer en GBS. Asi que de ahora en adelante, seguro que mis queridos clientes que trabajaban conmigo en severidades A o casos escalados me echaran de menos, ya que eso significa que abandono soporte técnico. Ha sido un placer trabajar con todos vosotros y estoy seguro que nos volveremos a ver en el futuro en mis visitas en cliente haciendo servicios proactivos.
Today, my colleague Enrique Palomino and I discovered this amazing tool for Windows Phone 8 that is absolutely a must.
It's name is Remote Office and enables you to control any Office file via a Windows Phone 8 and bluetooth. It has been developed by Microsoft Research and in their words:
Office Remote turns your Windows Phone into a smart remote for Microsoft Office, providing convenient touch-based control of Word, Excel, and PowerPoint documents projected from your PC. It lets you show what you want, when you want, with all the freedom you need to walk around and connect with your audience.
To set the tool up, you should follow the following steps:
1.- Install the app for Windows Phone 8 from this link
2.- Install an Office add-in in order to make the trick
3.- Open Remote Office and pair your PC with your Windows Phone 8 device via bluetooth.
4.- Open a file in your PC and enable Office Remote.
5.- Then you will be able to do the following things with:
- Navigate next slide/previous slide- View slide thumbnails and jump to slide- View speaker notes on phone- View presentation timer and slide progress- Laser point using touch on your phone
- Navigate rows and columns- Change sheets by swiping- Use Slicers, PivotTables and Filters- Jump to any named object in your workbook- Change zoom level
- Jump to headings- Jump to comments- Screen up/down- Line up/down- Change zoom level
I hope you'll enjoy it :)
For more info:
Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft EMEA Premier Field Engineer.
It's available the sdk for SharePoint 2013 in the following address.
Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA
It's ready to download October 2013 CUs for SharePoint 2013
SharePoint 2013 (Build 15.0.xxxx.xxxx)
REMEMBER TO INSTALL FIRST MARCH 2013 PU IF YOU ARE UPDATING FROM RTM
It's ready to download October 2013 CUs for SPS 2010
SharePoint 2010 (Build 14.0.7110.5000)
BTW, Maybe you'll notice that after installing the Config DB version is 14.0.7108.5000 instead of 14.0.7110.5000. No worries that it's because of the SEARCH dlls have been released as a version higher 14.0.7110.5000 than the SharePoint dlls 14.0.7108.5000 .
It has been published a kb concerning Windows Server 2012 R2 and SPS 2013. WS 2012 R2 will be supported since SharePoint 2013 SP1 will be released.