Is
in a windows domain user name interpretted as a line feed?

Question

I had this happen when I was adding two new employees to my geodatabases with their OS logins from our Windows domain, using ArcCatalog 10.6.1 and the Administration> Add User workflow.  The first guy went easy,  the next guy didn't work. His domain login is ykfp/nrom***. The error message made us wonder if /n is getting read as a line feed and if I needed to escape this with quotes or something.  There must have been other places where someone had a domain name that included /n however, so it seems unlikely that I am the first to encounter this.   I also tried the other syntax for his domain name nrom***@KFO.local.

Dropbox - AddingnromeroEd.png

Yesterday, I successfully added ykfp\Nrom*** as a user to one geodatabase.  But my domain manager had given me ykfp
rom*** as the login.  I haven't heard back from the domain manager when I asked him to check on the capitalization.  Does capitalization matter in Windows OS authentication?  I don't have a way to test this to see if it will work for the user.  I can't make an account on a PC in the domain as this user to try the geodatabase connection as ykfp\Nrom*** because I don't know the user's password.  Tomorrow, I plan to be in the user's office where I hope to work with him to install Desktop and add his geodatabase connections.

DanPatterson_Retired · Answer

I wonder if they checked the others I listed as well... \a  \r

plus all the others that will throw Unicode errors

PaulHuffman · Answer

Yes,  this is a known bug.  https://support.esri.com/en/bugs/nimbus/TklNMDgyNjc2   It could turn up with other tools and Arcpy functions and also with /t.  Capitalize these if you can. Thanks to Miguel at ESRI Support.

DanPatterson_Retired · Answer

No clue, but if 
 fails, you might want to check for a few more trailing a slash

print("
xx	x\ax")x       xyzThere are loads... called escape charactersEscape Characters — Python Reference (The Right Way) 0.1 documentation Which is why I don't like \ anything in the windows Unicode and/or python world 
sometimes they throw useful error messages, leaving people a tad confused.  Your IT department should have a protocol setup I am sureprint("
xx	x\ax\xyz")
  File "<ipython-input-2-fcf9ff201aa5>", line 1
    print("
xx	x\ax\xyz")
         ^
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 12-13: truncated \xyz escape