Have you had an RQM server on this machine in the past? It sounds like the server license might be expired (even though I realize you just installed!).

Without a QM CAL you won't be able to log in at /jazz/web/console, but you should still be able to log in at /jazz/admin, and this will allow you to fix the licensing problem.

In /jazz/admin, navigate to Server -> License Key Management. The direct path is is:
/jazz/admin#action=com.ibm.team.repository.admin.manageLicenses

Under server activation key, what is the status?

If it shows expired, import a permanent key (if you have one).

If you don't yet have a license, you can import an "extended trial". As an IBMer you can self-nominate for one here:
http://w3.tap.ibm.com/w3ki08/display/ratlsalesexec/SDP%20Eval%20Extensions

.

Now, try going back to /jazz/setup and continue.

Or, just go to User Management > Client Access License Management in the /jazz/admin interface . The direct path is:
/jazz/admin#action=com.ibm.team.repository.manageUserCALs

Let us know what you find.

lavernita wrote:

I downloaded RQM 2.0 from Extreme Leverage and installed it.. I
started the server and logged in the
https://hostname:9444/jazz/setup. I clicked on the fastpath button
and proceeded through the steps.
I selected the Tomcat User Database for the user registry.
I created an administrator account
I disabled ADMIN access.
In the Assign Client Access Licenses section, there was a warning
message... "Warning: The server has reached the maximum user
limit. You will not be able to increase the number of users that are
assigned a Client Access License type that is counted in the server
user limit."
I attempted to select the "Rational Quality Manager - Quality
Manager" client access license, but I could not. The checkbox
was greyed out, but the status said available. The other 2 licenses
were available for selection. What could be wrong... do I need to
install a different license key?

This is a known problem and I think is documented in the release notes.

You can ignore it and click next and everything will be OK. This has
to do with the unlimited user capability of RQM 2.0