Answered by:
Operations Manager 2007 R2: Discovery Wizard fails during RHEL 5.1 machine discovery

Question
-
Here's what I get when trying to discover Red Hat 5.1 machine:
Date: 5/25/2010 10:11:15 AM
Application: System Center Operations Manager 2007 R2
Application Version: 6.1.7221.0
Severity: Error
Message:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SystemCenter.CrossPlatform.UI.Administration.DiscoveryTaskHelper.<>c__DisplayClass4.<GetAvailableUnixAgents>b__3(Object , ConsoleJobEventArgs )
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)This error is consistent and occurs after several minutes of running the Discovery Wizard in Operations Console.
Linux machine name is present in the DNS server and is both forward and reverse resolvable.
Version of Cross Platform installed is 6.1.7000.273.
- Moved by WadeWe Wednesday, October 26, 2011 9:01 PM New forum (From:Cross Platform Solutions for System Center)
Tuesday, May 25, 2010 7:44 PM
Answers
-
This is why you should use DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx) to watch what is goin on during the wizard process. Download DebugView, run it, then go through the discovery wizard and watch the output in the DebugView console. You will see a lot more information.
Robert Hearn • Sr. Program Manager
Customer & Partner Community
System Center Cross Platform & Interop
Read the Cross Platform & Interop team blog | Become a Fan on Facebook | Follow us on Twitter | Read my blog
- Marked as answer by Matthias ArenskoetterMicrosoft employee Sunday, June 13, 2010 9:04 AM
Thursday, June 3, 2010 8:54 PM
All replies
-
The initial Agent deployment is done through SSH/SFTP. These components rely on a separate logging mechanism than OpsMgr.
To enable this logging, you create a blank file named EnableOpsmgrModuleLogging in the Temp directory of the Management Server
you chose for discovering your Red Had Server
An easy command line to generate this file is:
COPY /Y NUL %windir%\TEMP\EnableOpsMgrModuleLogging
For reference, see the following article:
http://technet.microsoft.com/en-us/library/ee344801.aspx
After you have done that, start your discovery again and take a look at the Logfiles for more informations.
- Marked as answer by Matthias ArenskoetterMicrosoft employee Thursday, May 27, 2010 2:29 PM
- Unmarked as answer by Matthias ArenskoetterMicrosoft employee Wednesday, June 2, 2010 2:45 PM
Wednesday, May 26, 2010 7:15 AM -
A couple of other suggestions...
One..use DebugView to watch the debug output of the discovery as it happens.
Two, make sure your MPs are installed correctly, at the latest version, and that you also installed the latest version of the agents. The "null reference" might be that the Red Hat MP is looking for a version of the agent that has not been installed.
Get the latest agent here: System Center Operations Manager 2007 R2 Cross Platform Cumulative Update 2 (KB979490)
Robert Hearn • Sr. Program Manager
Customer & Partner Community
System Center Cross Platform & Interop
Read the Cross Platform & Interop team blog | Become a Fan on Facebook | Follow us on Twitter | Read my blog
- Proposed as answer by Robert_Hearn Wednesday, May 26, 2010 5:06 PM
Wednesday, May 26, 2010 5:06 PM -
Actually, it does not look like it even reaches the stage of SSH/FTP.
After I created the file EnableOpsMgrModuleLogging and restarted the machine, all went exactly as before and no logfiles were created in %windir%\TEMP
Tuesday, June 1, 2010 8:38 PM -
I already have all the updates installed, including KB979490. The problem is that it fails somewhere much earlier than any actual contact with the Linux box happens.Tuesday, June 1, 2010 8:39 PM
-
Oleg, can you repro this issue on another System where the Operational Console is installed?
- Marked as answer by Matthias ArenskoetterMicrosoft employee Sunday, June 13, 2010 9:04 AM
- Unmarked as answer by Matthias ArenskoetterMicrosoft employee Sunday, June 13, 2010 9:04 AM
Wednesday, June 2, 2010 2:44 PM -
This is why you should use DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx) to watch what is goin on during the wizard process. Download DebugView, run it, then go through the discovery wizard and watch the output in the DebugView console. You will see a lot more information.
Robert Hearn • Sr. Program Manager
Customer & Partner Community
System Center Cross Platform & Interop
Read the Cross Platform & Interop team blog | Become a Fan on Facebook | Follow us on Twitter | Read my blog
- Marked as answer by Matthias ArenskoetterMicrosoft employee Sunday, June 13, 2010 9:04 AM
Thursday, June 3, 2010 8:54 PM -
Me too also have same issue.Any one have the solution?ThanksTuesday, July 13, 2010 4:01 PM