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
Hola
Estas son las direcciones para descargar los respectivos Language Packs para Catalán, Gallego y Vasco para SPS 2013 y Project Server 2013
SharePoint Foundation 2013
SharePoint Server 2013
El proceso de instalación como sabéis siempre es primero Foundation y luego Server. No obstante haremos pruebas para corroborar que no ha cambiado.
En instalaciones de Project Server 2013, la funcionalidad de Project Server 2013 no está traducida a estos lenguajes pero si la de SharePoint 2013. Para más información sobre ello os referimos a la siguiente dirección
http://technet.microsoft.com/es-es/library/ff700192.aspx
Para Office Web Apps los links son los siguientes:
Para más info:
http://technet.microsoft.com/en-us/library/cc262108.aspx
Gracias.
Saludos.
Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA
Hello
I would like to share that the mínimum versión of SharePoint supported on Windows Azure:
- SharePoint 2010 SP1 + CU and onwards.
- SharePoint 2013 RTM and onwards.
Not supported:
- Fast Server over SPS 2010
- WSS 3.0, MOSS 2007
For more information please check the following page.
http://technet.microsoft.com/en-us/library/jj154957(v=office.14)
THX.
Kind Regards..
I would like to let you know that it's available for download the April 2013 Security update for Office and there are some patches for SharePoint 2010 included. Please
http://blogs.technet.com/b/office_sustained_engineering/archive/2013/04/09/april-2013-office-update-release.aspx
On the other hand it has been release the SP2 BETA for SharePoint 2010, Project 2010 y Office Web Apps 2010 among others. You should need a connect account to download them
BTW, please, I would like to let you know that MICROSOFT SUPPORT DO NOT SUPPORT THIS BETA because is delivered AS IS and it's only for testing purpouses, so you will use it AT YOUR OWN RISK.
https://connect.microsoft.com/office/InvitationUse.aspx?ProgramID=7722&InvitationID=OSP2-DMWP-G97K
Hi
It's ready to download April 2013 CUs for SharePoint 2013
SharePoint 2013 (Build 15.0.4505.1002)
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 April 2013 CUs for SPS 2010 and MOSS 2007
SharePoint 2010 (Build 14.0.6137.5000)
(REMEMBER TO INSTALL FIRST SP1)
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.
SharePoint 2007 (Build 12.0.6676.5000)
Warning! This update will be only install if SP3 is installed in the environment.
Please, keep in mind that you must install them in the following order first WSS 3.0, and later MOSS 2007.
After installing the updates you must execute the SharePoint configuration wizard in each of the servers of the farm or execute “psconfig –cmd upgrade –inplace b2b -wait” on a cmd.
Regards
La próxima semana tendrá lugar el Martes 9 de Abril de 2013, 8ª Conferencia Española de Usuarios de SharePoint - CEUS VIII en el Teatro Goya en Madrid. Como sabéis es un evento donde usuarios, partners y Microsoft se reúnen y tratan sobre nuevas características, posibilidades y escenarios de clientes sobre SharePoint 2013 y SharePoint On-line.
Además, por parte de soporte Premier estaremos Matias Cordero, Enrique Palomino y yo ,Héctor Calvarro, haciendo una pequeña presentación sobre Performance Point en SharePoint Server 2013 en el track de B.I.
Para consultar la agenda y apuntaros, podéis visitar el siguiente link:
https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032545292&Culture=es-ES&community=0
Muchas Gracias.
Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA.
It has been detected a bug documentation on Software boundaries and limits for SharePoint 2013 http://technet.microsoft.com/en-us/library/cc262787.aspx for Spanish, Italian and French languages, among others languages except English.
The bug is concerning the Web Applciation section that does not reflect that SharePoint 2013 supports farms of 20 Web Application or less.
Now, the bug is on fix process.
BTW, the documentation on English prevails over the other languages.
THX
Kind Regards.
Hi all.
Good tool for Windows 8 in order to search and download MSDN Sample codes from MSDN code gallery using Moden UI
Click here for dowload it
http://apps.microsoft.com/windows/en-US/app/sample-browser/6fd83c79-a2fc-4887-9284-535681eb3993
For further info please visit the oficial web page of the tool
http://blogs.msdn.com/b/onecode/
Hello all
There has been released March 2013 Public Updates for SharePoint 2013. In somehow, they are like the February 2013 CU + some extra updates
Please, they are mandatory in order to install next April 2013 and onward CUs.
SharePoint Foundation 2013 Public Update - KB 2768000
SharePoint Server 2013 Public Update - KB 2767999
ATENCIÓN
If you have a farm with search component and high availability search topologies enabled; you should follow next entry:
http://blogs.technet.com/b/tothesharepoint/archive/2013/03/13/how-to-install-update-packages-on-a-sharepoint-farm-where-search-component-and-high-availability-search-topologies-are-enabled.aspx
If you are installed in SharePoint Server 2013 bear in mind that the server one includes the foundation. It's not needed to install foundation.
Furthemore, if you have any server running Workflow Manager and Service Bus, their Cus are also available:
Workflow Manager February 2013 Cumulative Update - KB 2799754
Bus Service February 2013 Cumulative Update - KB 2799752
Regards.
S. Somasegar, the corporate vice president of the Developer Division at Microsoft, has announced the Office Developer Tools for VS 2012 RTM
You can download it from:
http://aka.ms/OfficeDevToolsForVS2012
For more info, please check:
http://blogs.msdn.com/b/somasegar/archive/2013/03/04/now-available-office-developer-tools-for-visual-studio-2012.aspx
It's ready to download February 2013 CUs for SPS 2010 and MOSS 2007
SharePoint 2010 (Build 14.0.6134.5000)
SharePoint 2007 (Build 12.0.6673.5001)
Maybe some of you have started to use Microsoft Office Developer Tools for Visual Studio 2012 - Preview 2 in order to develop for SharePoint 2013.
We would like to let you know that ,so far, the component is not supported (delivered "AS IS"). So if you have any issue you need to wait until the RTM release in order to open a case.
Please, check the license of this component that is attached to this post and you should check points 10, 14 and 15 for more detailed info.
PLEASE CLICK FOR DOWNLOAD THE LICENSE
Otherwise, you can post an entry in the following fórum for questions regarding this component.
http://social.msdn.microsoft.com/Forums/en-US/category/apps
Kind regards.
With the General Availability of SharePoint 2013, I would like to share with you some points to have a healthy and supported environment.
The following scenarios are NOT supported
Another strong point is the Contemporary UI that renders in HTML5 for mobile browsers, between others mobile views.So, the following mobile browsers detailed in TechNet are the supported ones:
http://technet.microsoft.com/en-us/library/fp161353.aspx
Finally, please bear in mind that SPS 2013 is built on .NET 4.5 RTM in order to develop new .NET projects, although becasue of the new Apps development model there will be a lot of custom functionality relying on JavaScript.
¿Qué te parecería crear soluciones para Microsoft Office y SharePoint 2013, usando tecnologías web estándar, y poder distribuirlas a millones de personas en todo el mundo desde la tienda de Office en Office.com? No te pienses mucho la respuesta, ¡ya puedes hacerlo!
Ven a nuestro DevCamp y aprende cómo conseguirlo.
Si quieres aprender más sobre las aplicaciones para Office y/o SharePoint visita dev.office.com
El registro a este evento es gratuito, pero debes estar registrado para poder asistir. Los asistentes cargarán con los gastos de reserva y pago de su alojamiento y/o viajes. Las comidas serán provistas por la organización del evento.
Para registrarte en este evento, dirígete aquí y selecciona el lugar y día que prefieras (o en los enlaces para el registro en Madrid que tienes a la derecha). Esta invitación no garantiza tu plaza, recibirás una notificación informándote sobre el estado de tu registro en menos de 5 días laborales tras la cumplimentación de tu registro. Ten en cuenta que, debido a la cantidad limitada de plazas, estas se limitan a dos por empresa.
Registro:
Madrid, día 4 de Marzo de 2013
Madrid, día 6 de Marzo de 2013
Nivel:
300
Idioma: Inglés
Audiencia: Arquitectos / Desarrolladores web
Preguntas: Email: jumpstapps@microsoft.com
In this day and age more and more customers are choosing to use Jquery in their customized pages and choose the JavaScript client object model in SharePoint 2010 and 2013. However, it turns out that anyone with skills can reverse engineer debugging the JavaScript client used internally by Microsoft but it shouldn't be used by customers / Developers.
Recently a customer reported an issue we using that kind of JavaScript. The code was as follows.
function FuncNaive1() {
var OldCalendarNotify4a = SP.UI.ApplicationPages.CalendarNotify.$4a; /cahnge to $4b if Sp1 or later
SP.UI.ApplicationPages.CalendarNotify.$4a = function ()
OldCalendarNotify4a();
FuncNaive2();
}
As you can see, the code was calling to an internal function called SP.UI.ApplicationPages.CalendarNotify.$4a and even the customer was completely arware that we should change the var to $4b if SP1 or later. The internal function code looks as following:
Then he overwrites the function calling the old functionality and a new one created by him
It turns out that these actions are completely unsupported. It's not expected that a developer/customer call the function SP.UI.ApplicationPages.CalendarNotify.$4a due to it's not documented in the SDK of SharePoint 2010 nor SharePoint 2013, moreover you shouldn't "override" an internal function. Another point to add it's that Microsoft is free of changing the internal functionality, as you see in the customer comment concerning the SP1
Some months ago I talked regarding this topic in the blog http://blogs.msdn.com/b/calvarro/archive/2012/09/27/reflection-and-or-reverse-engineering-of-any-microsoft-sharepoint-version-is-not-supported.aspx so you can check the blog entry for more info.
In order to know what namespaces functions/methods and objects are public and supported in the SPS 2010 and SPS 2013 SDK for the JavaScript object Model, you should check the following links or the SDK:
SPS 2010 => http://msdn.microsoft.com/en-us/library/ee552096(v=office.14).aspx
SPS 2013 => http://msdn.microsoft.com/en-us/library/jj193034.aspx
It is available to download the updates regarding SharePoint 2010 December 2012 CU and MOSS 2007 December 2012 CU
SharePoint 2010 (Build 14.0.6131.5001)
SharePoint 2007 (Build 12.0.6670.5002)
I would like to let you know that today ends the full support of WSS 3.0 SP2 and MOSS 2007 including the CUs until WSS 3.0 SP3 and MOSS 2007 SP3.
So the minimal supported versión is WSS 3.0 SP3 and MOSS SP3
For more information, please check
http://support.microsoft.com/lifecycle/default.aspx?LN=en-gb&p1=12200&x=11&y=6
Thanks.
Good Afternoon
Probably some of you ,due to any automatic update in your SharePoint 2010 servers, may notice that opening the SP 2010 Management Shell you are prompted with the following messages:
Error: "The local farm is not accessible. Cmdlets withFeatureDependencyId are not registered."
Moreover, it turns out executing cmdlets you are having next error:
"Microsoft SharePoint is not supported with versión 4.0.30319.17929 of the Microsoft .Net Runtime."
As all we may know SharePoint 2010 is bulit on .NET 3.5 that relies on .NET 2.0. So, as PowerShell 3.0 uses .NET 4.0 , the assemblies compiled on .NET 3.5 of our SharePoint 2010 are not working.
Then, in order to solve this issue temporally you should modify the shortcut of the start menú of SP 2010 Management Shell and forcé it to use PowerShell 2.0 instead of PowerShell 3.0.
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe-NoExit - versión 2.0 "& 'C:\Program archivos de programa\Archivos comunes\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1'"
For more information you can check the next KB
http://support.microsoft.com/kb/2796733/en
Good morning.
As an update to the previous post Operating Systems supported for SharePoint 2010 installations.
http://blogs.msdn.com/b/calvarro/archive/2011/10/26/sistemas-operativos-soportados-para-instalaciones-de-sharepoint-2010-y-requerimientos-m-237-nimos.aspx
I would like to add:
- SharePoint 2010 ,until next SP2, it's not supported on any Windows Server 2012 http://support.microsoft.com/kb/2724471/en-us
- Remember for Windows SBS 2011 installations, as in Windows SBS 2008, It's only supported the version that comes with the operatiing system, SharePoint Foundation 2010.
- Windows 8 ,as in Windows 7, is only supported for code development installations with all the "Windows features" concerning .NET 3.5 activated and the App pools running in .NET 2.0 mode.
Thanks
It is available to download the updates regarding SharePoint 2010 October 2012 CU and MOSS 2007 October 2012 CU
SharePoint 2010 (Build 14.0.6129.5003)
SharePoint 2007 (Build 12.0.6668.5000)
Un post rápido para una aplicación útil. Remote Desktop Connection Manager nos permitirá manejar varias maquinas virtuales.
La podéis descargar de aquí
http://www.microsoft.com/en-us/download/details.aspx?id=21101
Un saludo.
Hello.
As you could notice this morning ,who will have WSUS activated on your servers, the security bulletin MS12-066 http://technet.microsoft.com/en-us/security/bulletin/MS12-066 (KB 2741517) applies to SharePoint 2010 and MOSS 2007. That hotfix fix a vulnerability that allows elevation of privileges.
As the hotfix is critical, it will be installed automaticaly. So, after the installation, it's mandatory to execute PSCONFIG on every single server of the farm => "psconfig –cmd upgrade –inplace b2b -wait" to complete the update process.
Thank you.
WSS 3.0 and MOSS 2007 products get into Extended Support from henceforth, as you can read in the following link.
http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=SharePoint+Server+2007&Filter=FilterNO
Once a product moves into extended support, several changes take place:
Customer can't ask for CDCR's.
Customer can ask and get Security fixes. However, ever, non-security hotfixes (RFH) will not be offered unless the customer purchase an Extended Hotfix Support Agreement witin next 90 days.
Support also ends for Enterprise Agreement custoemrs-
This support is still available.
For more info please check http://support.microsoft.com/gp/lifepolicy
How are you?
Recently, I'm finding on support cases, custom code developed by our customers that are based on some internal SharePoint functionalitities obtained by reserve engineering and/or custom code calls to private/internal SharePoint methods/properties through System.Reflection (What's Reflection?)
Please, I would like to inform you that those practices are totally unsupported and it's a violation of the EULA agreed during the installation of the product( Microsoft do not allow them) . For instance, you can watch the terms for SPS 2010
Besides the previous license terms violation, it could drive your environment to an unstable status or it could create side effects in your environment. Those properties/methods are intended to be used only by SharePoint source code. On the other hand, only the public API properties/methods in MSDN/ any SharePoint SDK version are the supported ones.
Eventually, you will be prompted to change your code to a supported one and the support case will be set as solved. If the new supported code is affected by the same misfunctionality the investigation will be carry on in a new support case.
I faced an interesting case some time ago that I would like to share with all of you. One of our customers were expenriencing time outs when creating a web applciation. I collected a memory dump and we foung the following call stack:
System.Threading.WaitHandle.WaitOne(Int64, Boolean)
System.Diagnostics.Process.WaitForExit(Int32)
Microsoft.SharePoint.Administration.SPAdministrationServiceUtilities.RunCommand(System.String,System.String, System.TimeSpan)
Microsoft.SharePoint.Administration.SPProvisioningAssistant.RegisterAspNetClientFiles()
Microsoft.SharePoint.Administration.SPWebApplication.Provision()
Microsoft.SharePoint.ApplicationPages.ExtendVirtualServerPage.BtnSubmit_Click(System.Object,System.EventArgs)
System.Web.UI.WebControls.Button.OnClick(System.EventArgs)
System.Web.UI.WebControls.Button.RaisePostBackEvent(System.String)
System.Web.UI.Page.RaisePostBackEvent(System.Web.UI.IPostBackEventHandler,System.String)
System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean)
System.Web.UI.Page.ProcessRequest(Boolean, Boolean)
System.Web.UI.Page.ProcessRequest()
System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)
ASP._admin_extendvs_aspx.ProcessRequest(System.Web.HttpContext)
System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)
System.Web.HttpApplication+PipelineStepManager.ResumeSteps(System.Exception)
System.Web.HttpApplication.BeginProcessRequestNotification(System.Web.HttpContext, System.AsyncCallback)
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext)
System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr,IntPtr, IntPtr, Int32)
System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
With not doubts, when the issue happened the provision of the SPWEbApplication was waiting for an external event and because of the method Microsoft.SharePoint.Administration.SPProvisioningAssistant.RegisterAspNetClientFiles() that appears on the top of the stack, it seemed that the culprit was IIS.
When we inspected the IIS manager. I found a big amount of application pools. As you probably know, SharePoint 2010 only supports10 application pools per WFE http://technet.microsoft.com/en-us/library/cc262787.aspx#WebserverAppServer (FYI MOSS 2007 only supports 8 application pools per WFE)
However, we applied a simple work around until the customer will reduce the number of application pools. Directly we tuned the shut down time and the ping time to 300 seconds whne a enw IIS application pool will be created.
I hope this will help you.