In this situation, even though the retail (non-expiring) version of JFile has been added to the webserver, an evaluation version of JFile is still either in place on the webserver or cached on the client with which you are testing. Here is a list of steps that can be taken to assure that the server and client are upgraded successfully.

1. Locate, with certainty, the retail version of the JFile jar and cab files. If you are uncertain whether your JFile jar and cab files are evaluation versions or retail versions, you can always log on to our website and re-download a copy of the retail version. Place your retail JFile files someplace safe - as the next step involves locating and deleting all other copies of the file.
   
   
2. Now that you know where the retail version of the JFile jars and cab file are located, search your webserver for all other instaces of these files, and delete them : "filetransfer.jar", "filetransfer.cab", "Mac_filetransfer.jar".
   
   
3. Move your retail version of JFile into the directories where they are needed. These directories must match the paths specified in your <APPLET> tag's codebase attribute.
   
   
4. Now, test your web application. If any users still receive expiration messages, ask these users to clear their browser cache. One of a few things may happen:
   
   
   • The upload will succeed.
     The retail version of JFile will download when your web page is rendered and all subsequent uploads will succeed.
     
     
   • JFile will fail to load in the browser.
     This may be because there is a "codebase" path pointing to the evaluation version of JFile that has just been deleted from the webserver. Check the codebase attribute of the <APPLET> tag and change it to point to the location of the retail version of JFile.
     
     
   • The client will still receive an expiration message.
     This should be a rare case and involves unexpected behavior with client-side caching. Clear the browser cache again , close all browser instances and search the client's file system for "filetransfer.jar", "filetransfer.cab", "Mac_filetransfer.jar". If any of these files are located, please delete them. Restart the browser and repeat step 4.