This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Corrupted VPD registry database | ||
---|---|---|---|
Product: | installer | Reporter: | puce <puce> |
Component: | Code | Assignee: | mslama <mslama> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
java -Dis.debug=1 -jar setup.jar > bugs\log.txt
Error Screenshot 1 Error Screenshot 2 Error Screenshot 3 C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common after reinstall Installation after deleting the files under C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common |
Description
puce
2006-01-20 18:18:15 UTC
Created attachment 28497 [details]
java -Dis.debug=1 -jar setup.jar > bugs\log.txt
Created attachment 28498 [details]
Error Screenshot 1
Created attachment 28499 [details]
Error Screenshot 2
Created attachment 28500 [details]
Error Screenshot 3
This looks like corrupted VPD registry (database used by InstallShield to store info about installed components). Workaround is to clean directory C:\Program Files\Common Files\InstallShield\Universal\common. Please first zip its content and attach resulting file here. This problem was already reported but we have no idea what causes this. No response from reporter. It looks like dupl of issue #67530. Please let me know if workaround helps. Created attachment 28550 [details]
C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common
After deleting C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common (Windows XP (German)), I don't get those the error screens anymore, but the only thing that happens is that the C:\Programme\netbeans-5.0rc2 directory gets created. The progress bar of the installer stays at 0% for some seconds and then switches to the "successfully installed" screen. The C:\Programme\netbeans-5.0rc2 directory is empty! Created attachment 28552 [details]
C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common after reinstall
Please check MD5 chceksum of installer to make sure it is not corrupted. For RC2 Windows installer MD5 checksum is 48f0171e98f18701fc800cb557fcd21b. If it is correct please try again command: java -Dis.debug=1 -Dtemp.dir=<Path to tmp dir> setup.jar if you get more info. I checked the MD5 checksum and it is the same. However, I found the solution. After deleting the files under C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common I get the effect described before. But when I rerun the installer afterwards without deleting those files (a directory "Gen1" was created), everthing works fine. The same is true for the extracted version. I will create an attachment for the case when it fails, so maybe you can improve the installer a bit. Thanks for your help! Created attachment 28608 [details]
Installation after deleting the files under C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common
There is: ServiceException: (error code = -30008; message = "Die Vertrauensstellung zwischen dieser Arbeitsstation und der primären Domäne konnte nicht hergestellt werden. It seems it is network problem. It was already reported but I cannot find previous report. Unfortunately it is InstallShield behavior and I cannot fix it anyhow. I would say (also from previous report) that your machine is member of some domain or group but it is not available currently (maybe unplugged network cable?). I am sorry I do not have any solution/workaround for this problem. Are you logged as local user? What is network configuration? Is machine part of any domain? Is that domain available? I want to report it to InstallShield. My machine is part of a domain, which in fact is currently not available. However, as I said before, if you call the installer twice without deleting the InstallShield files between the two calls, the installation works! Ok. Thanks. Not ideal but at least some workaround without tweaking network configuration. *** This issue has been marked as a duplicate of 67530 *** |