There are not enough Concurrent Access Licenses to log you on.

[woliveri]

Hello all,
I'm getting this error message below and don't know how to get rid of it. I'm using Crystal Reports 8.5 under VB6. I have created a dll which will open a report connecting to SQL Server in memory and export it to disk using rtf format. This works for a while then I get the error below. I'm cleaning up my references as I should so I'm not sure what's going on here.

#### Error #####
There are not enough Concurrent Access Licenses to log you on. This system has 5 Concurrent Access Licenses. Please try again later, or contact your system administrator to obtain more licenses. Licenses can be purchased direct from Seagate Software or through the Seagate Software Online Store.

#### End Error ###


Thanks for any help,

Bill

 

[lyanch]

Crystal Enterprise Standard, which is free with 8.5 has only 5 concurrent licenses. The message that you are receiving comes from CE which uses licenses even for unmanaged reports.

Lisa

 

[woliveri]

Lisa (or anyone else),

Any idea on how to get rid of it??? Can I uninstall CE Standard from CR 8.5??


Thanks in Advance,

bill

 

[lyanch]

They are separate installations. CE is the portion that allows you to report to the web. You may well be using it even though you might not realize it.

Lisa

 

[woliveri]

I don't ever recall installing CE and in fact, the documentation I've read say's it installs from a second CD which we don't have. On top of that, I've checked the install under Add/Remove programs and it's not listed in the installed programs when I go through the CR Wizzard for uninstalling or adding features.

However, I do see a Enterprise folder under Seagate Crystal Reports.

I found a document "Managing RDC Licenses within you ASP Applications" where it is written:

"If you are running the report from an ASP application using the RDC (Craxdrt.dll) and Rptserver.asp then you have downloaded the correct document for your method of web reporting"

I'm not using ASP but I am using the RDC for opening my report and then exporting it to disk as RTF format such as:

Dim CrxApp As CRAXDRT.Application
Public Report As CRAXDRT.Report

Set CrxApp = New CRAXDRT.Application
sReportPath = "\\server\c\rpts\somereport.rpt"

Set Report = CrxApp.OpenReport(sReportPath)


The last line is where I get nailed.


Then at the end I clean up my references:


If Not CrxApp Is Nothing Then
Set CrxApp = Nothing
End If
If Not Report Is Nothing Then
Set Report = Nothing
End If


This is killing me.....


Any suggestions on a way around this?

Any other methods available which do not use the RDC where I can open a report in memory and export it to disk as a RTF file?


thanks in advance,

bill

 

[kenhamady]

Are you creating a server based app or a client based application? The 5 concurrent limit is not just Crystal Enterprise but is any server based application. You shouldn't be running into this if you are creating a client based application. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[woliveri]

Ken,
I'm access sql server from a client for the db info but at any rate, cleaning up the references after use should resolve this problem. I don't have any issues with other desktop applications. Only this dll situation. Any ideas why?


thanks,

bill

 

[kenhamady]

The issues is where the DLL (and the reporting engine that it is using) is installed. Is it running on each client PC or is it running from a central server? Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[woliveri]

This "application" dll will reside on the server. Let me give you a more complete picture.

I've created a windows service which calls the vb6 dll for faxback functionality.

So the line of events are:

1. A file gets deposited in a folder with fax information.

2. The windows service opens the file and gets the fax info.

3. The windows service then calls the vb6 dll and passes the info

4. The vb6 dll opens a report in memory and saves it to disk in rtf format.

5. The vb6 dll uses Windows 2000 fax services to pick up the rtf document and fax it.



So the entire app will reside on the Server to answer your question.

Right now I'm in development so the entire app resides on my development machine Windows 2000 Pro.

 

[HowardHammerman]

One solution is to queue report requests to run when a license is available. The Reportal product does this for you. Howard Hammerman,

Crystal Reports training, consulting, books, training material, software, and support. Scheduled training in 8 cities.
howard@hammerman.com

http://www.hammerman.com

800-783-2269

 

[woliveri]

Howard,
Shouldn't I be releasing the license problem when I clean up references? I don't understand this. When I kill a CR app the license remains???

 

[kenhamady]

You are in an unusual area, because you are using the RDC to create a server based app that is not web based or CE based. There isn't much documentation about this. The CR license is clear that any server based application is limited to 5 CALs. But the only clear documentation on managing/releasing licenses is for ASP coding. I am not sure where your CALs are being managed.

As a side note, the CR license doesn't allow you to distribute server-based applications using the runtime software. Runtime can only be used for client based apps. If you were planning on distributing this dll you might want to read the license again. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[HowardHammerman]

Ken is right. For everyone's information here is part of the license:

2.8 "Report" means any work or document created using a Crystal software product, regardless of resulting file
format.
2.9 "Report Distribution System" means any process or system or combination of processes or systems that is
or are used to automatically and/or regularly deliver, share or distribute Reports, without providing any
Access to a Server/Web-based Application: (a) to greater than fifty (50) end users directly, or (b) to a
location that is accessible to greater than fifty (50) end users, who are reasonably likely to view or use the
Reports. A Report Distribution System shall not include: (a) distribution of Reports in hard copy form; (b)
manual distribution on a one-time or ad hoc basis; or (c) distribution of Client Applications created using
the Royalty Free Runtime Software. For purposes of calculating the number of end users, you do not need
to include any end user who otherwise has a valid license to use the Software or any of Crystal’s other
products (other than any product offered free of charge).

