Differences

This shows you the differences between two versions of the page.

--- troubleshooting:add_user [2019/04/16 00:56] – Scott Cunliffe
+++ troubleshooting:add_user [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 ===== This User Has No Access =====
+{{tapemaster_user_uncommited.png}}
 When assigning access rights to a [[object:user|User]], they may be assigned individually, through Group access or a combination of both.
@@ Line 12: / Line 14: @@
 If you are assigning access rights via the assigned Group only, click ''No'' to continue.
+===== Access Validation =====
+{{tapemaster_user_access_violation.png}}
+When presented with the error popup ''The access element has no access at all.  Are you sure that you want to add an element with no access'', click ''No'' and add appropriate User access rights (Read, Write, Alter and/or Catalog) to Customer-ID Access before clicking ''Add''.
@@ Line 17: / Line 25: @@
 ==== User-ID Is Already Defined ====
+{{tapemaster_user_already_defined.png}}
 ''User-ID Is Already Defined'' is presented when the [[object:user|User-ID]] you are attempting to create already exists in the TapeTrack database.
@@ Line 23: / Line 33: @@
 ==== Unknown Group-ID ====
+{{tapemaster_user_unknown_group.png}}
 ''Unknown Group-ID'' is presented when the [[object:user|User-ID]] you are attempting to create has not yet been assigned to a ''[[:master:user|Group]]''.
@@ Line 29: / Line 41: @@
 ====  Illegal Key Value Was Specified ====
+{{tapemaster_user_illegal_key.png}}
 ''Illegal Key Value Was Specified'' is presented when the [[object:user|User-ID]] you are attempting to create is either blank or contains an illegal character, or starts with a space, period or dash.
@@ Line 36: / Line 50: @@
 ====  Database Write Operation Failed ====
-Duplicate email address already assigned to another user
+Duplicate email address already assigned to another [[object:user|User]].  As you can login to TapeTrack with either your User Name or email address (Windows AD login excluded) the email addresses must be unique to each [[object:user|User-ID]].