We are using Biblioscape 6.6 (Library Edition) and got a problem with BiblioWeb license. That happened when the PC where Biblioscape was installed crashed due to bad RAM. Before that I was using a "number of hits" type of license, which was supposed to have 50,000 hits. However, when I run BiblioWeb program it says that the limit is 3764 with total hits made of 3936. Now, I cannot use that type of license anymore. We definitely couldn't use all the hits available since I'm only setting up the program (however, 3936 seems to be a reasonable number).
My questions are:
1. It looks to me to be a bug or malfunctioning of the system, when the total number of allowed hits was cut down to 3764. How the initial 50,000 can be restored?
2. From the Biblioweb website I found that Biblioscape Professional edition comes with 3 "Write" user accounts, 3 "Read" user accounts, 50,000 hits accounts, or 1 concurrent user account. Biblioscape Librarian edition comes with 3 concurrent user accounts.
In the registration I see that there are 3 write and 3 user accounts available and ONLY 1 concurrent user. How I can restore the number of concurrent users allowed in Librarian edition?
3. Is there a log created if BiblioWeb runs as a service? I also was not able to identify the problem when BiblioWeb service refused to start
until I ran BiblioWeb program. Could BiblioWeb service report the "license" errors to Windows Events log for better ?
4. As I understand that each request for a graphic file inside BiblioWeb Web pages is counted as a hit. Does this mean that all BiblioWeb native
graphics are counted as hits every time the Web pages are reloaded? I can not assume that the graphic files are always cached, because some of our computers get cleaned pretty regularly. Is there a way to decrease the number of "non catalog" request hits? Or the only way would be to remove all graphics from web pages?
Paul, I also sent a email on support@biblioscape.com a few days ago, but haven't got any reply. Does the email work or it's better to use forum?
Thank you a lot!
Oleg
The problem is likely caused
The problem is likely caused by program crashing. Please let me know your "Machine ID". I will email you the key to fixe the problem. I have just replied your email. Sorry for answering your email late.