TechNote (Archived)

Fewer users can access a Breeze Meeting than what the Meeting Peak Concurrent Users Quota reflects

Issue

---

Although the Meeting Peak Concurrent Users Quota, which can be found by going to the Breeze Manager and clicking on Administration, reflects the fact that additional users can join the meeting, users attempting to join the meeting receive an error that the quota has been exceeded.

Reason

---

When a user logs into a meeting, Breeze increments the Meeting Peak Concurrent Users Quota but does not decrement it back when the user logs out of the meeting. Over time, the Meeting Peak Concurrent Users Quota keeps increasing and the quota limit is reached. Consequently, fewer users can access a meeting than what the Meeting Peak Concurrent Users Quota reflects.

Solution

---

1. Make sure all users are logged out of all meetings.
2. If you are using the embedded database engine, which ships with Breeze, run the following query against the Breeze embedded database from the command line, which can be accessed by typing "cmd" from Start > Run:
   
   osql -E -d BreezeDB -Q "select used from pps_acl_quotas where quota_id = 12" -o c:\output.txt
3. Open the output.txt file generated from the query above.
4. If it's anything other than 0 (zero), please do the following:
   1. Make sure all users are logged out of all meetings.
   2. Shut down the Macromedia Breeze Application service from the Services window, which is accessible via the Control Panel.
   3. Run the following commands from the command line, which can be accessed by typing "cmd" from Start > Run:
      • 'osql -E', hit <Enter> to login to the database.
      • ‘use BreezeDB, hit <Enter>.
      • ‘update pps_acl_quotas set used = 0, hit<Enter>.
      • ‘where acl_id in, hit <Enter>.
      • ‘(select acl_id from pps_acl_rollup, hit<Enter>.
      • ‘where parent_acl_id = 7) , hit<Enter>.
      • ‘and quota_id = 12; , hit <Enter>.
      • ‘go, hit <Enter>.
      • Type ˜exit to log out from the database, after the query is successfully executed.
      Note:BreezeDB, in italics above, should be replaced by the name of the database that Breeze is connected to.

To prevent this issue from happening again, please schedule downtime and apply Breeze 5.1 Service Pack 1.

Search Support

---