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.

Bug 71679 - Corrupted VPD registry database
Summary: Corrupted VPD registry database
Status: RESOLVED DUPLICATE of bug 67530
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-20 18:18 UTC by puce
Modified: 2006-10-23 16:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
java -Dis.debug=1 -jar setup.jar > bugs\log.txt (39.24 KB, text/plain)
2006-01-20 18:20 UTC, puce
Details
Error Screenshot 1 (32.84 KB, image/jpeg)
2006-01-20 18:22 UTC, puce
Details
Error Screenshot 2 (36.23 KB, image/jpeg)
2006-01-20 18:23 UTC, puce
Details
Error Screenshot 3 (31.52 KB, image/jpeg)
2006-01-20 18:23 UTC, puce
Details
C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common (1.01 MB, application/x-compressed)
2006-01-23 14:42 UTC, puce
Details
C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common after reinstall (2.26 KB, application/x-compressed)
2006-01-23 14:54 UTC, puce
Details
Installation after deleting the files under C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common (15.70 KB, text/plain)
2006-01-26 13:40 UTC, puce
Details

Note You need to log in before you can comment on or make changes to this bug.
Description puce 2006-01-20 18:18:15 UTC
Hi,
I need to reinstall the IDE (I tried several installers starting from NetBeans
IDE 5.0 beta + Application Server 8.1 Bundle Installer up to RC2). Unfortunatly,
I have no entry in the the windows software panel to uninstall the IDE first
(maybe due to a crash at the very end of the installation). When I run the
"_uninst\uninstaller.exe" I get an error from InstallShield "no UUID for given
product". The installer doesn't allow to install over the same directory and
when I install it to a new directory I get the errors shown in the attachments.
The last screenshot appears right after choosing the jdk version.

java -version:
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

I asked the mailing list and was told to file an issue.

Any help appreciated.

-Puce
Comment 1 puce 2006-01-20 18:20:25 UTC
Created attachment 28497 [details]
java -Dis.debug=1 -jar setup.jar > bugs\log.txt
Comment 2 puce 2006-01-20 18:22:45 UTC
Created attachment 28498 [details]
Error Screenshot 1
Comment 3 puce 2006-01-20 18:23:02 UTC
Created attachment 28499 [details]
Error Screenshot 2
Comment 4 puce 2006-01-20 18:23:21 UTC
Created attachment 28500 [details]
Error Screenshot 3
Comment 5 mslama 2006-01-20 18:51:20 UTC
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.
Comment 6 mslama 2006-01-23 14:19:05 UTC
No response from reporter. It looks like dupl of issue #67530. Please let me
know if workaround helps.
Comment 7 puce 2006-01-23 14:42:01 UTC
Created attachment 28550 [details]
C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common
Comment 8 puce 2006-01-23 14:53:15 UTC
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!
Comment 9 puce 2006-01-23 14:54:08 UTC
Created attachment 28552 [details]
C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common after reinstall
Comment 10 mslama 2006-01-23 15:27:59 UTC
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.
Comment 11 puce 2006-01-26 13:38:57 UTC
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!
Comment 12 puce 2006-01-26 13:40:33 UTC
Created attachment 28608 [details]
Installation after deleting the files under C:\Programme\Gemeinsame Dateien\InstallShield\Universal\common
Comment 13 mslama 2006-01-26 14:18:27 UTC
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.
Comment 14 mslama 2006-01-26 14:25:16 UTC
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.
Comment 15 puce 2006-01-26 17:25:27 UTC
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!
Comment 16 mslama 2006-01-26 18:15:52 UTC
Ok. Thanks. Not ideal but at least some workaround without tweaking network
configuration.

*** This issue has been marked as a duplicate of 67530 ***