Solved: Unity Connection User Import Error

keithchiang · ‎08-03-2012

We are using UC version 8.6.2.20000-2. When I try to import a user, I received following error -

Friday, August 3, 2012 9:45:58 AM EDT ERROR importing user (NAME) with extension = XXXXXX : Department input is invalid

From Tomcat log, I see -

15:36:00.619 |16247,,,Cuca,3,ERROR [pool-7-thread-30] com.cisco.unity.dao.impl.SubscriberDAOImpl - field validation exception

15:36:00.619 |16247,,,Cuca,2,ERROR [pool-7-thread-30] com.cisco.unity.async.UserImporter - Exception while importing user: null

15:36:40.411 |16247,,,Cuca,4,ERROR [pool-7-thread-30] com.cisco.unity.datatools.BeanHelper - invalid field: name=department, value=Executive Administration

, constraint=regex: ^[^\x00-\x1F\x7F]*$

Any help or advice is much appreciated. Thanks in advance!

Bradford Magnani · ‎08-03-2012

Try creating a new test user in the same department in AD and import them to see if they have the same issue. Trying to narrow down what works and what doesn't will be key.

Hope that helps,

Brad

View solution in original post

Bradford Magnani · ‎08-03-2012

Hi Keith,

How are you importing the user? Directly from LDAP? BAT with CSV?

Does this happen to all users or only specific ones within that department?

Brad

keithchiang · ‎08-03-2012

Importing from LDAP. I can'tconfirm if this is affecting anyone else.

Bradford Magnani · ‎08-03-2012

Try creating a new test user in the same department in AD and import them to see if they have the same issue. Trying to narrow down what works and what doesn't will be key.

Hope that helps,

Brad

keithchiang · ‎08-03-2012

We created a new AD account with everything the same except using different name and user ID. I was able to import that user. We deleted the old AD account and UC account, change the new AD with the original account's user name and ID, resync UC LDAP, import again...success. Very wierd. Thank you for your help Bradford.

Bradford Magnani · ‎08-03-2012

Great, glad it's working for you

natevdw · ‎03-16-2018

There's probably a blank space in the phone number in active directory! Or somewhere in one of the AD fields. Check for blank spaces.