Does the user also have a Fixed or Floating AR System User license?

Is this the same for all users?

You can use the Application License Review in the AR System Admin Console to check that users have licenses assigned.

Martin

Hi,

Your image shows the AR System (Floating) User licences rather than application (Incident Management) - do you have enough of these configured in the AR System Admin  - Add or Remove Licenses console?

Martin

Hi

Please check the available floating license.

the above scenario occurs after all floating licenses are in use.

thanks

US

if you have enough AR Floating License, pls check do you have valid Incident Management Application License and valid Incident Management User Floating License....check these two once...i think the later one is making problem for u...application user floating...increase the numbers and try again

Hi,

as everyone has mentioned, the error message clearly explains the issue:

No free application user floating write license tokens are available.Currently accessing the application form in read-only mode.License will upgrade when one is available. : BMC:Incident Mgmt (ARWARN9862).

This means that the system has allocated all available BMC Incident Mgmt User Floating Licenses (Write tokens) in the pool.  Remembering here that you can allocate more than the number of installed Floating licenses to Users, but if more than the number of Users vs licenses log in at the same time, the additional Users will be allocated a Read license until another User releases the "Write" token.

Cheers

Carl

http://www.missingpiecessoftware.com/

Hi,

what is a "Lifetime" license?

If a user has not correctly logged out of the system when using a Floating license, the system will not release the license back into the license pool until the timeout is met - this is something to note when using Floating licenses and had been discussed here before. 

This means although you say that only 3-4 users are accessing Remedy at the same time, if these 3-4 user do not release the licenses correctly (i.e. logout correctly), then any other users that connect will consume the remaining free licenses until the timeout occurs.  So the system will believe that there are more users connected than actually possibly could be. 

You may need to adjust your timeout values to release the licenses more promptly for this type of situation.

As mentioned, you can check this in the license console to see how many users the system "believes" is consuming the allocated licenses.  This will give you an indication of what is occurring.

Other discussion surrounding Floating license also offer other tips on how to best manage these scenarios.

Cheers

Carl

Cheers

Carl

http://www.missingpiecessoftware.com/

Hi,

there are 2 parts to license allocation, one at the AR level and one at the Application level. 

The error you have posted indicates this is occuring at the Application level, but you have not stated what kind of AR license they have. 

This will also be taken into consideration when allocating a "Write" token for use.

Have you looked at what licenses are being allocated for both AR User and Application when this occurs?

What different combinations have you tested and validated against? i.e. Fixed AR User and Floating Application, Floating AR User and Floating Application, Floating AR User and Fixed Application ...

The Floating license understanding can be complex at time as it is not just based on a single license when accessing the Applications.  You need to check to see what is allocated at the time of the error which will give you an indication of what the system is allocating and not allowing.

Cheers

Carl

http://www.missingpiecessoftware.com/

go to ARSystem Administration Console--->License Review--->select the category as 'Application' and release all the Users from the system(you can also release the Server Licenses as well).

And make sure that you have enough 'Application User Floating License' and 'Application User Fixed License' in the Add/Remove Licenses for the Incident Management corresponding to the number of users concurrently would be accessing the system.

Wait for sometime, flush the midtier and browser cache and start testing the combination of AR Fixed + APP Fixed, AR Float + APP Float, AR Fixed+ App Float ....

as mentioned over here there is a timeout setting when the user is idle for sometime then the token would be grabbed from them and assigned to the pool check on that as well.