MD5 error occurs when downloading the Host On-Demand cached client

Resolving The Problem

A file size of '0' indicates a problem on the server. Any other file size discrepancy can be caused by several circumstances.

To debug the problem, complete the following checklist:

1. Enter the number 5 in the Java console, which shows the Java™ plug-in debug information. Start the cached client download. You can see which files the Java plug-in is trying to load and the location from which it is trying to pull the files.
2. Manually remove all remnants of the cached client. Look for the HODCC directory and any files named *.ccr*. Delete them if found.
3. Clear the Internet Explorer browser cache (Tools > Internet Options > Temporary Internet Files > Delete Files). Make sure you select 'Delete all off-line content' under Temporary Internet Files.
   For Firefox, select Tools > Options > Advanced > Network > Offline Storage > Clear Now.
4. Clear the Java 2 plug-in cache (Start > Settings > Control Panel > Java Control Panel > Temporary Internet Files > Delete Files).
   
   If none of the previous steps above resolve the problem, consider these:
   
5. Remove the plug-in completely through Add/Remove Programs.
6. Delete anything in c:\Documents and Settings\[myuserid]\ that starts with .j*, for example, .jpi_cache.
7. Delete C:\Documents and Settings\[myuserid]\UserData\SUN\java if it exists.
8. Reinstall the plug-in. Make sure you have a clean browser cache before attempting to download the cached client again.

• Incomplete download most likely from a time-out problem. In this case, increase the PersistTimeout value in your HTTP server from the default of 1 minute to a higher value, such as 5 minutes. Or you can set your PersistTimeout to a value of '0' and the OutputTimeout to a value of 1 hour.
  
• When you try to install the Java 1 cached client from a Host On-Demand V10 server that has been updated with a fix pack using the AparUpdater utility.
• To correct this problem, download the full version of Host On-Demand and install it instead of using the fix packs. This issue is being addressed as a code defect; however, a fix has not been created.

• If you have just installed a refresh pack, for example 8.03c, and your users are getting an MD5 error when installing the cached client or Web Start client, and you are also getting a second pop-up message about the size of a file being incorrect. For example, the length of sccbase2.jar is 887790 - should be 890201, then you need to check the patch.log file that is generated as part of the AparUpdate (ibmaparupdater) utility.
  
• Search for any "Panic" messages.
  For example, "Panic!! - could not regenerate zip file .ulnewsccbase2.jar."
  
  To correct this problem you need to run the ibmaparupdater utility again. Be sure that the web server is stopped, that the deployment is not running, and that all service manager functions are stopped prior to starting the ibmaparupdater utility. Then, start the ibmaparupdater utility and restore the previous installation followed by an Apply APAR.
  
• You have multiple Java 2 plug-ins installed. With later versions of the Java 2 plug-in and with Host On-Demand this is not a problem, but you still may have a corrupted Java 2 plug-in installation. You might need to remove all of them. In that case follow steps 5-8 above.