Modul ErrorManagerPA

All Replies

• Thursday, November 22, 2007 7:16 AM

   

   
  

  0

  Sign In to Vote

  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>

   

  Then, we’d recommend you to re-run “Product Feature Configure” wizard.

   

  If the problem still persist, then please follow the below steps to collect information for further troubleshooting.

   

  1.    Please download the MPSRPT_SetupPerf.exe and run on the client to collect more information for further troubleshooting.

  http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_SetupPerf.exe

  2.    Send the cab file which MPSRPT_SetupPerf.exe given to scedata@microsoft.com.

   

  More information

  818742.KB.EN-US Overview of the Microsoft Configuration Capture Utility (MPS_REPORTS)

  http://support.microsoft.com/default.aspx?scid=KB;EN-US;818742

   

   

  Note:

   

  Please include the following three lines in the email body:

   

  Modul ErrorManagerPA

  http://forums.microsoft.com/TechNet/ShowPost.aspx?postid=2433630&siteid=17

  Xiu Zhang- MSFT

   

  Regarding more information about how to send email to SCEDATA@microsoft.com, please refer to:

   

  How to send files to the Microsoft SCE team for review

  http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1680389&SiteID=17

   

  Post a quick note in the current thread after sending the email.

   

  Thanks!

   

  Best regards,

  Xiu Zhang - MSFT

  Microsoft Online Community Support

  • Reply
  • Quote

   
• Sunday, November 25, 2007 4:10 PM

   

   
  

  0

  Sign In to Vote

  Hello Xiu Zhang,

   

  Thank you for your answer. Until now I wasn't able to reach the test environment, therefore I wasn't able to check all content.

   

  to 2: I found in registry: \\bs-data01.BlackSeals.lan\Anwendungsfehler. I think that is OK. If I want to open it with my domainuser, I get an access error. I will look as fast as possible for the access permission.

   

  Maybe there is a wrong setting. How should the folder permission and the publishing permission look like?

   

  I will also try the Product Configuration Wizard. Are there any disadvantage if I run the wizard again?

  • Reply
  • Quote

   
• Monday, November 26, 2007 7:11 AM

   

   
  

  0

  Sign In to Vote
  Hi,

   

  Permission for Anwendungsfehler foler should like below:

   

  Share Permissions:

  Everyone-Full control

   

  Security Tab:

  Administators (domain\Administrators) -Full control 

  AEMAgent (Domain\AEMAgent) -Full control

  AEMUsers(Domain\AEMUsers) - special permission

   

   

  To find these, you can follow the below steps:

  1. You can find your Anwendungsfehler foler and right click on it.

  2. Select to properties,then change to Sharing tab.

  3. Ensure that "Share this folder" has been ticked.

  4. Click on "Permissions" button to check the Share Permissions.

  5. Then change to Security Tab to check the settings on it.

   

  We recommend you to new the share foler when you re-run the Feature Configure Wizard.

   

  Hope it helps!
  • Reply
  • Quote

   
• Monday, November 26, 2007 7:22 AM

   

   
  

  0

  Sign In to Vote
  Hi,

   

  You also can run the blow command to   Configure Application Error Monitoring, using the C:\ErrorData directory as the upload location and port 51906.

   

  SCECertPolicyConfigUtil.exe /ManagementGroup SCEServer_MG /PolicyType Domain /SCEServer [SCEServerFQDN]/AEMFileShare c:\ErrorData /AEMPort 51906 /ConfigureAEM true /ConfigureFirewallPolicy true /ConfigureRemoteControl true

  Hope it helps

   
  • Reply
  • Quote

   
• Thursday, November 29, 2007 3:52 AM

   

   
  

  0

  Sign In to Vote
   

  Any feedback will be appreciate to us!

   

  Please feel free to post here if you get any update.

  • Reply
  • Quote

   
• Thursday, November 29, 2007 7:55 AM

   

   
  

  0

  Sign In to Vote
  Hello Xiu Zhang,
  
  

  Xiu Zhang - MSFT wrote:

  Any feedback will be appreciate to us!   Please feel free to post here if you get any update.

  
  
  Sorry, but there was less time.
  
  
  

  Xiu Zhang - MSFT wrote:

  Hi,   Permission for Anwendungsfehler foler should like below:   Share Permissions: Everyone-Full control   Security Tab: Administators (domain\Administrators) -Full control  AEMAgent (Domain\AEMAgent) -Full control AEMUsers(Domain\AEMUsers) - special permission     To find these, you can follow the below steps: 1. You can find your Anwendungsfehler foler and right click on it. 2. Select to properties,then change to Sharing tab. 3. Ensure that "Share this folder" has been ticked. 4. Click on "Permissions" button to check the Share Permissions. 5. Then change to Security Tab to check the settings on it.

  
  
  I checked it and it seems to me that the permission of that folder is correct. On the server, the folder exists on "D:\SCE\Anwendungsfehler".
  
  I found unexpected a permission failure in the Sysvol folder. The GPO for SCE had different permission between Sysvol and Active Directory. At the moment I used the Active Directory permission for the Sysvol folder. Maybe that was the reason for the "Modul ErrorManagerPA" error? I will wait for some days, if it occour again. Then I will try the Feature Configuration Wizard. After that all you will get a status update.
  
  Is there any report view in the SCE Console for Application folder? I want to check if the SCE Server will get the error reports from the clients and if it will send it to Microsoft.
  
  • Reply
  • Quote

   
