ASE Home Page Products Download Purchase Support About ASE
ChartDirector General
Forum HomeForum Home   SearchSearch

Message ListMessage List     Post MessagePost Message

  ChartDirector Unregistored.
Posted by Bhanu on May-28-2012 20:07
We have purchased ChartDirectory and we have chartdir.lic file.
We are using weblogic application server.
In our application below every chart we are getting "chartdirector unregistered from www.advsofteng.com" in yellow color.

Here I am sending my BootLog.

Cannot load license file chartdir.lic - java.io.FileNotFoundException: chartdir.lic (The system cannot find the file specified)
Updated license check at 2012-05-28 17:24:46> Cannot load license file chartdir.lic - java.io.FileNotFoundException: chartdir.lic (The system cannot find the file spec
ified)
Aug-09-1996

Thanks and Regards,
Bhanu Chandar Rao A

  Re: ChartDirector Unregistored.
Posted by Peter Kwan on May-29-2012 01:39
Hi Bhanu,

If cdinfo.jsp shows that the error is "The system cannot find the file specified.", I means the license file "chartdir.lic" is not in the Java class path of the system. The two common reasons are:

(a) The file "chartdir.lic" is really not in the Java class path of the system.

For a JSP web application, there should be a path "WEB-INF/classes" for the web application, which is always in the Java class path of your application. We suggest to put the "chartdir.lic" in the "WEB-INF/classes" directory of your web application.

Note that on some JSP web servers, you may need to restart the web application so that the JSP system can pick up the new files in the Java class path. (You should only need to restart the web application, not the JSP web server.)

(b) The file is in the Java class path, but is not called "chartdir.lic". If the file is created using Windows Notepad, the Notepad may automatically append ".txt" to the file name, so that it becomes "chartdir.lic.txt". In the Windows File Explorer, you may see the file as "chartdir.lic" because the Windows File Explorer will "hide known file extensions" by default. To confirm if your file is really called "chartdir.lic", if you are on Windows, please right click on the file, and select Properties. It should show the true and full file name.

Also, note that the file should be called "chartdir.lic", not "Chartdir.lic" or "CHARTDIR.LIC". Although the Windows file system is not case sensitive, Java is itself case sensitive, and it may or may not load the file if the case is incorrect.


Note that the path WEB-INF/classes it a path of your "web application", not a path of the JSP web server or Java VM. (A JSP web server can host multiple web applications, each has its own Java class path. As per the JSP standard, the "WEB-INF/classes" of a web application is always in the Java class path of that application.)


Apart from WEB-INF/classes, Java treats JAR files in many of the directories as being in the Java class path. So you can put "chartdir.lic" in a JAR file (just zip it, and rename it to "xxx.jar" - the filename is not important), and put it the JAR file directories recognized by Java. An example is "WEB-INF/lib" of the web application. In many Java VM, the "jre/lib/ext" directory may also work. Note that if you put the license file in the Java VM system directory like "jre/lib/ext", you may need to restart the entire Java application (that is, the entire JSP web server), rather than just the web application.


Note that for WebLogic servers, in the past (at the time of Java 1.4) we have seen several cases that the server cannot read text file resources correctly if it contains an odd number of bytes. In particular, the last character is not read if the text file contains an odd number of bytes. The ChartDirector license happens to be 29 characters, which is an odd number. If this is the cause of the problem, the error message should be said the license "checksum" not match. To solve the problem, please add some empty space or a new line at the end of the license. (We have not seen similar problems for many years, so I assume this problem has been solved in the updated WebLogic server or IBM Java, but we mention this just in case.)


Please kindly let me know if the above can solve the problem.

Regards
Peter Kwan