I got this too. It turned out to be a problem with the TMP environment variable; I had set it to point to a non-writeable drive (the CD drive, as it happens). As soon as I set it to the right directory, the JDK installed OK (though I had an unrelated error near the end of installation).
I thought the days of these unhelpful messages were behind us. If Installshield or the JDK setup program can't use the TMP directory, why not say so?
I met the same problem under Win2K SP4. The cause were insufficient DCOM
acess permissions. After setting the default access permissions for DCOM
with "dcomcnfg.exe" ( in the "Default Security" tab) the installer runs
without errors. See also
http://consumer.installshield.com/kb.asp?id=Q108324Det var hvad jeg fandt -håber du kan bruge det