SharePoint : Gestion des Erreurs 6398, 7076 et 6482

 Dans une de mes fermes SharePoint MOSS, je suis tombé sur une répétition toutes les 1 a 2 minutes des erreurs 6398 :

---

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Timer
Event ID:    6398
Date:        6/29/2009
Time:        2:42:19 PM
User:        N/A
Computer:    xxxxxxxxxxxxxxxxxxxxx
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 68fe9ed3-1254-470f-bd92-74d2a35ec018) threw an exception. More information is included below.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---

Ainsi que des erreurs 7076 :

---

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    7076
Date:        6/28/2009
Time:        3:22:19 AM
User:        N/A
Computer:    xxxxxxxxxxxxx
Description:
An exception occurred while executing the Application Server Administration job.

Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Techinal Support Details:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.DirectoryServices.Interop.UnsafeNativeMethods.IntADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.Interop.UnsafeNativeMethods.ADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_IsContainer()
   at System.DirectoryServices.DirectoryEntries.CheckIsContainer()
   at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.Find(String name)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.get_Item(String name)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.Office.Server.Administration.SharedWebServiceInstance.CreateSharedWebServiceApplicationPool(SharedResourceProvider srp)
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---

et 6482 :

---

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    6482
Date:        6/21/2009
Time:        10:08:19 PM
User:        N/A
Computer:    xxxxxxxxxxxxxxx
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (bf523f37-c8dc-44ef-a5df-aa04d095f2e5).

Reason: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Techinal Support Details:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.DirectoryServices.Interop.UnsafeNativeMethods.IntADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.Interop.UnsafeNativeMethods.ADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_IsContainer()
   at System.DirectoryServices.DirectoryEntries.CheckIsContainer()
   at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.Find(String name)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.get_Item(String name)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.Office.Server.Administration.SharedWebServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---

Après de nombreuses recherches pour fixer ces erreurs, ou on trouve par exemple des problèmes de paramétrage COM :

• http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/b951e1f5-520e-4f20-9fa9-ba6f510f1826
• MOSS Errors
• SharePoint Execute Method Exception (Event ID 6398)
• …

On pense alors avoir trouvé la solution, mais il n’en est rien, en réalité, les deux erreurs sont différentes, car celle observée fait références à des erreurs de la lecture/écriture mémoire alors que les corrections sont liées à des erreurs COM

L’erreur n’était visible que sur le serveur d’application (Il faut donc bien contrôler tous les serveurs de sa ferme) et provenait du moteur de recherche qui partait en boucle sur certaines sources de contenu (plus de 1500 Heures).

Il a donc fallu redémarrer le serveur d’application puis faire un stop de l’indexation en cours des sources de contenu et un stop du service de recherche (NET STOP OSEARCH), qui se relance immédiatement tout seul.

Ainsi après plusieurs exécution de ces deux scripts (PowerShell et NET STOP), les indexations en cours ont pu être finies et la situation stabilisée.

Tout est maintenant rentré dans l’ordre.

Il est donc extrèmement important de surveiller les serveurs de ses fermes SharePoint, particulierement le Serveur d’indexation lorsqu’on possède de nombreuses sources de contenu.

Romelard Fabrice [MVP]