Quantcast
Channel: Micro Focus Forums
Viewing all articles
Browse latest Browse all 11924

NSM AD 3.1 & 3.1.1 303 error

$
0
0
Hello,Somehow all our policies that use DFS stopt working after some months with out problems and i get the errors: 225 : The specified name could not be resolved by the network client. and 303 : Extended path information is missing for the specified network path. In the translog file i get a strange error: "Path conflict check failed while analyzing path info"It looks like NSM is mixing 2 DFS pathsCurrent State: 10 (Waiting for policy paths to become accessible) - Entering DoEvent() Current State: 10 (Waiting for policy paths to become accessible) - Getting information for policy path: "\\\DFS|Locaties|DOR1|Profiel\Deelnemers". Current State: 10 (Waiting for policy paths to become accessible) - Calculating leveling path... Current State: 10 (Waiting for policy paths to become accessible) - Path conflict check failed while analyzing path info, target: \\\DFS|Locaties|DOR1|Profiel\DeelnemersPolicy path: \\\DFS|Locaties|WSC1|Home\Medewerkers Current State: 10 (Waiting for policy paths to become accessible) - Removing "\\\DFS|Locaties|DOR1|Profiel\Deelnemers" from available paths. Current State: 10 (Waiting for policy paths to become accessible) - DoEvent() complete, result: 303 Current State: 10 (Waiting for policy paths to become accessible) - Entering DoEvent() We have at the moment 641 events waiting for processingYours,Niels

Viewing all articles
Browse latest Browse all 11924

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>