Users might appear as UNKNOWN\username if a domain component part of the distinguished name in AD contains the string 'DC' itself

Versions / Builds Affected

20131111

Status

Resolved

Problem Summary

Users might appear as UNKNOWN\username if a domain component part of the distinguished name in AD contains the string 'DC' itself

TT / JIRAID

1824

How to Identify

Let's consider the following scenario: - the customer as a Active Directory domain named: DCABC (NetBIOS name) / dcabc.com (DNS) - his users would normally be named: DCABC\user1, DCABC\user2 or DCABC\user3 - in some pages within MARC (e.g. under Configuration > Access Control) the users appear with the literal word UNKNOWN instead of the NetBIOS domain name though (e.g. UNKNOWN\user1, UNKNOWN\user2 or UNKNOWN\user3) - When checking the arc_users table / userName column (via SELECT * FROM arc_users) of a database you would see the names in the same way (with the word UNKNOWN) The key here is that a domain component part of the Distinguished Names (http://msdn.microsoft.com/en-us/library/aa366101(v=vs.85).aspx) contains the string 'dc' itself. As an example, let's look at the Distinguished Name of User 1: CN=User1,OU=MyOrganizationalUnit, DC=dcabc,DC=com. Here the important part is that the value of DC= which is 'dcabc' - we see that it contains 'dc'. You can confirm the Distinguished Name by checking: Core\DebugLogs\usercntmaad.txt

Workaround / Fix Details

Fixed in MARC2014 build 20140616 ---- CAUTION - To update the DBs if needed the following query can be used:

Required Actions

IF IT IS NEEDED TO FIX THE EXISTING USER ROWS IN THE DBS: 1. Pause archival of items (e.g. disable any data sources) 2. Take a backup of the system incl. all data (esp. the Archive Stores and DBs) 3. Edit the SQL query below to match the customer's domain name (replace DCABC with their domain - the rest must not be changed!): UPDATE arc_users SET userName=REPLACE(userName,'UNKNOWN\','DCABC\'); 4. Upgrade to MARC2014 build 20140616 or newer 5. Start archival of items again ----- IF IT IS NOT NEEDED TO FIX THE EXISTING USER ROWS IN THE DBS: 1. Upgrade to MARC2014 build 20140616 or newer