• Thursday, November 29, 2007 8:42 AM

   

   
  

  0

  Sign In to Vote
  Hi,
  
  I already used the "Product Feature Configuration" wizard. Maybe I found there the reason? We have here an ISA 2006 Server. Therefore I used the proxy server configuration with user and password setting. There I'm able to choose between http and https. I used there the https setting.
  
  According to the following error message:
  

  >>>
  Ereignistyp: Fehler
  Ereignisquelle: Health Service Modules
  Ereigniskategorie: Keine
  Ereigniskennung: 10907
  Datum:  19.11.2007
  Zeit:  23:33:33
  Benutzer:  Nicht zutreffend
  Computer: BS-DATA01
  Beschreibung:
  Ein Modul 'ErrorManagerPA' konnte das neues Datenelement nicht verarbeiten. ServicePointManager unterstützt keine Proxys mit dem https-Schema.

  Mindestens ein Workflow ist hiervon betroffen. 

  Workflowname: Microsoft.SystemCenter.CM.AEM.Internal.MEWriterToDataWarehouse
  Instanzname: \\bs-data01.BlackSeals.lan\Anwendungsfehler
  Instanz-ID: {83855ED8-7A61-6595-890D-D2E0D79247DF}
  Verwaltungsgruppe: BS-DATA01_MG

  Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
  <<<

  it seems to me I should change the settings from https to http proxy server. In the above error message does the "ServicePointManager" indicate, that it doesn't support proxys with https.
  
   So I changed it now. I will to a status update as soon as possible.
   Maybe you are able to give me an answer to the last questions from my last entry.
  
  • Reply
  • Quote

   
• Thursday, November 29, 2007 9:09 AM

   

   
  

  0

  Sign In to Vote
  Hi,

  Thanks for your time and effort!

   

  Meanwhile,the below post discussed a lot on ISA settings with SCE box.

  http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2003186&SiteID=17

   

   

  Hope it helps.
  • Reply
  • Quote

   
• Monday, December 03, 2007 6:53 AM

   

   
  

  0

  Sign In to Vote

  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!

  • Reply
  • Quote

   
• Wednesday, December 05, 2007 8:40 AM

   

   
  

  0

  Sign In to Vote

  Xiu Zhang - MSFT wrote:

  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.

  
  
  It isn't resolved. As I wrote, I looked for warnings and errors in the event viewer for some days. Additional there wasn't everey day time for the test environment.
  
  Ok, what happens:
  
  After I changed the proxy from https to http, I get an error message from the same source. The content: it will not support the proxy authentification.
  Therefore I changed the setting in the SCE Console to use no proxy authentification and also I turned it off in the ISA Console (only for the SCE Server).
  
  Now I have no error message, but I get a warning in the SCE Console every day.
  
  >>>AEM Module Network Error:
  Netzwerkkommunikationsfehler 'Die zugrunde liegende Verbindung wurde geschlossen: Unbekannter Fehler beim Empfangen..' mit dem Fehlercode 'ReceiveFailure' im Error Manager-Modul. Workflowname: Microsoft.SystemCenter.CM.AEM.Internal.MEWritertoDataWarehouse Instanzname: \\bs-data01.BlackSeals.lan\Anwendungsfehler Instanz-ID: {83855ED8--7A61-6595-890D-D2E0D79247DF} Verwaltungsgruppe: BS-DATA01_MG
  <<<
  
  
  Also there is a new error. I don't think, that there is a relation with the above error. After using the product configuration wizard I get every day the error, that the push/repair of a agent client failed. In the test environment, there is no new client. If I check which agent client failed, I get the name of the SCE Management Server.
  
  However, I will use MPSRPT_SetupPerf.exe and the above instruction to send you an email.
  
  [edit]I sent out the email with the attachement (one cab file from the MPSRPT_SetupPerf.exe Tool) to you.[/edit]
  
  • Reply
  • Quote

   
