none
EBS 2008 SCE 2007 Tasks Queued EBS servers no longer reporting

    Pregunta

  • This all started when I put a new pc on the network. The discovery wizard ran and everything was good till I changed the pc's name. It then went from monitored to unmonitored and moved it out of the group. Trying to get it back in I followed a technet article about running a sql script that discovers old pc name in sql that's no longer listed in sce. The script ran and didn't find anything. The next bit was delete the healt state manually. I did that and no pc's could connect anymore. I stopped the services and put the old folder back. All pc's started reporting back in, new pc was still not showing as client and listed as unmonitored. After deleting the health state the servers stopped reporting after restoring folder they continued to fail reporting in EBS console. The 3 servers event logs for operational management show they are reporting and updates are discovered and installed. I've reentered the SCE run as account info. 

    Tasks are queued up, I ran a sql script to show the queud tasks but none are displayed.My morning reporting e-mail is also not being sent.

    I've combed through dozens of technet articles and blogs here but everything I try leads no where. If in SQL it says everything is fine while the front side says error or just queus tasks.

    Because this is EBS I have 28days to resolve before the servers shut down.

    viernes, 10 de febrero de 2012 15:40

Respuestas

Todas las respuestas

  • I restored an old health state and it sort of fixed 2 of the 3 ebs servers. checking the mgt server event log was seeing event id 29106 SizeNumeric found article http://support.microsoft.com/kb/2017680 errors traced back to when i installed new 08 management pack removed the new ones since i couldn't figure out which was the old ones. errors stopped and servers connected.

    Still can't get our new windows 7 pc to show up in managed group though. Still shows unmonitored. And my task queue is still backed up.

    After writing this reply my tasks that were queued all went to failed and new tasks are processing.

    Just have to figure out the windows 7 pc.

    • Editado hutchnate viernes, 10 de febrero de 2012 18:09
    viernes, 10 de febrero de 2012 18:04
  • Hello,

    Just for your information, the following article discussed a similar issue for SCE 2007 SP1:

    EBS, SCE, Windows Server 2008 R2 and Windows 7
    http://blogs.technet.com/essentialbusinessserver/archive/2009/10/30/ebs-sce-windows-server-2008-r2-and-windows-7.aspx

    Thanks,


    Yog Li

    TechNet Community Support

    lunes, 13 de febrero de 2012 11:23
  • Thanks for the link I already followed that. win7x64 was reporting prior to me changing the pc's name. Once i changed the name the server no longer allows it to connect. Server shows event id 20000, A device which is not part of this management group has attempted to access this Health Service.
    The win 7client shows event id 20070. The OpsMgr Connector connected to (server name here), but the connection was closed immediately after authentication occured.  The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration.

    I've manually installed the agent and it shows the correct management group. I followed some technet help on checking sql when after name change old name stays in sql. It returned with nothing.

    lunes, 13 de febrero de 2012 17:47
  • Hello,

    Did you see an entry of the agent with the old computer name on SCE console? If yes, you have to manually remove the old name from SCE console. 

    To remove it, go to the Administration pane, highlight "Agent Managed", find the pc in the list, right-click and select delete.

    Then manually run a discovery and it should find the new pc.  The agent is already installed, so it will start reporting.  If it's not working properly, you can try running a repair on the agent once it shows up in the administration pane.

    The new computer name will need to be in the SCE Managed Computers group so it will recieve the correct group policy. 

    Thanks,


    Yog Li

    TechNet Community Support

    martes, 14 de febrero de 2012 8:40
  • Yog,

    Thanks for the tips but I already know that and already did all that. It does show up in admin pane, it's greyed out. If I delete or repair & discovery/manual install it adds it to the SCE managed group. If i look at the agent config file it shows it's part of the correct group. Which isn't hard since I only have 1 group. It shows up the managed computer group with monitor error and message this computer hasn't checked in yet. Becuase the server keeps rejecting it's communication.

     Server shows event id 20000, A device which is not part of this management group has attempted to access this Health Service.
    The win 7client shows event id 20070. The OpsMgr Connector connected to (server name here), but the connection was closed immediately after authentication occured.  The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration.

    martes, 14 de febrero de 2012 15:13
  • Hello,

     

    Event ID 20000 and 20070 both indicate that this is a certification problem. A lot of factors can cause this. For your reference, the following threads disscussed a similar issue:

     

    SCROM (SCE server) - ERRORS 20070 and 21016?
    http://social.technet.microsoft.com/Forums/en-US/systemcenterrom/thread/a0783858-a0fe-4d6f-ab80-b0de9065951e/

    New agents not working Events 20000, 21016, 20070, etc
    http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/02d63acd-edc3-4ab1-b722-37c1261313fe

    OpsMgr 2007: Port requirements for SCOM agents in a DMZ
    http://blogs.technet.com/b/operationsmgr/archive/2009/02/17/opsmgr-2007-port-requirements-for-scom-agents-in-a-dmz.aspx

    OpsMgr 2007: Agents in remote domain are unable to communicate with the Management server
    http://blogs.technet.com/b/smsandmom/archive/2008/11/07/configmgr-2007-agents-in-remote-domain-are-unable-to-communicate-with-the-management-server.aspx

     

    Thanks,


    Yog Li

    TechNet Community Support

    • Marcado como respuesta Yog LiModerator miércoles, 22 de febrero de 2012 7:06
    viernes, 17 de febrero de 2012 10:19
  • Hello,

    Is there any further information on this issue? We’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks,


    Yog Li

    TechNet Community Support

    martes, 21 de febrero de 2012 2:57