I was planning on using Crystal Report Server 2008 for my web application. It says that I can buy 5 CAL. It also says that CALs are for concurrent users and can have 100 recipients. What does that mean? does that mean that 100 users can view reports simultaneously just using 5 CALs? Is it 100 recipients for all 5 CAL or 100 recipient per CAL?
According to their documentation:
Licensing for internal corporate deployment End-user report viewing
is licensed through concurrent access licenses (CAL). This means that
a set number of end users can simultaneously connect to Crystal
Reports Server. For example, a five CAL license enables five end users
to be simultaneously logged on to the system. The sixth end user that
attempts to log on will be denied access until one of the first five
user logs off of his/her session times out.
So, issue part the first: one concurrent user per concurrent access license.
Issue part the second: the allowed number of publishing recipients. From their licensing document:
The number of publishing recipients varies according to the number of
concurrent access licenses (CAL) licenses.
5 CAL, 100 recipients
10 CAL, 250 recipients
20 CAL, 1000 recipients
250 CAL, Unlimited recipients
So, for 5 CAL, you receive 100 recipients in accordance with this tiered model. Each "recipient" appears to be a single user that can access Crystal Reports' data-driven publishing feature.
Note that some additional restrictions may apply. For the version of Crystal Reports Server mentioned in the documentation above, a maximum of 20 CAL is allowed per deployment.
Related
After 40 calls to users.settings.filters.create I start to receive User-rate limit errors. All future filters.create calls then fail for the next (approx) 24hrs. Specific error message below.
HTTP 429
"User-rate limit exceeded. Retry after 2021-05-19T07:24:15.104Z
(Forwarding rules)] Location[ - ] Reason[rateLimitExceeded]
Domain[global]"
I have a 5-second delay between each call, so well under the published daily usage and per-user rate limits. I calculate the API allows 250 / 5 = 50 calls per second.
https://developers.google.com/gmail/api/reference/quota
We are using Google Workspace Legacy edition, the project OAuth consent is set for Internal use and the project is not verified (not a requirement for Internal).
Is there an obvious reason that 40 consecutive filters.create calls spread over 200 seconds would trigger a User-rate limit in these circumstances?
Limitations for unverified apps are across the board. The fact that your app is for internal use only doesn't matter you must still abide by the unverified app restrictions.
If you want to be able to send more then that you will need to apply for verification.
Because your app is for workspace account and internal use it should be easer for you to verify it.
I have a query regarding outlook 365 cached mode. Say for example a new user has a outlook mails on server for three months say JAN, FEB and MAR. Let's say we are in 1st of April, iam configuring outlook365 cached mode to 1 month. So March mails will be available offline. Let's say one month is passed, now we are in MAY. Now what happens to MAR month mail which is already downloaded offline, since cache is set to one month. Will MARCH and APRIL mails will be available offline, or only APRIL mails will be available and march gets removed locally?
By default, if Cached Exchange Mode is enabled, Outlook caches email messages only from the last N months (in your case - 1-month-old) and removes anything older from the local cache for the PC. These default settings depend on the device, with mobile devices having smaller default settings. The email messages that are removed from the local cache are still available for users to view, but they’ll need to be connected to Exchange Server to view them. Users can view messages that were removed from the local cache by scrolling to the end of a message list in a folder and clicking the message Click here to view more on Microsoft Exchange. Users can also change how much email to keep offline. The administrator can change the default age or enforce the age of email messages that are removed from the local cache.
Note: This question is about something that I do not understand in the documentation here:
https://developers.google.com/gmail/api/v1/reference/quota#concurrent_requests
Concurrent Requests
The Gmail API enforces a per-user concurrent request limit (in
addition to the per-user rate limit). This limit is shared by all
Gmail API clients accessing a given user and ensures that no API
client is overloading a Gmail user mailbox or their backend server.
enforces a per-user concurrent request limit (in addition to the per-user rate limit).
I do not find what is the 'per-user concurrent request' anywhere in their documentation. Whereas the per-user rate limit is found at the top in the same page.
https://developers.google.com/gmail/api/v1/reference/quota#top_of_page
The Gmail API enforces a per-user concurrent request limit (in addition to the per-user rate limit). This limit is shared by all Gmail API clients accessing a given user and ensures that no API client is overloading a Gmail user mailbox or their backend server.
The confusion here is the difference between per-user concurrent request limit and per-user rate limit
Lets say I make an app that lets users read from their Gmail account. I am going to be limited by the number of request each user can make though MY app the limit is per-user rate limit
Now lets say the user installs your app which also allows them to access their Gmail account. You are also limited to how fast the user can access the api via the per-user rate limit.
However both of our APPs and the gmail and inbox apps are are all running with the same per-user concurrent request limit concurrent meaning across all of the apps the user is using.
the per-user concurrent request limit is probably there to ensure that a developer doesn't create a number of different projects and rip data using all of them.
To my knowledge per-user concurrent request limit is not documented its a stealth limit and i have never seen anyone who has been able to nail down exactly what the numbers are for the concurrent limits in Google APIs. With the exception of the Google Analytics API which is 10000 not including the google analytics website and the official mobile apps
Example:
per-user rate limit
User number one logs in and lists all of his emails he has 10 user gets no error.
User number two logs in, he has 1000 emails and your application tries
to select them all out in 1 second. You are going to get a rate limit error for this user. You are flooding google.
However apps by other developers will be able to access the user inbox via the API
per-user concurrent
user number one is only running your application. logs in and lists all of his emails he has 10 user gets no error.
User number two is running your application and 20 other applications by other developers. Tries lists all of his emails assuming he has done this on all the applications at the same time he may end up getting an error.
These errors are user based due to the name Per-user in the name of the limit.
Example 2:
Lets look at the Google analytics API because i know the hard numbers for this api.
A user using your app can max make 100 requests over 90 seconds. (User-app based)
An application can make max 50000 requests a day. (App Based)
An all Applications can max make 10000 requests a day against a view (concurrent app based)
The API quota for my project was successfully increased to 4M through the application process. This is confirmed in the details for the quota via the Google Developer console quota page for the enabled API.
Videos are, however, being rejected with this message after just the standard 50 uploads with this message:
Task 310: Upload failed. Exception: HttpError 400 "The user has exceeded the number of videos they may upload."
Here is an example of a successfully published video.
Thousands of videos are waiting in the queue from an event that finished days ago. Several people from Google have been trying to help but this morning I was asked to post on Stack Overflow.
badRequest (400) uploadLimitExceeded The user has exceeded the number of videos they may upload.
This isn't a project based quota which would have been upgraded. This is a user based quota which can not be upgraded. It means that the user in question has exceed their upload limit for the day. The YouTube API has a slightly different quota system than other Google APIs. The ones listed in developer console are just the general ones. You should check calculating quota usage
200,000 read operations that each retrieve two resource parts.
10,000 write operations and 90,000 additional read operations that each retrieve two resource parts.
400 video uploads, 1500 write operations, and 50,000 read operations that each retrieve two resource parts.
This quota should reset at midnight West Coast USA time. It sounds strange to me that you are seeing this after only 50 videos. I am not all that sure what denotes a user; it could be IP address or the authenticated user.
Videos: insert
Quota impact: A call to this method has a quota cost of 1600 units in addition to the costs of the specified resource parts.
So Google support got back with a note saying that we'll just have to wait for the quota refresh... I can't even see any difference from the 'increased upload' capacity and the limit does seem to be 50 (roughly at least). I've asked them how long the anti-spam upload freeze actually is but I'll carry on breathing whilst I wait for that puppy.
Special thanks for help from DalmTo and halfer though.
Message from Google Support:
I have enabled "Increased upload" capacity for your channel. Please
re-login to your account and check if all works fine.
We don't have any 50 videos per day limit anymore tell the truth, but
we have antispam algorithms which may temporary suspend your Upload
function.
This algorithm is confidential, so I can not discuss this feature in
details. If you can not upload videos you should just wait I am
afraid. But I hope "Increased upload" will help.
I am attempting to speed up sent e-mail in CRM 2011 by editing the Microsoft.Crm.Tools.EmailAgent.xml file. I am modifying the SchedulingPeriod element and I am not sure if the interval setting is in seconds or milliseconds.
The CRM 4.0 documentation from Microsoft states “all time intervals in the configuration file are specified in milliseconds.” http://msdn.microsoft.com/en-us/library/cc906241.aspx
The Microsoft Dynamics CRM 2011 Unleashed Book states “The outgoing e-mails are processed asynchronously, and the default polling is scheduled for every 1,000 seconds (about 15 minutes), so you must wait that time before the e-mails are actually sent.”
Tip: To increase the speed at which outgoing e-mails are sent, you can edit the configuration file Microsoft.Crm.Tools.EmailAgent.xml (which is usually located at C:\Program Files\Microsoft CRM Email\Service) and find the SchedulingPeriod element. We recommend changing its default value to 10 seconds.
Question 1: In CRM 2011, is the SchedulingPeriod specified in milliseconds or seconds?
Question 2: In CRM 2011, is the default SchedulingPeriod (1,000) = 1 second or 15 minutes?
The Microsoft Dynamics CRM 2011 Unleashed book mentions speeding up outgoing e-mails by changing the default value to 10 seconds.
Question 3: In CRM 2011, will changing the SchedulingPeriod to (10) = 10 seconds or 10 milliseconds?
it is in seconds, 1000 seconds == 16 minutes 35 seconds, there should also be a setting for number of threads just above this in the file that you can increase to improve performance.
Like everything CRM though test it first as your setup might behave differently to mine, speeding this up might just move your bottleneck elsewhere - usually the UI if you havent put it on another server. also concider if you are using Virtual Servers and they are on the same physical hardware making one work more can slow the others if they aren't balenced correctly.