This article will walk you through the troubleshooting steps that you should take when you are trying to diagnose problematic behavior with your JFile application.

Taking these steps may not only help you determine the origin of the problem on your own, but will also make you better prepared for submitting a support incident, should you require further assistance diagnosing the problem.

1. Differentiate between client-side and server-side problems.
   When using JFile to send your HTTP Request, the HTTP Response is returned to JFile, instead of the directly to the browser. JFile returns its own error codes, such as General_Send_Error when there are errors on the server. To see the error generated from the server directly, take JFile out the picture and try submitting your Request to the same processing page using just an HTML form. If you are posting to a FileUp script on the server, you can find sample scripts for HTML forms in the FileUp samples folder. If you receive an error from FileUp on the server, enter the error code in the SoftArtisans Knowledge Base for information on how to resolve the error. If you do not receive an error server-side, continue troubleshooting JFile directly.
   
   
2. Determine if the behavior is related to the JVM vendor or version:
   
   
   • Determine which vendor's JVM you are running in your browser.
     
     Netscape for Windows: Netscape uses the Sun JVM.
     
     Internet Explorer for Windows: IE can be configured to use either the Sun JVM or the Microsoft VM. To determine which JVM you are using, go to Tools...Internet Options...Advanced. If you have "Use Java [version number] for <applet> (requires restart)" checked, then you are using the Sun JVM. If this is not checked, you are using the Microsoft VM.
     
     Internet Explorer for Macintosh: Current versions use the Macintosh Run Time for Java from Sun. For a history of previous versions, please see the Microsoft Knowledge Base article on Internet Explorer VM compatibility: http://support.microsoft.com/default.aspx?scid=kb;en-us;q214828
     
     
   • Test to see if the behavior changes across JVMs and across browsers.
     
     
   • Consider upgrading your JVM, if applicable. The Microsoft and Sun JVMs will output their version number to the java console. To enable the java console, see the instructions below. If you choose to upgrade your JVM, you should also follow the instructions below for upgrading JFile, as later versions of JFile provide support for the later versions of the JVMs.
     
     
   • Need to download a different JVM?
     To download the Sun JVM, get the Java Plug-In from Sun's download site. The Microsoft VM is no longer being distributed from the Microsoft Website due to a court settlement with Sun, but Microsoft will continue to support their VM until 2007.
     
     
   • Branching your code based on the JVM vendor or version: You may decide to branch your code based on JVM vendor or version. KB article 839 explains how to write an applet that can return this information to your scripting environment.
     
     
3. Configure the browser and JFile for debug string output to the java console.
   
   
   • Enable the java console:
     
     In Netscape for Windows:
     The ability to log to the java console is automatically enabled.
     
     In Internet Explorer for Windows with the Sun JVM:
     The ability to log to the java console is automatically enabled.
     
     In Internet Explorer for Windows with the Microsoft VM:
     Go to Tools...Options...Advanced. Locate the "Microsoft VM" header and check "Java Console Enabled (requires restart)" and also check "Java Logging Enabled". Click "OK" to close the dialog and close all instances of the browser. These changes will take effect when a new browser instance is opened.
     
     In Internet Explorer for Macintosh:
     Go to Explorer...Preferences. In the resulting window, choose Web Browser...Java...Java Options. Then ensure that "Enable Java", "Log Java Output" and "Log Java Exceptions" are checked.
     
     
   • Enable JFile's DebugInfo parameter:
     
     Tell JFile to send debug strings to the java console by adding the DebugInfo parameter to the JFile object tag. Set the value to "1" to enable debug string output. <param name="DebugInformation" value="1">
     
     
   • Open the Console when you run your application in the browser, so that you can see the output:
     
     In Netscape for Windows:
     Tools...Web Development...Java Console
     
     In Internet Explorer for Windows with the Sun JVM:
     Tools...Sun Java Console
     
     In Internet Explorer for Windows with the Microsoft VM:
     View...Java Console
     
     In Internet Explorer for Macintosh with the MRJ:
     View...Java Messages
     
     
4. Determine the version of JFile that is running.
   
   
   • In any version of JFile, the version property can be used to determine the current version of JFile: http://support.softartisans.com/docs/JFile/prog_ref_upclient_version.htm
     
     
   • Version 3 and higher of JFile will also output it's version number to the java console.
   
   
   After determining the version of JFile, check the Version Differences page on the support website. Check to see if your issue has already been addressed, and if upgrading is appropriate. After upgrading, be sure to clear your browser cache.
   
   

If you are unable to determine the cause of the behavior after gathering this information and using our self-help resources such as the Knowledge Base and Version Differences page, please visit our support site and send the above mentioned information(java console output in text format, version info, etc.) as well as a description of the behavior to technical services for assistance.