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
Hello
Maybe most of you have faced the following VS 2010 error message when trying to debug or deploy a wsp file via VS 2010 in a multi-server farm:
Error occurred in deployment step 'Activate Features': Feature with Id '2447ad0c-98d2-4363-9ef0-f217694f804e' is not installed in this farm, and cannot be added to this scope.
Basically the error happens because VS 2010 do not support features activation on multi-server farms.
However ,the devil is in the details, the exact explanation is in a previous step. It turns out that VS 2010 internally implements a call to the method SPSolution.DeployLocal http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spsolution.deploylocal.aspx . That method is intended for troubleshooting purpouses of wsp files and as you can read on the MSDN documentation it performs a local deployment instead of an immediate deployment (Only to one sever of the farm)
Therefore, the only solution to avoid the situation is to compile the code (build o re-build) , go to the VS 2010 top menu and select build -> package. After that a new wsp file will be created on the BIN folder of the project.
Eventually, now you are free of selecting ,PowerShell or STSAdm, in order to add a solution, deploy it and activate it
Thanks
Kind Regards.
Héctor Calvarro Martín. SharePoint Dev. Microsoft Support Engineer for DEV EMEA
Tweet
HI
It is available to download the updates regarding SharePoint 2010 for April 2012 and MOSS 2007 for April 2012
SharePoint 2010 (Build 14.0.6120.5000)
(REMEMBER TO INSTALL BEFORE THE SP1)
If SPS 2010 installed you must only install the SPS 2010 CU because it includes the Foundation one.
After installing the updated you should run the SharePoint Config Wizard in every server of the farm.
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.6661.5000)
Warning! This update will not be installed if you are not updated to SP3.
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.
Thank you so much.
Cheers.
Hi.
I would like to remind that SQL Server 2012 is not supported on WSS 3.0/MOSS 2007.
Basicaly, The supportability of products is normally the minimum requirement + 2 versions, unless exceptions. So in this case, the minimum requirement is SQL Server 2000 and the next two versions are SQL Server 2005 and SQL Server 2008/R2.
Furthermore, If you want to use it on SharePoint 2010 SP1 you have to be installed at least on the SP1, as you can check on the following url:
http://support.microsoft.com/kb/2460045
Thanks.
Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA
How are you?
Unfortunately, I was dealing with this issue for a while, looking for info on the Internet and I didn't find anything. So I decided to use some internal resources in order to solve it.
I was facing the error Windows cannot connect to the printer, Operation failed with error 0x00000057 when adding a new printer with admin privileges.
The curious thing was that the printer was working before however ,after a global outage on the printer server, it gave up working and disappeared from printer devices.
Basically, all pointed that the root cause was a bad driver or bad connection. Then I decided to go deeper and to open a regedit.exe window. I was checking the windows register and I found that there were existent printer connections on the regkey HKEY_CURRENT_USER\Printers\Connections\[NAME OF THE NETWORK PRINTER]. I deleted them, tried to add again the printer and all worked like a charm.
Hola
Se necesita instalar Lync CU 4 (ya que se necesita el rol de Lync Mobile).
Si no, la aplicación no funcionará (via MVP Juan Carlos González http://jcgonzalezmartin.wordpress.com/ )
Ya está disponible el cliente de Lync para Window phone. Obviamente para que funcione se necesita Lync Server o una cuenta de Lync Online/Office 365.
Características principales:- Ver la disponibilidad de los colegas en tiempo real y seleccionar el modo más oportuno de establecer comunicación: mediante un mensaje instantáneo (MI), correo electrónico o llamada telefónica.- Conectar con las llamadas de conferencia de Lync con un solo toque, sin necesidad de escribir largos códigos de acceso numéricos o números de conferencia. - Realizar y recibir llamadas utilizando solo el número de telefonía IP empresarial (Lync ID); por tanto, puede establecer contacto con otros usuarios utilizando una identidad única y coherente.- Lync 2010 para Windows Phone proporciona seguridad de la capa de transporte (TLS) y protección de red interna/de perímetro sin necesidad de una VPN; por tanto, su experiencia de comunicación será segura con independencia de dónde se encuentre o qué red utilice.
El enlace para la descarga http://www.windowsphone.com/es-ES/apps/9ce93e51-5b35-e011-854c-00237de2db9e
Muchas Gracias.
Un saludo.
Hi!!
If you have Service Pack 3 for SharePoint Server 2007 installed, and you try to install this cumulative update package, you may encounter an error that states that "the expected version of the product was not found on the system." If this issue occurs, run the package executable (.exe) file at a command prompt and set the PACKAGE.BYPASS.DETECTION.CHECK=1 switch to the following setting.
For x86: "office-kb2596986-fullfile-x86-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1"
For x64: "office-kb2596986-fullfile-x64-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1"
THX!!
After the public availability of the SharePoint 15 CTP, now we have a new announcement SharePoint 15 SDK CTP has been released.
http://www.microsoft.com/download/en/details.aspx?id=28768
It's intended to provide an overview of the future SharePoint 15 object model in order to take in account on future migrations or on new developments.
Btw, i would like to remind you:
Community Technical Preview (CTP) builds do not go through the same rigorous testing that beta builds undergo. While betas receive a much higher level of testing and feature work, CTPs are intended to expose developers to the latest working build. CTPs are therefore unsupported, prerelease software and there are some precautions you should take. Please read the latest Readme and Installation Guides before you download or install prerelease software.
Kind regards
UPDATE ==> IT WILL BE FIXED ON APRIL 2012 CU FOR SPS 2010 AND ON JUNE 2012 for MOSS 2007
Hi all
I would like to inform that MOSS 2007 and SPS 2010 output cache stops working after installing security update for the .NET MS11-100 KB2656362 http://support.microsoft.com/kb/2656362 and KB2656352 http://support.microsoft.com/kb/2656352 . It is reported and the Product Group is working on a fix.
Please, it's recommended from your side to measure if you want cache on the environment but to be impacted by security issues or to be secure but without any output cache.
On Spanish available in the Spanish SharePoint Support Team Blog
Ya están disponibles para su descarga las actualizaciones de Diciembre 2011 para SharePoint 2010
SharePoint 2010 (Build 14.0.6114.5000)
(RECORDAD INSTALAR ANTES EL SP1)
Si teneis SPS 2010 sólo debeis instalar el relativo a SPS 2010 ya que incluye el de Foundation.
Tras instalar las actualizaciones se deberá ejecutar el Asistente de Configuración en cada servidor de la granja.
Por último, recordad que después de aplicar este CU necesitáis reiniciar el servicio de sincronización de perfiles.
Gracias.
Hola!!
Ya están disponible para su descarga la actualización de Diciembre 2011 de WSS 3.0.
WSS 3.0 (Build 12.0.6656.5000)
Aviso! Esta actualización no se instalará si no se encuentra instalado ya el SP3 en el entorno.
Por desgracia el de MOSS 2007 se ha retrasado saldrá en los próximos días ya os avisaremos.
Tras instalar las actualizaciones se deberá ejecutar el Asistente de Configuración en cada servidor de la granja o “psconfig –cmd upgrade –inplace b2b -wait”
Ya está disponible el paquete para MOSS 2007 que sufrió el retraso.
La versión de WSS 3.0 la encontrareis en http://blogs.msdn.com/b/calvarro/archive/2011/12/14/disponible-acumulativo-de-diciembre-2011-para-wss-3-0-el-de-moss-2007-retrasado.aspx
El orden, como siempre, será instalar primero las actualizaciones de WSS 3.0, y posteriormente las de MOSS 2007.
Un saludo
Click on this sentence for this article in Spanish; Available on the Spanish SharePoint Support Team blog.
Hi
Most of you have faced the following bug after uploading a photo to a root MySite site collection:
The issue is because of a regression on the October 2011 CU. The steps to repro it:
Users cannot upload pictures to mysite configured on root site collections of a web app
1. Create a Mysite collection for UPA2. Install OctCU3. Goto mysite as a user and try to change his picture
Unfortunately, There isn't any easy workaround for that however the issue has been fixed in the December CU 2011 (It will be released circa December 27th 2011)
Thank you.
Today, I've been contacted by my fellow colleague from the CRM team, Fausto Cipriani. He wanted me to lend him a hand with a case related to integration between Dynamics CRM 2011 List Component and SharePoint 2010.
It turns out that one of his customers when trying to connect to one of the Documents connections he retrieves something like a SharePoint 2010 embeded page in an iframe instead of the view of the connector. For instance
We proceed to check the hot spots regarding how to set up the connector:
The previous points were right configured. The customer informed us that his administrator user was not having the issue but other administrators were having it, besides the some users.
Checking the url that the connector were connecting to, it failed when connecting to a child site. Furthermore when we were checking if the feature was activated, I noticed that the feature was a site collection feature and not a site feature (That means that the feature only appears on the top site instead on every site, appears in Manage Site Collection Feature y not in Manage Site features)
I thought to myself if any user that was failing had credential/rights on the top/parent site. We checked that it hadn't any right so we granted viewers only rights, the issue dissapeared and the documents view appeared properly. For instance (BTW, the user didn't have any document)
Then, if the connector it is configured against a child site that belongs to a site collection that has a hierarchy it's needed ,at least, to grant viewers only credentials to the user in the parent site that is belonging the feature.
Potential explanation of the issue
My point of view about why this issue is hapenning is:
As the feature is a site collection feature, the connector custom code needs that the user logged has credentials on the parent site because if not the internal logic of the connector could be failing and it's not able to complete the action of listing the documents and set the right documents view
Unfortunately, this is only an assumption because I do not have any oficial statement from the CRM Product Group nor the SharePoint Product Group
Eventually, I would like to point you to the following urls about how to set up the connector and the official download page of the connector:
http://social.technet.microsoft.com/wiki/contents/articles/4324.aspx
http://www.microsoft.com/en-us/download/details.aspx?id=5283
Thank you so much
Hay veces que configurando Visual Studio vas tan rápido que de repente no te das cuenta y seleccionas una plantilla de programación que no se corresponde con la cual quieres adoptar. Pues nada más fácil para resetearlo, ir a tools, Import and Export settings y clickar en reset all settings. Después de esto os preguntará si queréis guardar los settings actuales y finalmente podréis seleccionar el tipo de proyecto.
Ayer por la mañana en Estados Unidos se realizó la conferencia para desarrolladores Build y como sabeis se presento la Developer Preview de Windows 8. Aclarar que no es la Beta, es un versión anterior a la Beta donde se muestran las capacidades del Sistema Operativo para el desarrollo de aplicaciones.
La gran novedad de esta presentación ha sido la interfaz Metro (Interfaz que ya aparecia en los dispositivos WP7) la cual facilita la experiencia de usuario además de que esta versión de Windows es totalmente tactil. No obstante la interfaz antigua de windows seguirá existiendo con novedades como el estilo Ribbon de Office en algunos menus del sistema operativo. Otros hints importantes son IE 10, la integración completa de Windows con Skydrive o una integración con Windows Store para que los desarrolladores puedan vender sus apps.
También se ha lanzado un nuevo site (hub) para desarrolladores de applicaciones en Windows llamado Windows Dev Center que centraliza toda la información que se necesite sobre C#, HTML 5, construcción de applicaciones en metro etc. http://msdn.microsoft.com/en-us/windows/home/
Por último compartir los enlaces de descarga y también recordaros que si tenéis subscripción MSDN hay disponibles más cosas relativas a Windows 8 para descargar como el SDK. (Yo sin duda me quedo con la iso que trae Visual Studio y las demos ;) )
Link de descarga de Windows 8:
http://msdn.microsoft.com/en-us/windows/apps/br229516
Link para comenzar a desarrollar applicaciones en metro:
http://msdn.microsoft.com/en-GB/windows/apps
PS:¡¡Yo ya me la estoy bajando!!!
It is available to download the updates regarding SharePoint 2010 June 2012 CU
SharePoint 2010 (Build 14.0.6123.5000)
Desde Outlook 2007 se ha deshabilitado el protocolo Outlook como informa el KB 929590 http://support.microsoft.com/kb/929590/es
El protocolo de Outlook ya no funciona fuera de Outlook
Se ha cambiado el protocolo de Outlook (Outlook://). Este protocolo sólo funcionará cuando se utilice en Outlook. Puede utilizar este protocolo en la página principal de una carpeta, en la barra de herramientas Web o en el cuerpo de un elemento de Outlook.
Nota: Outlook no reconoce automáticamente el protocolo de Outlook cuando lo escribe en el cuerpo de cualquier elemento. Sin embargo, el protocolo funciona si lo establece como un hipervínculo.
Para volverlo a habilitar hay que hacer unos ligeros cambios en el registro de Windows creando unas nuevas claves. Para conseguirlo, hay que descargar el archivo zip adjunto y aplicar el regedit correspondiente, dependiendo de la versión de office.
Acto seguido ejecutar en Internet explorer outlook:inbox y comprobaréis como el protocolo funciona perfectamente.
El grupo de producto de Windows por medio de Sam Moreau ,Principal Director of User Experience for Windows, ha presentado el nuevo Logo de Windows 8.
En la presentación del logo se ha hecho una retrospectiva historica de los logos de Windows y sus caracteristicas.
Para más información sobre el logo y esa retrospectiva podéis consultar la comunicación oficial del grupo de producto.
http://windowsteamblog.com/windows/b/bloggingwindows/archive/2012/02/17/redesigning-the-windows-logo.aspx
Available in Spanish on HablaMOSS blog
The other day I wanted to run some test regarding Lync Server 2010 and SharePoint. Unfortunately, I found the next error message:
"Not Available: Failure occured while attemmpting to check the schema state. Please ensure Active Directory is reachable"
After some time pulling my hair out checking DNS settings, DC connections and so on I decided to check the official documentation.
Unfortunately, I found that I was wasting my time in something that was unsupported :(
"You cannot collocate any Exchange Unified Messaging (UM) component or SharePoint component with any Lync Server role."
http://technet.microsoft.com/en-us/library/gg398102.aspx
Next time I will read the documentation first instead of doing experiments :) .
Ya esta disponible la versión BETA de Skype para Windows Phone 7.
Podéis descargar la versión beta de manera gratuita dando clic aquí desde tu Windows Phone CLICK (con el cliente Zune no fucniona) o escanenando el código QR de debajo (Se necesita estar Mango –7.5-)
Estos son algunos de los equipos ya certificados para Skype for Windows Phone:
• Nokia Lumia 710 • Nokia Lumia 800 • HTC Titan • HTC Radar • Samsung Focus S • Samsung Focus Flash
Gracias
Some months ago I faced a case in somehow curious regarding to the method SPWeb.GetSiteData(p) http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spweb.getsitedata.aspx . It turns out that the following code snippet was not generating the expected table of items:
try
{ //Some code rgarding SPSiteDataQuery p
DataTable dt = SPContext.Current.Site.RootWeb.GetSiteData(p);
//Some code
}
catch (Exception e)
{
The issue was that in order to use this method you need to use a explicit SPWEB, so the code should be coded in this way:
{ //Some code regarding SPSiteDataQuery p
SPSite Siteh = SPContext.Current.Site;
using (SPWeb Webh = Siteh.OpenWeb())
DataTable dt = Webh.GetSiteData(p);
//Some Code
Eventually, to sum up, it seems to be by design (I didn't double check with USA Product Group) but the statistics regarding the items seems to be calculated when you instace the new SPWeb in an explicit way
Kind regards.
He de reconocer que me encantan este tipo de posters con todas los shortcuts de funcionalidades de programas. Por lo cual os dejo los posters referentes a Visual Studio 2010 y sus lenguajes (C#,J#, C++ etc) que seguro que os son de utilidad.
Se pueden descargar de aquí.
http://www.microsoft.com/en-us/download/details.aspx?id=13189
Good Afternoon.
Some days ago one of our customers was updating a MOSS 2007 environment from RTM to SP3, without applying any update between RTM and SP3. He opened a support case and reported the following issue.
[SPWebTemplateSequence][ERROR] [15/05/2012 9:43:19]: Template OSRV#0: Exception thrown in activatingSPSite scoped features for SPSite with URL http://centraldamin/ssp/admin(Id=21cc6e91-21f0-4393-b13a-f60bb5610c46). Skipping this SPSite for template upgrade. Exception: System.InvalidOperationException: La característica '2b1e4cbf-b5ba-48a4-926a-37100ad77dee' no está instalada en este conjunto. No puede agregarse a este ámbito.
en Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId,SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly) en Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId, Boolean force) en Microsoft.SharePoint.Upgrade.SPWebTemplateSequence.ActivateSiteFeatures(List`1 lstsiteidToUpgrade, List`1& lstsiteidExceptions, List`1& lstwebinfoExceptions
Fortunately, the error is old known issue. It turns out that the Infrastructure update installs new features related to the Central Admin and to the Share Services Providers.
In order to solve it, it's need to install those feature using the command psconfig.exe -cmd installfeatures
Then the customer pointed us to a blog from a former Microsoft fellow talking in a further detail about that feature in subject:
"2b1e4cbf-b5ba-48a4-926a-37100ad77dee', is basically the “S2SearchAdmin”"
So for more info I would like to share with all of you the blog that the customer pointed.:
http://blogs.msdn.com/b/jjameson/archive/2009/01/23/error-installing-moss-2007-december-cumulative-update.aspx
I hope it will be useful for you.
Hola.
Como todos sabréis por las últimas noticias del CES, Kinect va a estar disponible para Windows en RTM a partir del 1 de Febrero de 2012. Por ello me gustaría compartir con vosotros dos páginas indispensables para todos aquellos que empiecen en este mundo para Windows.
Página de lanzamiento de Producto con toda la información relevante y características
http://www.microsoft.com/en-us/kinectforwindows/
Blog Corporativo sobre Kinect for Windows.
http://blogs.msdn.com/b/kinectforwindows/
¿Estás ya preparado para construir el futuro?
Today, the support of SharePoint 2010 versions between RTM(14.0.4762.1000) and SP1 (14.0.6029.1000) is ended as you can double check in the following link:
http://support.microsoft.com/lifecycle/?p1=14944
That is because the SP1 was released one year ago and ,as you may know, the Office Business Group Service Pack policy states "When a new service pack is released, Microsoft will provide 12 months of support for the previous service pack". More info in the following link:
http://support.microsoft.com/lifecycle/#tab2
Then, the new support cases opened regarding issues between RTM and SP1 versions will be treated as "limited support". That means that you will face the following limitations:
For more info:
http://support.microsoft.com/gp/newsplifecycle
So, please, I would like to recommend you to install at least SharePoint 2010 SP1 + any of the latest cumulative updates to keep your infraestructure fully supported. To install the SP1 you could follow the following link:
http://blogs.msdn.com/b/calvarro/archive/2011/06/28/sharepoint-2010-sp1-y-june-cu-2011.aspx