AD forest discovery fails with "unexpected exception"
AD forest discovery fails and does not continue parse through the other forests after and "Discovery is being aborted due to an unexpected exception".
We would like to see where the discovery sees that it cannot contact or reach any given forest but is able to continue with the other forests to collect the data.
Gregor Hindman
shared this idea
1 comment
-
Scott Macpherson
commented
We just had this issue and resolved it with our PFE. We are on SCCM CB 1610 and will be updating to 1706 in a couple of weeks. We found that new AD sites were not being brought into our Boundaries thru the Forest Discovery. We have 33 other Forests trusted to our main Forest we are migrating all 33 into. The Discovery was stopping after 7 Forests were discovered. Seemed like it was discovering them alphabetically from the bottom up. An error message was found in the ADForestDisc.log log that states " ERROR: [ForestDiscoveryAgent]: Discovery is being aborted due to an unexpected exception.". No other errors were found. We resolved this temporarily by turning off discovery for all domains that are not primary to our needs and the discovery completes successfully now. We only have this environment published to 2 of the 33 Forests. Maybe if the Discovery were set to on do Forests that are published to and we have to turn on any others we want would be beneficial.