It's all about the answers!

Ask a question

RQM setup error on zlinux


Robert Lawrence (611) | asked Jul 14 '10, 11:07 a.m.
Installed RQM 2.0.1ifix1 on zlinux test system. Attempted to run setup.

Setup runs successfully through step 5 (LDAP settings). When I attempt to go to step 6 (next button), I see "saving settings" followed by "There was an error attempting to create the new user:". Setup cannot proceed beyond this point.

Server specifics:
SUSE Linux Enterprise Server 10 (s390x)
WebSphere 6.1.0.31, configured to authenticate using bluepages LDAP.
DB2 V9.5 fp5

Seeing this entry in the rqm.log:
13 Jul 2010 17:00:40,260 WARN com.ibm.team.repository.servlet.TeamServerServlet - CRJAZ1186I Authenticated user "Robert W. Lawrence" does not exist in the repository. Logging in as "ADMIN".

I created a user id for myself in the repository. Ran setup again, same error message.

Any thoughts on how to fix or work around this problem?

One answer



permanent link
Robert Lawrence (611) | answered Jul 15 '10, 4:38 p.m.
Installed RQM 2.0.1ifix1 on zlinux test system. Attempted to run setup.

Setup runs successfully through step 5 (LDAP settings). When I attempt to go to step 6 (next button), I see "saving settings" followed by "There was an error attempting to create the new user:". Setup cannot proceed beyond this point.

Server specifics:
SUSE Linux Enterprise Server 10 (s390x)
WebSphere 6.1.0.31, configured to authenticate using bluepages LDAP.
DB2 V9.5 fp5

Seeing this entry in the rqm.log:
13 Jul 2010 17:00:40,260 WARN com.ibm.team.repository.servlet.TeamServerServlet - CRJAZ1186I Authenticated user "Robert W. Lawrence" does not exist in the repository. Logging in as "ADMIN".

I created a user id for myself in the repository. Ran setup again, same error message.

Any thoughts on how to fix or work around this problem?



Found my problem.

Typo in WebSphere "Advanced LDAP user registry settings". User ID map was "*.mail". Should have been "*:mail".

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.