AD Topology Discovery script

Discussion:

(too old to reply)

Kevin Beares [MSFT]

2005-03-02 17:44:38 UTC

Hi Lain,

I believe this article should help you solve the problem with the timeout
errors. I also included another article that explains what this script is
trying to do and why. The first article should also answer your question on
how you can gain access to where the script is being run from. I hope this
helps.
--
Thanks,

Kevin Beares
MOM Community PM
--
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"

TITLE: MOM 2005: Errors with the "AD Topology Discovery" script
[ ]
**Problem** BETA - MOM Operations Mgr 2004 [2004 -W_6620 ]
ID: SOX040702700041 CRT: Jul 2 2004 MOD: Jul 2 2004 STS:Customer
Verified

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Problem Description ***
Receiving following alert from management server every 30 minutes from
management
server:

Severity: Error
Maintenance Mode: False
Domain: TEKNOLOJI
Computer: TEKMOM11
Time Last Modified: 6/11/2004 11:30:08 AM
Resolution State: New
Time in State: 6/10/2004 2:00:04 PM
Problem State: 0
Repeat Count: 33
Name: A script hung or exceeded its specified timeout
Source: Microsoft Operations Manager
Ticket Id:
Owner:
Description: The response 'script: AD Topology Discovery' has been running
more
than 300 seconds and exceeded the time allowed to run. This might indicate
the
response is engaged in an infinite loop or is hanging.
The response is running on thread '2824' in the process MOMHost.exe with
process id
'2668'.
Management Group: GTMOM
Time of Last Event: 6/11/2004 11:30:00 AM
Time Raised: 6/10/2004 5:00:04 PM
Alert Id: d60cd07d-1778-4bb0-af08-e75e35b67a84
Rule Id: 4c3815bb-e092-4cd9-9528-d662c458e081
Rule Name: A script hung or exceeded its specified timeout
CustomField1:
CustomField2:
CustomField3:
CustomField4:
CustomField5:
Time Added: 6/10/2004 5:00:04 PM
Time of First Event: 6/10/2004 5:00:00 PM
Time Resolved:
Resolved By:
Modified By: NT AUTHORITY\NETWORK SERVICE
Computer Custom Data 1:
Computer Custom Data 2:
Maintenance Mode End:
Maintenance Mode User:
Maintenance Mode Reason:

I checked the event log of the management server:

First receiving following error:

The response 'script: AD Topology Discovery' has been running more than 300
seconds
and exceeded the time allowed to run. This might indicate the response is
engaged
in an infinite loop or is hanging.
The response is running on thread '724' in the process MOMHost.exe with
process id
'2364'.
Management Group: GTMOM

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

and then

The host process for script responses will be restarted to recover from
responses
that might have been engaged in an infinite loop or hanging.
Management Group: GTMOM

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

finally

The response processor failed to execute a response. The response returned
the
error message: The remote procedure call failed.

Response Details:

Rule ID: {250F4C13-E035-43C5-961D-1424D934699F}
Response description: script: AD Topology Discovery

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Resolution *** Jul 2 2004 10:31AM vreavis

In environments where there is a large AD infrastructure or a lot of DCs,
this
script may not complete in a timely manner. Check the Script frequency
setting in the rule.

Right click on Rule Groups in the Admin Console and search for all rules
that run
the script AD Topology Discovery. Open the rule properties and under the
DataProvider tab, you can notice the "Provider name" indicates that it is
scheduled for every 30 minutes. Choose the Modify button and raised it to
90
minutes and the problem went away.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

TITLE: MOM://AD Topology Discovery script logs "Topology Discovery did not
fully discover topology"
[ ]
**Problem** Windows Server 2003 Enterprise [2003 -W_5826 ]
ID: SOX050113700006 CRT: Jan 13 2005 MOD: Jan 13 2005 STS:Customer
Verified

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Problem Description ***
Symptoms:
=========
- Roughly every 30 minutes, DCs with MOM agents installed may report an
alert
from the AD Topology Discovery script
- It states "Description: Failed to get the flat names for the computer
'<name
of other DC>'"
- Also "The error returned was: 'Permission denied' (0x46)"

Cause:
======
- This is caused by an RPC authentication failure which was caused by
mismatched
SMB signing policy settings in my customer's environment

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Resolution *** Jan 13 2005 7:07AM keiththo

Resolution:
=========
- This problem can be fixed by correcting the SMB Signing policies to
either
consistently allow or not require signing between servers

More Information:
==============
- This was verified by running the following three lines as a VB script
which
returned error 0x80040046

Set oOOMADs = CreateObject("McActiveDir.ActiveDirectory")
strFlatDomainName = oOOMADs.GetFlatDomainForDC("dc5cd.dept.clinlan.local")
WScript.Echo err.number

- The script above will display a prompt with the return code of call
GetFlatDomainForDC() -> 0 is success, etc
- It should first be run while logged on as a user with Admin rights ->
if the
return code is 0 then run it as the MOM Action Account
- GetFlatDomainForDC() is a function exported by OOMADS.dll, part of the
Active
Directory Management Pack Helper Objects
- The function simply makes a remote RPC call to run DsGetDcName() on
the DC
listed as the first and only parameter
- Note that the original error in this case was 0x800401CE -> the error
changed
after applying the Q889054 ReplProv hotfix

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

