Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

ERROR 1402!


2 replies to this topic

jforst

jforst
  • Full Members
  • 19 posts

Posted 09 June 2004 - 18:09

We are having multiple customers reporting an Error 1402 during installation of our product when trying to run actions RegisterClassInfoRegister or RegisterProgIdInfo. All Users have Administrator Rights on their Systems. This error has just recently been noted on at least the current version and 3 prior versions of our product that has been working up to now. It occurs on Windows XP Home and Professional so far.

I have included information from 3 different Install log files below. As you will notice they all happen in this same area but some get farther than others.

********* Dev Studio v8.0

Action 18:26:48: RegisterClassInfo. Registering class servers
RegisterClassInfo: Class ID: {43668E21-2636-11D1-A1CE-0080C88593A5}
RegisterClassInfo: Class ID: {B5C45061-2729-11D1-A1D7-0080C88593A5}
RegisterClassInfo: Class ID: {202D3AEF-2F0E-11D1-A1F6-0080C88593A5}
Action 18:26:48: RegisterProgIdInfo. Registering program identifiers
RegisterProgIdInfo: ProgID: DfrgSnapin.DfrgSnapin.1
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1402.Could not open key: UNKNOWN\DfrgSnapin.DfrgSnapin.1\CLSID. System error 5. Verify that you have sufficient access to that key, or contact your support personnel.
Action ended 18:26:50: InstallFinalize. Return value 3.

********* Dev Studio v9.01

MSI (s) (90:EC): Executing op: ActionStart(Name=RegisterClassInfo,Description=Registering class servers,Template=Class ID: )
Action 7:38:18: RegisterClassInfo. Registering class servers
MSI (s) (90:EC): Executing op: RegClassInfoRegister(Feature=Diskeeper,Component={F8295318-F426-49E7-8330-18AD797D2098},FileName=C:\Program Files\Executive Software\Diskeeper\DfrgSnap.dll,ClsId={43668E21-2636-11D1-A1CE-0080C88593A5},ProgId=DfrgSnapin.DfrgS
napin.1,VIProgId=DfrgSnapin.DfrgSnapin,Description=DfrgSnapin Class,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {43668E21-2636-11D1-A1CE-0080C88593A5}
MSI (s) (90:EC): Executing op: RegClassInfoRegister(Feature=Diskeeper,Component={F8295318-F426-49E7-8330-18AD797D2098},FileName=C:\Program Files\Executive Software\Diskeeper\DfrgSnap.dll,ClsId={B5C45061-2729-11D1-A1D7-0080C88593A5},ProgId=DfrgSnapinAbout.
1,,Description=This is the snapin created on 10/30,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {B5C45061-2729-11D1-A1D7-0080C88593A5}
MSI (s) (90:EC): Note: 1: 1402 2: UNKNOWN\CLSID\{B5C45061-2729-11D1-A1D7-0080C88593A5}\InprocServer32 3: 5
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1402.Could not open key: UNKNOWN\CLSID\{B5C45061-2729-11D1-A1D7-0080C88593A5}\InprocServer32. System error 5. Verify that you have sufficient access to that key, or contact your support personnel.
MSI (s) (90:EC): Product: Diskeeper Home Edition -- Error 1402.Could not open key: UNKNOWN\CLSID\{B5C45061-2729-11D1-A1D7-0080C88593A5}\InprocServer32. System error 5. Verify that you have sufficient access to that key, or contact your support personnel
.

Action ended 7:38:28: InstallFinalize. Return value 3.

******** Dev Studio 9.01

MSI (s) (2C:20): Executing op: ActionStart(Name=RegisterClassInfo,Description=Registering class servers,Template=Class ID: )
Action 11:50:36: RegisterClassInfo. Registering class servers
MSI (s) (2C:20): Executing op: RegClassInfoRegister(Feature=Diskeeper,Component={F8295318-F426-49E7-8330-18AD797D2098}
RegisterClassInfo: Class ID: {43668E21-2636-11D1-A1CE-0080C88593A5}
MSI (s) (2C:20): Executing op: RegClassInfoRegister(Feature=Diskeeper,Component={F8295318-F426-49E7-8330-18AD797D2098}
RegisterClassInfo: Class ID: {B5C45061-2729-11D1-A1D7-0080C88593A5}
MSI (s) (2C:20): Executing op: RegClassInfoRegister(Feature=Diskeeper,Component={A276C558-38FD-44BC-805F-64FEC5322F78}
RegisterClassInfo: Class ID: {202D3AEF-2F0E-11D1-A1F6-0080C88593A5}
MSI (s) (2C:20): Executing op: ActionStart(Name=RegisterProgIdInfo,Description=Registering program identifiers,Template=ProgID: )
Action 11:50:36: RegisterProgIdInfo. Registering program identifiers
MSI (s) (2C:20): Executing op: RegProgIdInfoRegister(ProgId=DfrgSnapin.DfrgSnapin.1,ClsId={43668E21-2636-11D1-A1CE-0080C88593A5},,Description=DfrgSnapin Class,,,VIProgId=DfrgSnapin.DfrgSnapin,VIProgIdDescription=DfrgSnapin Class,)
RegisterProgIdInfo: ProgID: DfrgSnapin.DfrgSnapin.1
MSI (s) (2C:20): Note: 1: 1402 2: UNKNOWN\DfrgSnapin.DfrgSnapin.1\CLSID 3: 5
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1402.Could not open key: UNKNOWN\DfrgSnapin.DfrgSnapin.1\CLSID. System error 5. Verify that you have sufficient access to that key, or contact your support personnel.
MSI (s) (2C:20): Product: Diskeeper Professional Edition -- Error 1402.Could not open key: UNKNOWN\DfrgSnapin.DfrgSnapin.1\CLSID. System error 5. Verify that you have sufficient access to that key, or contact your support personnel.

Action ended 11:50:53: InstallFinalize. Return value 3.


Glytzhkof

Glytzhkof
  • Moderators
  • 1,447 posts

Posted 10 June 2004 - 04:00

Weird! The first thing I would do would be to verify the permissions on the registry keys and verify that SYSTEM and the user installing the software has write access:

1. Start : Run...
2. Type "regedt32". This is NOT the same app as regedit.exe
3. Go to Bring the HKEY_LOCAL_MACHINE window to front
4. Browse to HKLM\DfrgSnapin.DfrgSnapin.1\
5. Go to Security> Permissions...
6. Add SYSTEM and Everyone with write access (adding EVERYONE is the "hammer approach", but just for testing...)

Regards
-Stein Åsmul

gibilix

gibilix
  • Members
  • 1 posts

Posted 02 June 2006 - 10:16

I was having exactly the same problem but with a different product (Symantec AV Corporate Edition 10.1) and I found out that the administrative installation point I was creating was faulty because Windows INstaller on the machine I was using to create it had problems.

I have recreated the installation point from a different computer and that solved the problem.

I hope this can help you.