Nothing been changed, user getting started to not able to import model into Rhapsody DM project area

Did you check out the link that Dan provided about managing licenses?  If you look at the issued licenses, are all of the floating licenses issued?  The documentation at http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m2/index.jsp?topic=%2Fcom.ibm.jazz.repository.web.admin.doc%2Ftopics%2Fc_managing_licenses.html shows how to see what licenses are issued. 

I have found the following instruction quite useful:

To view a list of issued client access licenses on the current license server:

1. Click the Users tab and then select Acquired Floating Licenses.
   

Without seeing exactly what the customer is seeing, it's hard to debug any further.  I would probably check to make sure that the licenses do exist, and that they have been assigned correctly to the users.  I would do as you mentioned and test with a smaller number of users.  I don't see how going through set up again would affect the licenses.  However, I am not a license expert.

Hi Jin,

I had a quick look at the code and it is possible that it is not in fact a license issue; rather, it could be a permissions problem.

1) Please go to https://servername:port/dm/admin and from the Project Areas menu, choose Active Project Areas.
2) Choose the project area where you are trying to perform the import.
3) Verify the correct process has been chosen -- although you cannot change it at this point, this affects the permissions.
4) In the Members and Administrators sections, verify the users who are trying to import are included appropriately (by clicking the Add... link).
5) Click on the Permissions link at the left of the page.
6) As a test to verify that this will resolve the issue, click Project Configuration and ensure all items in the Permitted Actions box are checked.
7) Repeat this with Team Configuration and ensure all items in the Permitted Actions box are checked.
8) Verify that the permissions problem is now resolved and the import now works.
9) Repeat steps 6 and 7 but set the permitted actions more selectively for security reasons.

Hi Jin, is the customer running WAS 8.0.0.3 or later? If they are can you check to see if they have the following custom property set in Session Management: InvalidateOnUnauthorizedSessionRequestException

This value can be found by logging into WAS Console and going to:

Server->Server Types->WebSphere Application Server->Server1->Session Management->Custom Properties

If it is not set then add the new variable and set it to true. Then Restart WAS and try the scenario again.

There was a similar issue in CLM that caused problems when logging in and out of one user then logging in as a different user. The error was different but the scenario seems similar. In our case even though you logged out of one account and into another it still tried to use the credentials of the previous user. I think it is worth a try to see if this solves there problem.

 Thank you, all 

 Currently.