Cuando implementamos soluciones en SharePoint muchas veces no encontramos el detalle de un error en la aplicación; en esos casos, se puede ingresar a los log files de sharepoint a ver el detalle de la ejecuciòn del portal.
La ubicación por defecto es:
“C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12LOGS”
En el servidor web.
Espero que sea de ayuda Sigue leyendo
En una entrada anterior publiqué un método para cargar archivos desde cualquier aplicación web; en este caso publico la misma funcionalidad desde el control upload de infopath forms services.
Deben utilizar un botón adicional al cual le añaden el siguiente codigo .net:
public void btnCargarDocumento_Clicked(object sender, ClickedEventArgs e)
{
XPathNavigator DOM = this.MainDataSource.CreateNavigator();
XPathNavigator fileDocumento = DOM.SelectSingleNode(“/my:misCampos/my:att_documento”, NamespaceManager);
byte[] attachmentNodeBytes = Convert.FromBase64String(fileDocumento.Value.ToString());
int fnLength = attachmentNodeBytes[20] * 2;
byte[] fnBytes = new byte[fnLength];
for (int i = 0; i < fnBytes.Length; i++)
{
fnBytes[i] = attachmentNodeBytes[24 + i];
}
char[] charFileName = System.Text.UnicodeEncoding.Unicode.GetChars(fnBytes);
string fileName = new string(charFileName);
fileName = txtIdActividad.Value + “-” + fileName.Substring(0, fileName.Length – 1);
byte[] fileContents = new byte[attachmentNodeBytes.Length – (24 + fnLength)];
for (int i = 0; i < fileContents.Length; ++i)
{
fileContents[i] = attachmentNodeBytes[24 + fnLength + i];
}
string LibreriaDestino = “http://SERVIDOR:8001/sitio/sitiodocs/documentosA/”;
string Destino = LibreriaDestino + fileName;
System.Net.WebClient objWebClient = new System.Net.WebClient();
objWebClient.Credentials = System.Net.CredentialCache.DefaultCredentials;
objWebClient.UploadData(Destino, “PUT”, fileContents);
//limpiar el control upload
if (!fileDocumento.MoveToAttribute(“nil”,
fileDocumento.LookupNamespace(“xsi”)))
{
fileDocumento.SetValue(“);
}
}
Espero que sea de ayuda Sigue leyendo
Fabian Imaz ha elaborado una serie de artículos acerca de sharepoint 2010 que son muy interesantes:
– Como crear y configurar sitios en microsoft SharePoint 2010
– Nueva barra Ribbon en SharePoint 2010
– Cambio de BDC a BCS
– SharePoint Designer 2010
Es de mucha ayuda para comenzar a revisar SharePoint 2010
Además pueden descargar la versión Beta en el siguiente link:
Un dato muy importante para realizar un upgrade de SharePoint es saber el tiempo de inactividad de la intranet mientras se realiza esta actualización.
Como parte de las buenas prácticas es recomendable hacer el upgrade de sharepoint services 3.0 hacia el sp2 y luego el upgrade de sharepoint server sp2. El tiempo de inactividad de la intranet depende de la cantidad de sitecollections que se han implementado en tu intranet; para intranets con 1 solo site collection debería estar demorando alrededor de 15 minutos; en cambio para una intranet con 25 site collections el tiempo estimado es de 1 hora.
Esto debido a que el upgrade se hace a cada una de las bases de datos de cada sitecollection, al hacer el upgrade se genera un log de la actualización que nos muestra como analiza el estado de upgrade en cada base de datos de cada site collection.
[SPHierarchyManager] [DEBUG] [12/2/2009 5:45:43 PM]: ——————– End Growing Tree ——————–
[SPManager] [INFO] [12/2/2009 5:45:43 PM]: Resetting the status of PersistedUpgradableObject: SPContentDatabase Name=WSS_Content1 Parent=SPDatabaseServiceInstance to Online.
[SPManager] [INFO] [12/2/2009 5:45:43 PM]: Finished upgrading SPContentDatabase Name=WSS_Content2 Parent=SPDatabaseServiceInstance.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content3 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content4 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content5 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content6 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content7 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content8 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content9 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT10 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT11 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT12 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT13 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT14 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT15 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: True.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT16 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: True.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT17 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: True.
Espero que esta información les ayude al momento de realizar actualizaciones en sus servidores sharepoint 2007. Sigue leyendo
MOSS 2007 or WSS 3.0 SP2 + Cumulative update (June 09) 12.0.0. 6510
MOSS 2007 or WSS 3.0 SP2 + Cumulative update (April 09) 12.0.0. 6504
MOSS 2007 or WSS 3.0 SP2 12.0.0.6421
MOSS 2007 or WSS 3.0 Cumulative update (Feb 09) 12.0.0. 6341
MOSS 2007 or WSS 3.0 Cumulative update (Dec 08) 12.0.0. 6335
MOSS 2007 or WSS 3.0 Cumulative update (KB956056 – KB956057) 12.0.0.6327
MOSS 2007 or WSS 3.0 Infrastructure Update (KB951695 – KB951297) 12.0.0.6318
MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB948945) 12.0.0.6303
MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB941274) 12.0.0.6301
MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB941422) 12.0.0.6300
MOSS 2007 or WSS 3.0 SP1 12.0.0.6219
MOSS 2007 or WSS 3.0 October public update 12.0.0.6039
MOSS 2007 or WSS 3.0 August 24, 2007 hotfix package 12.0.0.6036
MOSS 2007 or WSS 3.0 RTM 12.0.0.4518
MOSS 2007 or WSS 3.0 Beta 2 TR: 12.0.0.4407
MOSS 2007 or WSS 3.0 Beta 2: 12.0.0.4017
Office 12 (PDC image – pre-beta): 12.0.0.3111 Sigue leyendo
Detalles del Event Log:
Event Id: 7076
Event Source: Office SharePoint Server
The Message text will contain:
– “Microsoft.Office.Server.Search.Administration.
SearchAdminSharedWebServiceInstance”
– “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.”
– A reference to the Metabase in the call stack.
Event Id: 6398
Event Source: Windows SharePoint Services 3
The Message text will contain:
– “Microsoft.Office.Server.Administration.
ApplicationServerAdministrationServiceJob”
– “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.”
Event Id: 6482
Event Source: Office SharePoint Server
The Message text will contain:
– “Microsoft.Office.Server.Search.Administration.
SearchAdminSharedWebServiceInstance”
– “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.”
– A reference to the Metabase in the call stack.
La solución es aplicar el hotfix
946517
PlanetaPeru: buscador del Perú Sigue leyendo