Question | Answer |
|
|
Users are getting the message All resources are currently | First, refresh the Resources list in the HP SAM administrative |
in use. Please try again later but there appear to be free | console and check to see if any resources are available in the |
resources according to the HP SAM administrative console. | role (or dedicated resource) the user is attempting to access. If |
What are the potential causes for this? | no resources are shown as Available, try performing a |
| Synchronize operation on all of the resources to ensure that |
| their status is current. If there are still no resources shown as |
| Available, the message is accurate and more resources can |
| be added to the pool or the HP SAM session timers can be |
| used to free up idle resources. |
| If there are resources shown as Available and users are still |
| getting this message, consider the other potential causes |
| below: |
| ● Some resources are marked as disabled in HP SAM. |
| ● Some resources are assigned to a user as a dedicated |
| resource. Check the Manage Users page to see if these |
| resources show up as dedicated to any users. |
| NOTE: If a resource is in a role and is also dedicated |
| to a user, it will never be allocated to user who requests |
| a resource using that role. In other words, it really is |
| dedicated to that one user only. |
| ● Some resources may be temporarily reserved. When HP |
| SAM allocates a resource to a user, it reserves the |
| resource for that user for a certain amount of time (3 |
| minutes, by default) to allow that user time to log on. |
| During this time, the resource shows as Available in HP |
| SAM with no user logged in, but cannot be allocated to |
| any other user. |
| NOTE: This scenario may occur more frequently if this |
| time period is increased. This is set under System Settings |
| General via the User |
| ● Verify that the HP Session Allocation Management |
| Service is running on the HP SAM server. Typically, if |
| this service is not running, it causes resources to go |
| offline when users attempt to log on. |
| ● Verify that the HP SAM communication port (UDP |
| 47777, by default) is not blocked by a firewall. This is |
| the port over which the HP SAM Registration Service and |
| the HP SAM Server communicate blade status. Typically, |
| when this port is blocked, resources go offline when |
| users attempt to log on. |
| ● Verify that the resources show the desired protocol in the |
| HP SAM administrative console. For example, if the HP |
| SAM clients are set to ONLY connect via RGS, then |
| resources which show as Available but do not show |
| the RGS protocol are not allocated to the users. |
| ● Verify that all users have valid UPN names in Active |
| Directory. Users without UPN names may be allocated to |
| a resource by HP SAM, but after disconnecting, they |
| may be sent to a different resource and not sent back to |
| their resource. UPN names are required for proper HP |
| SAM to operate properly. |
|
|
91