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 47236 - On startup after installing profiler get message:Profiler module installation is corrupted..
Summary: On startup after installing profiler get message:Profiler module installation...
Status: CLOSED DUPLICATE of bug 47168
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-16 01:43 UTC by ghbean
Modified: 2007-02-12 22:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
On startup after installing profiler get message:Profiler module installation is corrupted.. (99.79 KB, text/plain)
2004-08-16 01:51 UTC, ghbean
Details
Exceptions thrown (4.33 KB, patch)
2004-08-23 20:30 UTC, Maros Sandor
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description ghbean 2004-08-16 01:43:39 UTC
After apparantly sucessfuly installing proiler 
(profiler-m1-windows.nbm) got the corrupted 
module message after exception( see Aug 01:46:45 
EDT 2004 i attached IDE.log).  

When I tried to reinstall the manual update was 
not recognized  on the Update Center Wizard's 
Select Modules to Install Dialog.
Comment 1 ghbean 2004-08-16 01:51:07 UTC
Created attachment 16822 [details]
On startup after installing profiler get message:Profiler module installation is corrupted..
Comment 2 Maros Sandor 2004-08-23 20:29:31 UTC
I've got the same problem. Downloaded the module, installed it 
(globally) and when the updater finished, I was rewarded with the 
attached exception. Restarted netbeans, and the same exception was 
thrown again. Win2K, JDK 1.4.2_05, NB 3.6. Then I invoked the Attach 
and Profile action, memory profiling, and got the second exception. I 
was unable to use the profiler at all, raising to P2.
Comment 3 Maros Sandor 2004-08-23 20:30:25 UTC
Created attachment 17048 [details]
Exceptions thrown
Comment 4 iformanek 2004-09-01 12:20:28 UTC
Those problems are caused by the module being installed globally 
(thus duplicate of 47168 which captures the root cause).
Agreed with the problems of module uninstall/reinstall, will make it 
more bulletproof as well as easy in subsequent milestones.

*** This issue has been marked as a duplicate of 47168 ***
Comment 5 ehucka 2006-10-09 12:11:04 UTC
Verification of old issues.
Comment 6 Alexander Kouznetsov 2007-02-12 22:28:00 UTC
Closing old issues.
Comment 7 Alexander Kouznetsov 2007-02-12 22:28:10 UTC
Closing old issues.