Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
10 subscribers
Views
1517 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Hello Team, We are getting below error in logs. Any idea on this it s
gauravp
over 9 years ago
Hello Team,
We are getting below error in logs. Any idea on this it seems data is not inserting in database.
2014-07-08 14:12:03,801 [ajp-/0.0.0.0:8009-11] ERROR org.hibernate.util.JDBCExceptionReporter - Violation of UNIQUE KEY constraint 'usr_username_uc'. Cannot insert duplicate key in object 'dbo.usr'. The duplicate key value is (ggpand).
...
OriginalPostID-115481
OriginalPostID-115481
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 9 years ago
The table in question is part of the primary data source of Appian and stores all users who have logged in to Tempo. The table is case insensitive meaning ggpand = GGPAND. If there's an entry with the same characters but different case (e.g. uppercase, camelcase, etc.) such as GGPAND already in the db.usr table and you try to login with ggpand you will see that error message and Tempo will not work properly for that account.
Assuming that the user account you really need is ggpand then simply use the Rename Users plug-in to rename GGPAND to GGPAND_OLD and then deactivate it. Then in the dbo.usr table rename GGPAND to GGPAND_OLD too. This will release the ggpand username so you stop seeing this error when ggpand logs in to Tempo
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 9 years ago
The table in question is part of the primary data source of Appian and stores all users who have logged in to Tempo. The table is case insensitive meaning ggpand = GGPAND. If there's an entry with the same characters but different case (e.g. uppercase, camelcase, etc.) such as GGPAND already in the db.usr table and you try to login with ggpand you will see that error message and Tempo will not work properly for that account.
Assuming that the user account you really need is ggpand then simply use the Rename Users plug-in to rename GGPAND to GGPAND_OLD and then deactivate it. Then in the dbo.usr table rename GGPAND to GGPAND_OLD too. This will release the ggpand username so you stop seeing this error when ggpand logs in to Tempo
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data