Troubleshooting


1. Virtual Memory error in Windows.

Problem: This error can occur after extended use of the builder. It is due to known problems in some Java Virtual Machines, like those in the Navigator and compilers like the JDK.

Solution: Restart your browser or the JDK. Sometimes you may have to restart your machine. Increase the cache settings in the Navigator under Network Preferences. A good minimum for the Memory Cache is 4MB and the Disk Cache is 20MB.

2. Compile failed error.

Solution: Check the compile errors window in the Application Builder. If you are unsure of how to resolve the problem send the error to support@bulletproof.com..

3. Class Failed to Load.

Problem: Either a SQL failed or the class doesn't exist or some other error occurred when loading the class.

Solution. Send the Java console output to support@bulletproof.com and they will provide possible solutions..

4. Could not connect to JaggServer.

Problem: When you installed JDesignerPro, you may have set the wrong IP address or domain name of your server. Therefore JDesignerPro would be using the wrong IP to connect to JaggServer.

Solution: In the JDesignerPro directory, open JDesignerPro.ini. In the .ini file are one or more settings for your IP address or domain. Be sure those addresses match the IP address of your machine, as shown in the Networking Control panel, TCP/IP properties.

5. No suitable driver.

Problem: Either ODBC, ODBC system data sources, or the .dll drivers are not properly installed.

Solution: Be sure you have 32 bit ODBC 2.5 or later installed and you have your database setup as a System data source. Your data source must only be under System DSN, not under User Data Sources or this will confuse JDesignerPro.

6. Windows Dial-up networking is launched.

Problem: You may be seeing the dial-up networking application launched automatically by either your browser or by JaggServer when you start JaggServer. This is Windows’ normal response to a request for TCP/IP networking from an application.

Solution: You may press either Connect or Cancel on the Dial-up Networking application. You can run JDesignerPro through your browser locally and the JaggServer with or without the Dial-up connection. Both connecting and canceling will allow JaggServer to finish the start up process.

7. JaggServer will not run properly, or "Check that JaggServer is running"

Problem: In the Login window or in the set up screen, JDesignerPro states either that it cannot find JaggServer or that JaggServer has not been started.

Solution: In both cases, be sure JaggServer is running and the top line in JaggServer says "JaggServer running on port: XXXX" Where XXXX is the port number.

When you receive this message in the JDesignerPro login window, start JaggServer, press OK on the login window. The Login window will disappear. Simply restart JDesignerPro and JaggServer should now be available to JDesignerPro.

Also check that the path for the JaggServer target is correct. The target for JaggServer is found in the Properties of the JaggServer icon in the JDesignerPro program group. The Target field should look something like this:

C:\jdk\bin\java.exe -classpath .;C:\jdk\lib\classes.zip JaggServer

It is important that the root of the source directory be the same.

Note: There is a space between "java.exe" and "-classpath", then a period and semi-colon, ".;", then the path to the classes.zip files that are part of the JDK, then a space before "JaggServer".

8. A general slowness or screens not drawing properly.

Problem: Too small a cache setting.

Solution: Increase browser caches to 4000 for memory cache and 20000 for disk cache in Netscape Navigator / Communicator and increase the cache file in MS-Explorer.