Hi guys
I'm having a recurrent issue after the installation of MOM 2005 with the
The reponse 'script: AD Topology Discovery' has been running more than
1800
seconds and exceeded the time allowed to run. This might indicate the
response is engaged in an infinite loop or hanging.
I've tried finding where this automated task is coming from, as it's not
listed in the Tasks | Microsoft Active Directory area. I'm tempted to
rename
the actual script in order to stop this from being an issue, but I'd
actually
like to know
1) Why is it trying to automatically map the entire connected environment?
As in, what does it gain from doing so? Why isn't it just just discovering
our domain namespace and connectivity, if anything must be discovered at
all?,
2) To what degree it's trying to contact top-level forest infrastructure,
and
3) How can I disable this functionality without resorting to "breaking"
that
script?
Cheers
Lain
Siemens Australia

FranckCF

2005-06-14 11:03:11 UTC

Permalink

Hi,

I have always the same error :
id 21421 : the script is running more 1800 ....
id 21423 : the component host process for script will restart ....to recover
answer in loop state
id 21245 : the answer process has not succeed to execute answer.error rpc.

Thanks for your answers

Post by Kevin Beares [MSFT]
Hi Lain,
I believe this article should help you solve the problem with the timeout
errors. I also included another article that explains what this script is
trying to do and why. The first article should also answer your question on
how you can gain access to where the script is being run from. I hope this
helps.
--
Thanks,
Kevin Beares
MOM Community PM
--
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
TITLE: MOM 2005: Errors with the "AD Topology Discovery" script
[ ]
**Problem** BETA - MOM Operations Mgr 2004 [2004 -W_6620 ]
ID: SOX040702700041 CRT: Jul 2 2004 MOD: Jul 2 2004 STS:Customer
Verified
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Problem Description ***
Receiving following alert from management server every 30 minutes from
management
Severity: Error
Maintenance Mode: False
Domain: TEKNOLOJI
Computer: TEKMOM11
Time Last Modified: 6/11/2004 11:30:08 AM
Resolution State: New
Time in State: 6/10/2004 2:00:04 PM
Problem State: 0
Repeat Count: 33
Name: A script hung or exceeded its specified timeout
Source: Microsoft Operations Manager
Description: The response 'script: AD Topology Discovery' has been running
more
than 300 seconds and exceeded the time allowed to run. This might indicate
the
response is engaged in an infinite loop or is hanging.
The response is running on thread '2824' in the process MOMHost.exe with
process id
'2668'.
Management Group: GTMOM
Time of Last Event: 6/11/2004 11:30:00 AM
Time Raised: 6/10/2004 5:00:04 PM
Alert Id: d60cd07d-1778-4bb0-af08-e75e35b67a84
Rule Id: 4c3815bb-e092-4cd9-9528-d662c458e081
Rule Name: A script hung or exceeded its specified timeout
Time Added: 6/10/2004 5:00:04 PM
Time of First Event: 6/10/2004 5:00:00 PM
Modified By: NT AUTHORITY\NETWORK SERVICE
The response 'script: AD Topology Discovery' has been running more than 300
seconds
and exceeded the time allowed to run. This might indicate the response is
engaged
in an infinite loop or is hanging.
The response is running on thread '724' in the process MOMHost.exe with
process id
'2364'.
Management Group: GTMOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
and then
The host process for script responses will be restarted to recover from
responses
that might have been engaged in an infinite loop or hanging.
Management Group: GTMOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
finally
The response processor failed to execute a response. The response returned
the
error message: The remote procedure call failed.
Rule ID: {250F4C13-E035-43C5-961D-1424D934699F}
Response description: script: AD Topology Discovery
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Resolution *** Jul 2 2004 10:31AM vreavis
In environments where there is a large AD infrastructure or a lot of DCs,
this
script may not complete in a timely manner. Check the Script frequency
setting in the rule.
Right click on Rule Groups in the Admin Console and search for all rules
that run
the script AD Topology Discovery. Open the rule properties and under the
DataProvider tab, you can notice the "Provider name" indicates that it is
scheduled for every 30 minutes. Choose the Modify button and raised it to
90
minutes and the problem went away.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
TITLE: MOM://AD Topology Discovery script logs "Topology Discovery did not
fully discover topology"
[ ]
**Problem** Windows Server 2003 Enterprise [2003 -W_5826 ]
ID: SOX050113700006 CRT: Jan 13 2005 MOD: Jan 13 2005 STS:Customer
Verified
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Problem Description ***
=========
- Roughly every 30 minutes, DCs with MOM agents installed may report an
alert
from the AD Topology Discovery script
- It states "Description: Failed to get the flat names for the computer
'<name
of other DC>'"
- Also "The error returned was: 'Permission denied' (0x46)"
======
- This is caused by an RPC authentication failure which was caused by
mismatched
SMB signing policy settings in my customer's environment
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
*** Resolution *** Jan 13 2005 7:07AM keiththo
=========
- This problem can be fixed by correcting the SMB Signing policies to
either
consistently allow or not require signing between servers
==============
- This was verified by running the following three lines as a VB script
which
returned error 0x80040046
Set oOOMADs = CreateObject("McActiveDir.ActiveDirectory")
strFlatDomainName = oOOMADs.GetFlatDomainForDC("dc5cd.dept.clinlan.local")
WScript.Echo err.number
- The script above will display a prompt with the return code of call
GetFlatDomainForDC() -> 0 is success, etc
- It should first be run while logged on as a user with Admin rights ->
if the
return code is 0 then run it as the MOM Action Account
- GetFlatDomainForDC() is a function exported by OOMADS.dll, part of the
Active
Directory Management Pack Helper Objects
- The function simply makes a remote RPC call to run DsGetDcName() on
the DC
listed as the first and only parameter
- Note that the original error in this case was 0x800401CE -> the error
changed
after applying the Q889054 ReplProv hotfix
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

Eugen

2006-04-18 14:10:02 UTC

Permalink

Hi,
I have the same problem with a DC, after I ran "Update Agent Settings",
everything seems to be alright.
Best rgds,