It's all about the answers!

Ask a question

How to fix the "Project area cannot be saved" error when "The user "ADMIN" does not exist in the database."

Roy Schatz (122) | asked Jun 25 '15, 7:14 p.m.
Using CLM 5.0.2 I am attempting to create a new Project Area in Quality Manager (\qm).
My User ID has JazzAdmins, JazzUsers, and JazzProjectAdmins permission.

When I am trying to save the new Project Area (with Default Quality Management Processes) I receive a "Project area cannot be saved" error with the following error stack trace details:
Error 500 The user "ADMIN" does not exist in the database at at at at at at at at at at at at at sun.reflect.GeneratedMethodAccessor1706.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke( at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0( at

I am not sure what "The user "ADMIN" does not exist in the database" is about? 
Do we need to create a User "ADMIN" that requires certain permissions to make this work?

Anybody else who has seen this error in CLM v5.0.2 and know how to resolve this?

One answer

permanent link
Donald Nong (14.5k414) | answered Jun 26 '15, 12:13 a.m.
A couple of things to check.
1. Is the user account "ADMIN" disabled? You just need to confirm its status, and don't need to re-enable it if it is disabled.
2. Is your own user account correctly mapped to a Jazz user? When a user authenticates successfully with the JazzAdmins role but does not have a correctly mapped Jazz user, the user account may be mapped to "ADMIN" for some reason, regardless "ADMIN" is disabled or not.

Note: "ADMIN" is the default user account and you should not create a new one.

Roy Schatz commented Jun 26 '15, 2:58 p.m. | edited Jun 26 '15, 3:00 p.m.
First, I want to say thank you very much for your quick response. This is greatly appreciated and I think you might have identified the issue here quite well. However, I am not quite clear about our next steps...


1. Our administration was not able to find an ADMIN user. Not sure what happened there. If the ADMIN user got accidentally removed, what are the steps to rectify this? I assume that there might be more to it than just adding an ADMIN user via the application?
2. I am not sure what you mean by the user account being correctly mapped to a Jazz user? Could you please expand on that? What is it that we would need to look for and correct to fix the mapping?

Donald Nong commented Jun 28 '15, 8:49 p.m.

Check the document that I posted. The "Admin" account is a built-in one and does not need to appear on an LDAP server (of course you need another user that has JazzAdmins role to replace it).
For mapping, without going into the technical details, if you can see your name displayed at the top right corner after logging on, you can consider it done correctly.

Your answer

Register or to post your answer.