• Thursday, December 06, 2007 8:15 AM

   

   
  

  0

  Sign In to Vote
  Hi,

   

  Since event 10907 has disappeared in the event log ,we assume that ISA setting should be the sticking point.So we recommend you to follow the below article to configure ISA Server,,it is really useful to you though it is for ISA Server 2004 Firewall on SBS.

   

  How to Configure an ISA Server 2004 Firewall on Small Business Server for System Center Essentials

  http://technet.microsoft.com/en-us/library/bb422892.aspx

   

  Besides,we find a lot other errors in the event log, we'd recommend that you start up a new thread for it. We generally focus on one topic in one thread because in this way it will be better for other community members to participate in the discussion, and to search/find specific answers more efficiently in the future.

   

  Meanwhile,I think after correcting ISA settings,the main problem should be solved.please follow the below steps to re-install agent on client computers.

   

  1.Delete the agent from SCE console.(Administration-Agent Managed)

   

  2.Uninstall feature configuration.

  1).Open a command prompt and type "cmd".

  2).Type"SCECertPolicyConfigUtil.exe /Uninstall /ManagementGroup [SCEServer_MG]"

   

  Note:If it failed,then it indicates that the feature configuration is not normal.

   

  3.Please re-run "Product Feature Configure"Wizard.

  Notelease specify the AEM like "c:\Errordata."Do not use the former one.

   

  4.Run "gpupdat /force" on both SCE Server and client computer.

   

  5.Wait for about 5 minutes and then push agent to client computer.

   

  6. On a client, stop the Automatic Update service via services.msc.

   

  7. Rename the windowsupdate.log (under %windir%) to windowsupdate1.log, and then start the Automatic Update service.

   

  8. Run “wuauclt /detectnow” command.

   

  9. Wait for 10 minutes and then run “wuauclt /reportnow” command.

   

  10. We will get a new %windir%\windowsupdate.log file.

   

  Hope it helps.

   
  • Reply
  • Quote

   
• Thursday, December 06, 2007 8:19 AM

   

   
  

  0

  Sign In to Vote
  Meanwhile,I'd like to share some inforamtion on install angent on ISA 2006

   

  Agent fails to install on ISA 2006 Std

  http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2378309&SiteID=17&pageid=0

   

  Internet Security and Acceleration (ISA) Server TechCenter

  http://www.microsoft.com/technet/isa/default.mspx 

   

  Hope it helps.
  • Reply
  • Quote

   
• Tuesday, December 11, 2007 4:38 PM

   

   
  

  0

  Sign In to Vote
  Sorry, there was no time to trie the above extensive procedure. There was some work with the "real" Exchange Server 2007.
  
  After I was able to spend time on the test environment, you will get immediately an information.
  • Reply
  • Quote

   
• Thursday, June 12, 2008 9:50 AM

   

   
  

  0

  Sign In to Vote
  Hello Xiu Zhang,
  
  There was a lot of time between my last message. I was some traveling, had a lot of other work and there was a change to the testing environment.
  
  

  Xiu Zhang wrote:

  How to Configure an ISA Server 2004 Firewall on Small Business Server for System Center Essentials http://technet.microsoft.com/en-us/library/bb422892.aspx

  
  It seems to me, that the ISA 2006 Firewall has now the correct settings.
  
  
  

  Xiu Zhang wrote:

  1.Delete the agent from SCE console.(Administration-Agent Managed)   2.Uninstall feature configuration. 1).Open a command prompt and type "cmd". 2).Type"SCECertPolicyConfigUtil.exe /Uninstall /ManagementGroup [SCEServer_MG]"   Note:If it failed,then it indicates that the feature configuration is not normal.   3.Please re-run "Product Feature Configure"Wizard. Notelease specify the AEM like "c:\Errordata."Do not use the former one.   4.Run "gpupdat /force" on both SCE Server and client computer.   5.Wait for about 5 minutes and then push agent to client computer.   6. On a client, stop the Automatic Update service via services.msc.   7. Rename the windowsupdate.log (under %windir%) to windowsupdate1.log, and then start the Automatic Update service.   8. Run “wuauclt /detectnow” command.   9. Wait for 10 minutes and then run “wuauclt /reportnow” command.   10. We will get a new %windir%\windowsupdate.log file.

  
  
  Until now I didn't tried it. The AEM folder is still on "D:\". The Update procedure works without big problems. The same apply to created Software packages by myself.
  
  
  However there was a change to the testing environment. Now SCE has a little more RAM, a second CPU and of course a faster harddisc. Therefore the SCE runs much more "smoother". Also the SP1 installation helped something, but there are also some new (other) problems.
  
  It seems to me that the above problems are solved. For the new one I will create a new thread.
  
  • Reply
  • Quote