1 Reply Latest reply on Jun 17, 2010 3:06 PM by dmshimself

    AD Import errors

    gramsay Specialist

      Getting lots of this message in the import logs:


      "Could not set Target Attribute User.Notification Method = 2"


      Unfortunately it doesn't specify which users are giving the errors.

      Any idea what might cause this message? The default value is "External".

        • 1. Re: AD Import errors

          Just as an FYI Gtraham we always use a DB script to set that value for users due to issues in getting the import module to set these types of 'special' values.  We can also tune it that way to set different values depending on (say) if someone has an email address in their user record.  I'd like to think that at some point all DB scripts could go, but currently there are some areas that ened at leats one script, so why not have more than one.