locked
Problems with Agentless Exception Monitoring RRS feed

  • Question

  •  

    Hello,

     

    i'm testing the SCE 2007 SP1 Server and i got stuck with the AEM Feature.

    I have several VISTA Test Machines in my Test Domain and not one reports Problems (App Crashes / OS Crashes) to

    the SCE Server. All Clients have the right GPO Settings and reporting Performance Data etc back to the Server.

    Only the AEM is not working. Any Clues or Hints?

     

    Olaf

     

    Tuesday, April 1, 2008 12:39 PM

Answers

  • Hi Olaf,

    Is there any error in the Event Viewer on SCE server?

    Also, please open SCE console, navigate to "Monitoring" space, choose "Agentless Exception Monitoring", choose “crash listener view" and "application view" to check whether there is any information

    --------------------
    Regards,
    Eric Zhang



    Monday, April 21, 2008 8:40 AM

All replies

  • Hi Olaf,

    Did you enable AEM on the SCE server?

    Please open SCE console, navigate to administration space, run the "Feature Configuration wizard" and make sure AEM is enabled(choose "yes, collect application error" in the "error monitoring" page.

    Also, the client computers must have their error reporting settings configured to send error data to SCE server, please check the computer's policy setting under computer configuration\administrative templates\system\error reporting, make sure the setting has been configured properly.

    --------------------
    Regards,
    Eric Zhang



    Thursday, April 3, 2008 8:22 AM
  •  

    Hello,

     

    yes - AEM it's enabled and the Group Policy are correct. Are there any logs where i can look for errors?

     

    Here the gpo settings for the AEM (sorry it's in German)

    The Share SC_ERRORDATA has Share Permission EVERYONE FULL and

    SECURITY Settings for Group AEMAgent (Full Control) and Group AEMUsers (Special Permissions).

     

    Policy Setting Comment
    Fehlerberichterstattung konfigurieren Enabled
    Keine von Microsoft angebotene Websites bezüglich "Weiterer Informationen" anzeigen Disabled
    Keine zusätzlichen Dateien sammeln Disabled
    Keine zusätzlichen Computerdaten sammeln Disabled
    Warteschlangenmodus für Anwendungsfehler erzwingen Disabled
    Dateiuploadpfad für zentrale Fehlerberichte: \\ZM-RIS.genesis.local\SC_ERRORDATA
    Instanzen des Worts "Microsoft" ersetzen durch: ZM-RIS_MG
    Windows-Komponenten/Windows-Fehlerberichterstattung/Erweiterte Einstellungen für Fehlerberichterstattunghide
    Policy Setting Comment
    Betriebssystemfehler melden Enabled
    Standardeinstellungen für Anwendungsberichterstattung Enabled
    Standard: Alle Anwendungsfehler melden
    Alle Fehler in Microsoft-Anwendungen melden Enabled
    Alle Fehler in Windows-Komponenten melden Enabled
    Policy Setting Comment
    Windows-Fehlerberichterstattung im Unternehmen konfigurieren Enabled
    Name des Unternehmensservers: zm-ris.genesis.local
    Verbindung über SSL Enabled
    Serveranschluss: 51906
    Extra Registry Settingshide
    Display names for some settings cannot be found. You might be able to resolve this issue by updating the .ADM files used by Group Policy Management.

    Setting State
    Software\Policies\Microsoft\ErrorReporting\DW\DWAllowHeadless 1
    Software\Policies\Microsoft\ErrorReporting\DW\DWAlwaysReport 1
    Software\Policies\Microsoft\ErrorReporting\DW\DWFileTreeRoot \\ZM-RIS.genesis.local\SC_ERRORDATA
    Software\Policies\Microsoft\ErrorReporting\DW\DWReporteeName ZM-RIS_MG
    Software\Policies\Microsoft\ErrorReporting\DW\DWTracking 1
    Software\Policies\Microsoft\ErrorReporting\DW\ShowUI 0
    Software\Policies\Microsoft\MediaPlayer\Player\ExceptionHandling\DWAllowHeadless 1
    Software\Policies\Microsoft\MediaPlayer\Player\ExceptionHandling\DWAlwaysReport 1
    Software\Policies\Microsoft\MediaPlayer\Player\ExceptionHandling\DWFileTreeRoot \\ZM-RIS.genesis.local\SC_ERRORDATA
    Software\Policies\Microsoft\MediaPlayer\Player\ExceptionHandling\DWReporteeName ZM-RIS_MG
    Software\Policies\Microsoft\MediaPlayer\Player\ExceptionHandling\DWTracking 1
    Software\Policies\Microsoft\MediaPlayer\Player\ExceptionHandling\ShowUI 0
    Software\Policies\Microsoft\Office\10.0\Common\DWAllowHeadless 1
    Software\Policies\Microsoft\Office\10.0\Common\DWAlwaysReport 1
    Software\Policies\Microsoft\Office\10.0\Common\DWFileTreeRoot \\ZM-RIS.genesis.local\SC_ERRORDATA
    Software\Policies\Microsoft\Office\10.0\Common\DWReporteeName ZM-RIS_MG
    Software\Policies\Microsoft\Office\10.0\Common\DWTracking 1
    Software\Policies\Microsoft\Office\10.0\Common\ShowUI 0
    Software\Policies\Microsoft\PCHealth\ErrorReporting\IncludeShutdownErrs 1
    Software\Policies\Microsoft\Windows\Windows Error Reporting\CorporateWERUseAuthentication

     

     

    And here are the Properties from the crash Listener

     

       Crash Listener properties of \\ZM-RIS.genesis.local\SC_ERRORDATA
    Name \\ZM-RIS.genesis.local\SC_ERRORDATA
    Path zm-ris.genesis.local
    AEM Enabled True
    Local File Share Address E:\SC_ERRORDATA\
    Share Path \\ZM-RIS.genesis.local\SC_ERRORDATA
    Protocol https
    Port Number 51906
    Integrated Windows Authentication True
    Error Transmission to Microsoft enabled False
    Detailed Error Transmission to Microsoft enabled False
    Enable Pre-Vista Clients True
    Enable Vista and later clients True
    Organization Name ZM-RIS_MG
    Max # of Cabs to Collect 10
    Error Transmission Filters
    Folder Names
    MS Solution Response Publishing Enabled False
    MS Survey Response Publishing Enabled False
    MS Collection Response Publishing Enabled False
    MS File Collection Response Publishing Enabled False
    MS Registry Collection Response Publishing Enabled False
    MS WMI Query Collection Response Publishing Enabled False
    MS Memory Dump Collection Response Publishing Enabled False
    Default Solution URL
    Display Name

    \\ZM-RIS.genesis.local\SC_ERRORDATA

     

     

    Thursday, April 3, 2008 5:35 PM
  • Hi,


    1.    The AEM file share path should be a local drive to the Management Server and not a UNC (for example: c:\errordata)

    2.    The HttpListener port for AEM (port 51906 by default) is configured with the same SSL certificate that is used for the WSUS website (this is used for Error Reporting data from Vista clients, pre-Vista clients use SMB to copy the error reports to the share).

    So far, let’s check these settings follow the below steps.

     

    1.     Please check whether Domain and Domain Users groups have been given write access to the folder.

     

    2.    Please check the below registry value on client computer.

     

    HKLM\Software\Policies\Microsoft\PCHealth\ErrorReporting\DW\DWReporteeName: It should be \\<SCEServerFQDN>\<Share>

    HKLM\Software\Policies\Microsoft\PCHealth\ErrorReporting\DW\DWReporteeName: Replace instances of the word “Microsoft” with:<Management Group Name>


    --------------------
    Regards,
    Eric Zhang



    Monday, April 7, 2008 8:37 AM
  •  

    Hello Eric,

    thanks for your reply. I checked all your points and it seems that all is correct

     

    the registry key on the client are

     

    HKLM\SOFTWARE\Policies\Microsoft\PCHealth\ErrorReporting\DW\DWFileTreeRoot:  \\zm-ris.genesis.local\sc_errordata

     

    HKLM\SOFTWARE\Policies\Microsoft\PCHealth\ErrorReporting\DW\DWReporteename: ZM-RIS_MG

     

    Following Groups have write access to the sc_errorfolder

     

    AEMAgent FullControl

    AEMUsers Special Permissions as follows

    Traverse Folder / Execute Folder

    Read Attribute

    Read Extended Attributes

     

    The AEMAgent Group contains the group BUILTIN\Administrator

    The AEMUsers Group contains NT Authority\Authenticated Users

     

    Olaf

     

     

     

     

     

    Wednesday, April 9, 2008 4:25 PM
  • Hi Olaf,

    Try to modify the sharing and security of the sc_error folder, add everyone and give it the modify access, then check whether the problem will be resolved.

    --------------------
    Regards,
    Eric Zhang



    Thursday, April 10, 2008 7:19 AM
  •  

    Hi Eric,

     

    modified the sharing and security to everyone/full access and still no luck. The Network Monitor shows some

    sort of Communication between the Client and the Server with destination Port 51906. If you want i could send you the data.

     

     

    Bye

     

    Olaf

     

     

     

    Saturday, April 12, 2008 6:06 PM
  • Hi Olaf,

    Is there any firewall installed on the server or client?

    If it is, please modify the policy and open the 51906 port.

    --------------------
    Regards,
    Eric Zhang



    Wednesday, April 16, 2008 9:42 AM
  • No Firewall on the Server or the Client. I can see that the Client is accessing the Share.

     

    Object Open:
      Object Server: Security
      Object Type: File
      Object Name: E:\SC_ERRORDATA
      Handle ID: 10700
      Operation ID: {0,67482029}
      Process ID: 4
      Image File Name: 
      Primary User Name: ZM-RIS$
      Primary Domain: GENESIS
      Primary Logon ID: (0x0,0x3E7)
      Client User Name: genesis_admin
      Client Domain: GENESIS
      Client Logon ID: (0x0,0x13395)
      Accesses: ReadAttributes
       
      Privileges: -
      Restricted Sid Count: 0
      Access Mask: 0x80

     

    Handle Closed:
      Object Server: Security
      Handle ID: 10700
      Process ID: 4
      Image File Name: 

     

    Object Open:
      Object Server: Security
      Object Type: File
      Object Name: E:\SC_ERRORDATA\Counts
      Handle ID: 10700
      Operation ID: {0,67482040}
      Process ID: 4
      Image File Name: 
      Primary User Name: ZM-RIS$
      Primary Domain: GENESIS
      Primary Logon ID: (0x0,0x3E7)
      Client User Name: genesis_admin
      Client Domain: GENESIS
      Client Logon ID: (0x0,0x13395)
      Accesses: ReadAttributes
       
      Privileges: -
      Restricted Sid Count: 0
      Access Mask: 0x80

    Handle Closed:
      Object Server: Security
      Handle ID: 10700
      Process ID: 4
      Image File Name: 

     

     

     

     

     Eric Zhang - MSFT wrote:
    Hi Olaf,

    Is there any firewall installed on the server or client?

    If it is, please modify the policy and open the 51906 port.

    --------------------
    Regards,
    Eric Zhang



    Friday, April 18, 2008 12:21 PM
  • Hi Olaf,

    Is there any error in the Event Viewer on SCE server?

    Also, please open SCE console, navigate to "Monitoring" space, choose "Agentless Exception Monitoring", choose “crash listener view" and "application view" to check whether there is any information

    --------------------
    Regards,
    Eric Zhang



    Monday, April 21, 2008 8:40 AM
  • Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks!
    --------------------
    Regards,
    Eric Zhang

    Monday, April 28, 2008 6:42 AM
  •  

    Hello Eric,

     

    sorry... it's still not working...

    I have checked all points that you have mentioned, but no success.

    Next Week i will  build a new testlab with the Server and a few clients, maybe it works this time..

     

    I keep you informed.

     

    Bye

     

    Olaf

     

    Tuesday, April 29, 2008 1:26 PM
  • Hi Olaf,

    OK, If you still have any problems after building the new systm, please feel free to let me know.

    --------------------
    Regards,
    Eric Zhang



    Wednesday, April 30, 2008 6:03 AM