Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 616
  • Last Modified:

Hi! I need help fixing a DN syntax error in a csv I am using to import a number of users into AD.

When I run the CSVDE command to import users into AD, I get this error:
Connecting to "smtest.smtestdom"
Logging in as current user using SSPI
Importing directory from file "1usertest.csv"
Loading entries
2: CN=Lonely Test,OU=Test Users,dc=smtestdom
Attribute 0) objectClass: user
Attribute 1) sAMAccountName: Ltest
Attribute 2) initials: F
Attribute 3) givenName: Lonely
Attribute 4) sn: Test
Attribute 5) cn: CN=Lonely Test
Attribute 6) ou: Test Users
Attribute 7) dc: smtestdom
Attribute 8) securityMediatorSSN: 123-45-6789
Attribute 9) securityMediatorClassifications: Apples
Attribute 10) securityMediatorCodewords: Seeds

Add error on line 2: Invalid DN Syntax
The server side error is "Multiple values were specified for an attribute that can have only one value."
0 entries modified successfully.
An error has occurred in the program
HELP!   Thank you!
0
hdk001
Asked:
hdk001
  • 3
  • 2
2 Solutions
 
Mike KlineCommented:
Try putting quotes around "CN=Lonely Test"
See if that helps you
Thanks
Mike
0
 
hdk001Author Commented:
Thanks Mike but that did not work.  I'm still getting a syntax error with the DN.  I checked for spaces, comma placement, everything.  I am at my wits end!  What could be the problem???
0
 
Mike KlineCommented:
Did you also try quotes around OU=test users,  not sure.  I'll try to test if I have time
Thanks
MIke
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
hdk001Author Commented:
We have tried the double quotes around the cn and also around the ou. When we use quotes the error is actually different and states "invalid parameter", which I believe is just due to the quotes.  Eventually this will be to import 4600+ users, but we're trying to test with just a dummy account for now to get the formatting correct.  We have used the other solutions on here to work through some other issues, but this one is holding us up. Thanks for your assistance.
0
 
Aaron_DentonCommented:
I've found this page to be a good reference.  Especially the sample import file.
http://www.computerperformance.co.uk/Logon/Logon_CSVDE_Bulk.htm
Also, http://www.computerperformance.co.uk/Logon/Logon_CSVDE_Errors.htm
I would do as it suggets and start with just the minimal set of 3 values to get the import working and then add more info if you need to one field at a time to determine which one is tripping you up.
0
 
hdk001Author Commented:
The minimal set of 3 was the catalyst that helped me figure out the rest. The tool was erroring out because some of the LDAP fields were seen as dupilcates.  After getting rid of the other fields it still didn't work.  So I arranged the colums in the exact order that the example used( from the article) and it worked!  Thanks!
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now