Announcement

Collapse
No announcement yet.

SBS2008 freezes 3 times a week, maybe due to DCOM errors ????

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SBS2008 freezes 3 times a week, maybe due to DCOM errors ????

    Hello evrybody,

    first I apologize for my poor english, I am program developer in a small french company, with about 20 users on a DC SBS2008 + Exchange2007, and I am also in charge of the server maintenance

    Well, here is the matter : I encounter many freezes of the server that I am not able to diagnose, and my users become more and more on nerve !

    When it occurs, on the SBS I can't log into, I cannot ping it from other computer, everything is freezed.

    After rebooting, I go into log viewer and see that there are DCOM errors on the entier day, about every 20 minutes, like :

    DCOM n'a pas pu communiquer avec l'ordinateur EXPEDITIONS.mondomaine.local en utilisant les protocoles configurés.


    sorry for french, I suppose in english it's something like :

    DCOM was unable to communicate with the computer EXPEDITIONS.mondomaine.local using any of the configured protocols
    And a few minutes before every freeze, in logs, there are always those kind of errors :

    Échec du traitement de la stratégie de groupe. Windows n’a pas pu s’authentifier auprès du service Active Directory d’un contrôleur de domaine. (Échec de l’appel de fonction de liaison LDAP). Consultez l’onglet des détails pour plus d’informations sur le code d’erreur et la description.

    in english => Windows could not authenticate to the Active Directory service on a domain controller.

    then

    Le serveur {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} ne s’est pas enregistré sur DCOM avant la fin du temps imparti.

    in english => The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout

    then nothing....
    So I contact you, who are used to this system, because I am lost !

    I put in attachment an archive of the logs before each freeze, maybe it will help.

    Thank you in advance for any help.

    bvadam
    Attached Files

  • #2
    Re: SBS2008 freezes 3 times a week, maybe due to DCOM errors ????

    Sorry, but absolutely no way will I (or most other members) open a zip file from an unknown source
    Can you please post as TXT -- they may be larger, but a lot safer
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: SBS2008 freezes 3 times a week, maybe due to DCOM errors ????

      Don't worry, I have put it in a zip file because there are 2 files inside, in .evtx format. As a consequence, I can't post them in txt format..... an other solution ?

      Comment


      • #4
        Re: SBS2008 freezes 3 times a week, maybe due to DCOM errors ????

        Can you not export from the event log as CSV or some other plain format?

        You say it only contains 2 evtx files, but how does anyone else know that?
        (Not that we don't trust you, just most members take IT security very strongly!)
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Re: SBS2008 freezes 3 times a week, maybe due to DCOM errors ????

          I can export it in XML with the LogViewer xml export tool, but nothing else....

          Will it be ok ?

          EDIT : sorry I've found that I could export to txt, but still in french .....


          Niveau Date et heure Source ID de l’événement Catégorie de la tâche
          Information 04/10/2012 11:26:33 Service Control Manager 7036 Aucun Le service Service de découverte automatique de Proxy Web pour les services HTTP Windows est entré dans l’état : en cours d'exécution.
          Erreur 04/10/2012 11:21:59 Microsoft-Windows-GroupPolicy 1006 Aucun Échec du traitement de la stratégie de groupe. Windows n’a pas pu s’authentifier auprès du service Active Directory d’un contrôleur de domaine. (Échec de l’appel de fonction de liaison LDAP). Consultez l’onglet des détails pour plus d’informations sur le code d’erreur et la description.
          Erreur 04/10/2012 11:19:26 Microsoft-Windows-DistributedCOM 10010 Aucun Le serveur {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} ne s’est pas enregistré sur DCOM avant la fin du temps imparti.
          Erreur 04/10/2012 11:18:59 Microsoft-Windows-GroupPolicy 1006 Aucun Échec du traitement de la stratégie de groupe. Windows n’a pas pu s’authentifier auprès du service Active Directory d’un contrôleur de domaine. (Échec de l’appel de fonction de liaison LDAP). Consultez l’onglet des détails pour plus d’informations sur le code d’erreur et la description.
          Information 04/10/2012 11:18:44 Service Control Manager 7036 Aucun Le service Programme d’installation de modules Windows est entré dans l’état : arrêté.
          Erreur 04/10/2012 11:14:38 Microsoft-Windows-DistributedCOM 10010 Aucun Le serveur {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} ne s’est pas enregistré sur DCOM avant la fin du temps imparti.
          Information 04/10/2012 11:12:45 Service Control Manager 7036 Aucun Le service Service de découverte automatique de Proxy Web pour les services HTTP Windows est entré dans l’état : arrêté.
          Last edited by bvadam; 9th October 2012, 13:37.

          Comment


          • #6
            Re: SBS2008 freezes 3 times a week, maybe due to DCOM errors ????

            When the server freezes does it crush/restarts. Does anything work on it? Don't think it has anything to do with DCOM. I see this sort of messages on many servers and usually they can be ignored. It would be worth setting up procdump from SystemInternals if you can determine what triggers the freeze. If it's the processor you can set up to collect dumps when say the CPU usage exceeded 90%. It could help to find which process is responsible for what happens. If freezes only partially so you can still use the mouse and start some applications keep procmon handy as again this can help pinpointing the cause of the problem.
            What's worth doing is check your drivers and see if you can update anything. Especially RAID controller and NIC

            Comment

            Working...
            X