Home

Results 1 to 4 of 4

Thread: NSM AD 3.1 & 3.1.1 303 error

Threaded View

  1. #1
    Join Date
    Sep 2009
    Posts
    9

    NSM AD 3.1 & 3.1.1 303 error

    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
    Last edited by nvdhaar; 13-Jun-2013 at 02:49 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •