Windows Server

JB · Guest

OK, I give. From what I can tell my MOM 2005 server (that I inherited)
had at one time been named xyzN but is now just named xyz. I do NOT
think it was renamed after MOM was initially installed but I'm not 100
% sure.

Anyway, whenever discovery is performed it comes up with the following
error:

Computer Discovery Engine failed to contact machine "xyzN.lab.com".
This could be a misspelled computer name or the computer is not
contactable.

Error Message:
"Could not resolve machine to an IP Address. Error during DNS Lookup:
The requested name is valid, but no data of the requested type was
found"

I CAN'T FIGURE OUT WHERE IT IS GETTING THIS NAME!

Places I have searched are:

DNS, WINS, AD, registry, did a findstr /i xyzN on all files on the C:
Drive and found the name is a log file that was created during initial
OS install (that's what gave me the clue as to it being a different
name earlier in its life), and I even dumped the entire contents of the
onepoint db and searched for the bad name but all searches have been in
vain!

Where the hell is it getting this bogus/old name from? I notice under
the Computer Discover Rules that it has one default rule for this
server (with the correct name) but I can't edit this rule or delete it.
Does anyone know how I can fix this problem? Is there some binary
file that needs to be hacked or is there a way short of wiping the
entire MOM server and starting over again?

TIA.

JB

JB · Guest

Sorry, I should add that for the most part my MOM seems to be working
OK. This particular event/error is the only one that comes up with a
reference to this bogus/bad server name.

JB

Rory · Guest

To see if the computer is in your onepoint db, open SQL Query Analyzer and
run the following query

SELECT Domain, Name, DNSName, IsAgent
FROM Computer
WHERE Name = 'xyzN'

Another place to look for this computer is in a text file known as
ManualMC.txt. Do a search for this file in your MOM 2005 installation
directory. If it's there, delete the entry for the old server name. If it's
not there, look in your Managed computer rules and ensure that server isn't
listed there.

Rory

"JB" <jbyy4u@yahoo.com> wrote in message
news:1104268039.040642.151250@f14g2000cwb.googlegroups.com...

JB · Guest

Thanks Rory. As I mentioned I already dumped the database and searched
it as well as searched for the string within all files on hard drives
but all with no luck. FYI - I did run the query you provided but it
came up blank.

If there is a rule that has this invalid host I'm not sure where to
find it. I have only the default MP installed right now. I've cleared
out all of my discovery rules but like I mentioned above there is that
one default rule (which DOES show the correct name) that seems to be
read only and that I CANNOT delete.

Any other suggestions?

Thanks.

BJ

Darrell · Guest

Hi,

I am getting the same error on my MOM server. I too have search the database
but cannot find the computer name anywhere. I do not have a discovery rule
for that computer name.

I upgraded this server from MOM 2000 to 2005 and it seems to be a leftover
from the old installation.

"JB" wrote:

JB · Guest

Well, if I don't get this figured out soon I'm going to have to wipe
and re-install. I've actually made things worse now. What I did was I
added this bogus machine name as an alias to the real name in the local
hosts file on the Mgmt Server. This got rid of the initial error from
the Computer Discovery Script but then I started getting all kinds of
other errors again referring to this bogus name...so I removed the
alias from my hosts file and rebooted but am still getting lots of
errors all referring to this bogus name!!!

JB

	Windows Server Forum Index -> MOM	All times are GMT
Page 1 of 1