P3
FULL PRODUCT VERSION :
Unfortunatly it is impossible to perform java -version due to this bug.
ADDITIONAL OS VERSION INFORMATION :
Windows 7 Home Premium 64 bit
EXTRA RELEVANT SYSTEM CONFIGURATION :
Using jdk-6u19-windows-x64.exe (70.480.664 bytes)
A DESCRIPTION OF THE PROBLEM :
I removed JDK 6u17 then attempted to install JDK 6u19. The result was Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.
I suspect this is a MSI problem and not a problem with the JDK. The reason I have this problem is because in order to prevent multiple JDK installs to show up in the installed software list (which there aren't really, they all are installed to the same directory) I delete the older installs prior to installing new versions.
On my windows xp 32 bit machine the routine described above still works.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Currently no workaround although I suspect that using http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 would help if the problem does lie with MSI.
Unfortunatly it is impossible to perform java -version due to this bug.
ADDITIONAL OS VERSION INFORMATION :
Windows 7 Home Premium 64 bit
EXTRA RELEVANT SYSTEM CONFIGURATION :
Using jdk-6u19-windows-x64.exe (70.480.664 bytes)
A DESCRIPTION OF THE PROBLEM :
I removed JDK 6u17 then attempted to install JDK 6u19. The result was Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.
I suspect this is a MSI problem and not a problem with the JDK. The reason I have this problem is because in order to prevent multiple JDK installs to show up in the installed software list (which there aren't really, they all are installed to the same directory) I delete the older installs prior to installing new versions.
On my windows xp 32 bit machine the routine described above still works.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Currently no workaround although I suspect that using http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 would help if the problem does lie with MSI.