----
5 DISTRIBUTION OF RUNTIME SOFTWARE.
5.1. Client Applications. Client Applications may use Royalty Free Runtime Software and/or Royalty
Required Runtime Software.
5.1.1. Royalty Free Runtime Software Distribution License. Unless this is a "Not for Resale" or
"Evaluation" copy, Crystal grants you a personal, nonexclusive, limited license to reproduce and
Distribute Client Applications that use or include the Royalty Free Runtime Software to and only to
end users of the Royalty Free Runtime Software, if and only if you comply with all of the terms of
this Section and this license agreement:
5.1.1.1 You Distribute copies of Royalty Free Runtime Software solely as a part of
specific-purpose application programs written using an authorized copy of the
Software;
5.1.1.2 You remain solely responsible for support, service, upgrades, and technical or other
assistance, required or requested by anyone receiving such Royalty Free Runtime
Software copies or sample applications;
5.1.1.3 You do not use the name, logo, or trademark of Crystal, or the Software, without
written permission from Crystal;
5.1.1.4 You do not alter, disassemble, decompile, translate, adapt or reverse-engineer the
Royalty Free Runtime Software;
5.1.1.5 You do not alter, disassemble, decompile, translate, adapt, reverse-engineer, or
convert the report file (.RPT) format to an alternative format, including but not limited
to report file formats of general purpose report writer or database querying products
that are not property of Crystal, except as intended by the Software, without written
permission from Crystal; and
5.1.1.6 You will defend, indemnify and hold Crystal harmless against any claims or liabilities
arising out of the use, reproduction or Distribution of Royalty Free Runtime Software.
5.1.2. Royalty Required Runtime Software Distribution License. This Crystal Reports 8.5 Developer
License agreement does not in itself give you any right to Distribute, or Deploy the Client
Applications that include or use; the Royalty Required Runtime Software to end users who have
not already acquired the appropriate number of licenses of Crystal Reports from Crystal. To do so,
you must contact Crystal and acquire the Royalty Required Runtime Software Distribution License.
If you have previously received a Royalty Required Runtime Software Distribution License for a
prior version of the Software and are updating your Client Application with a new version of the
Royalty Required Runtime Software, you must acquire updated Royalty Required Runtime Software
Distribution Licenses for your upgraded Client Application from Crystal.
5.2. Server/Web-based Applications.
5.2.1 Deployment. You have the right to Deploy each Server/Web-based Application for Access by up
to, but not to exceed, 5 Concurrent Users. If you want to exceed the 5 Concurrent Users authorized
to Access each Server/Web-based Application, you just acquire additional Access Licenses as a
stand-alone offering. Under no circumstances may the 5 Concurrent Users you are authorized to
allow Access to each Server/Web-based Application be exceeded by combining additional Softwarelicenses, other Crystal products that include Access Licenses, promotional offers of any kind, or by
any other means, other than through the purchase of additional Access Licenses as stand-alone
offering.
5.2.2 Distribution. This license agreement does not in itself give you any right to Distribute
Server/Web-based Applications. For information on Distribution rights for Server/Web-based
Applications, please contact Crystal directly.
5.3. The Software may contain software components from Crystal's suppliers. This license agreement does
not grant you any right to distribute software components from these suppliers; including but not limited
to, Microsoft Corporation's "JET Files", unless you have obtained proper authorization from the
appropriate supplier.
6 COMPETITIVE PRODUCT RESTRICTIONS. You may not include the Software or sample applications in
any general-purpose report writing and/or database querying product, or any other product that is generally
competitive with Crystal product offerings; nor may you use Software to create a product that is generally
competitive with Crystal product offerings. If you wish to Distribute copies of Server/Web-based
Applications or sample applications on other terms, you must obtain written permission from Crystal.
=====
there is more, but I think these are the relevant parts.

Howard Hammerman,

Crystal Reports training, consulting, books, training material, software, and support. Scheduled training in 8 cities.
howard@hammerman.com

http://www.hammerman.com

800-783-2269

 

[woliveri]

Thanks Ken and Howard. I am not going to distribute this app. This is a in house app running on one server.

Anyway, I think I may have found two possible solutions to my problem. As I mentioned I'm using a Windows Service to call this dll and this Windows Service is created in VB.Net. I noticed that when I included a reference to my VB6 dll it also brought in references to ADODB object and the CRAXDRT object. So this may be part of the problem. I removed them and left only the reference to the VB6 dll. My thinking is the reference in the Windows Service is causing the problem. Still need to test this.

Also, In a Crystal Doc I found on the Web (Managing RDC Licences within your ASP Applications) there is some instruction on setting the ASP Timeout. Since this is not a Web Server and since I'm not using Web functionality I set this timeout to 60 seconds. I am now not getting the error on the concurrent licenses. However, since this is a development machine I really need to up this again.

I now need to roll back this setting to test the reference theory.