The ConfigMgr console could not connect to the ConfigMgr site database

Hoy repentinamente nos encontramos con que ninguna consola de SCCM se podia utilizar, obteniendo el error:

"The ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site server and SMS Provider computers. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console Connections" in ConfigMgr Help"

Revisando el archivo de log SMSADMINUI.log obteniamos las siguientes lineas:

Error Code:
InvalidClass
\r\nSystem.Management.ManagementException\r\nInvalid class \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
errorCode)
at
System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()

at
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsO
bject.d__0.MoveNext()\r\nManagementException details:
instance of __ExtendedStatus
{
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE ReportingSiteCode = ''"; ProviderName = "WinMgmt"; }; \r\n
[4][8/8/2008 1:09:29 PM] :Failure while loading required 'WQL' query engine, console cannot connect

Cause: The SMS provider WMI instance was missing



RESOLUCION:

Compilar smsprov.mof utilizando el comando:

mofcomp smsprov.mof

Este archivo se encuentra en C:\Program Files\Microsoft Configuration Manager\bin\i386

Saludos!

Consigue un examen de seguridad gratuito de tu PC

Microsoft ofrece un examen online de Seguridad, la herramienta Windows Live OneCare (en version beta) es un sistema gratuito que permite:

  • Comprobar la existencia de virus y eliminarlos
  • Eliminar del disco duro los elementos inservibles
  • Mejorar el rendimiento de tu PC

Actualización acumulativa de las Zonas Horarias de Windows

Ya disponible el KB951072, el cual incluye la actualización de la zona horaria de Argentina.

Si ya tuviste problemas con el cambio de horario de Argentina, del año pasado, con esta actualización, ya no tendrás que correr scripts, ni generar nuevas claves del registro en forma manual.

Sharepoint failed in event OnPostRestore

Recientemente tuvimos que restaurar la farm completa en un servidor para hacer algunas pruebas, restaurando el backup de produccion en esta nueva farm obteniamos el siguiente mensaje de error:

Object WSS_Content failed in event OnPostRestore. For more information, see the error log located in the backup directory. SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=SharePoint - 80 Parent=SPWebService is being updated by Domain\sharepoint_service, in the OWSTIMER process, on machine MACHINENAME. View the tracing log for more information about the conflict.

Investigando en la web dimos con la solucion, sigan los pasos siguientes obtenidos de http://support.microsoft.com/kb/939308

  • Stop the Timer service "Windows SharePoint Services Timer"
  • In Windows Explorer, locate and then double-click the following folder: C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUIDNotes
  • Back up the Cache.ini file.
  • Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt. Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
  • Double-click the Cache.ini file. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu.
  • Start the Timer service "Windows SharePoint Services Timer"
  • Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
  • Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
Espero les sea de utilidad.

Sharepoint Exception from HRESULT: 0x80041050

Hoy tuvimos un el error "Exception from HRESULT: 0x80041050" en nuestro entorno de test, la solucion la encontramos en esta pagina, paso a resumir los pasos realizados:

- abrir la consola de SQL (SQL Server Management Studio )
- sobre la base de contenidos de la aplicacion que da error ejecutar la siguiente Query:

select *
from AllDocs
where (VirusStatus > 0) and (VirusStatus is not null)

- Si obtenemos algun resultado, ahi esta el problema!, debemos ejecutar:

update AllDocs
set VirusStatus = null
where (VirusStatus > 0) and (VirusStatus is not null)

Listo, problema solucionado.