"Internal Error 2721. Kill_Gatekeeper" when uninst

Forum for support for the PureSight for WinGate content filtering plugin

Moderator: Qbik Staff

"Internal Error 2721. Kill_Gatekeeper" when uninst

Postby Viki » Aug 03 04 12:42 pm

Previously I have fine working Wingate 5.2.3 + PureSight 1.1.
Next I have uninstalled Wingate, but whan I tried run puresight.msi the following message hass appeared:
"Internal Error 2721. Kill_Gatekeeper" both when I checked Repair or Uninstall fields :(
cleaning registry, reboots - nothing helps.
What should I do to (re)install PureSight again? Wingate runs ok.

TIA, Viki
Viki
 
Posts: 6
Joined: Aug 03 04 12:32 pm
Location: Poland

Postby Pascal » Aug 03 04 2:32 pm

Hmmm. We haven't seen that one before - try the same, but as the shortcut from the Start Menu under WinGate\Plugins.

If that fails, I'll have to dig around the registry to see where the installation instructions are stored.
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby Viki » Aug 04 04 10:29 am

1) I tried, that also fails :-(
2) MsiExec.exe /x {DDD22EC1-B973-46EE-A49C-CC32F41FEEB0} gives the same error message.

I'm waiting for your digging results...
Could you send me default registry keys for PureSight? Maybe some of them are missing, and therefore "Repair option" doesn't work?

Viki
ono@o2.pl
Viki
 
Posts: 6
Joined: Aug 03 04 12:32 pm
Location: Poland

Postby Pascal » Aug 04 04 11:41 am

The error message says:

"Custom action [2] not found in Binary table stream"

That sounds like it is a corrupted .MSI file for PureSight. The easiest way I can see is to force a re-install. To do that, you need to make the Windows Installer un-aware of the fact that the product is already installed.

What I'm going to be describing here is a fairly advanced editing of the registry - so please - make sure you have a GOOD backup, and as you're working through these steps please make an ADDITIONAL backup after each one (Or of each key you delete) so you can be sure things are restorable.

On Windows XP, the key to begin looking in is here.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\

You are looking for something called "Products" which will contain a series of keys which look like DDD22EC1-B973-46EE-A49C-CC32F41FEEB0. One of those will contain "DisplayName" with a value of "PureSight for WinGate".

The easiest way to find it is to open the key I specified above, then run a search for "PureSight for WinGate". When it has found a key - you want to delete it from that long number onwards.

For example, on my local machine it was in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\C2CB06AAA6308FA40AABBF255911F507\InstallProperties

To get it back to a state where I could install it, I had to delete

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\C2CB06AAA6308FA40AABBF255911F507

That should sort you out. Please, just remember the warning about editing the registry.
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby Viki » Aug 04 04 12:49 pm

I have already tried to do it before. After deleting a key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\1CE22DDD379BEE644AC9CC234FF1EE0B (with: value name "UninstallString" with value "MsiExec.exe /X{DDD22EC1-B973-46EE-A49C-CC32F41FEEB0}", and value name "LocalPackage" with value "C:\WINDOWS\Installer\269ae3.msi") the system generated another error message:
"Configuration data for this product are corrupted. Please contact the technical help personel." This is a translation, because it's a messages from Polish version of WindowsXP.
What next?
Viki
 
Posts: 6
Joined: Aug 03 04 12:32 pm
Location: Poland

Postby Pascal » Aug 04 04 12:51 pm

Hmm. That worked for me. Did you only delete the values or did you delete the entire registry key ?

(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\1CE22DDD379BEE644AC9CC234FF1EE0B)
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby Viki » Aug 04 04 7:59 pm

If I deleted the whole key or only the value "MsiExec.exe /X{DDD22EC1-B973-46EE-A49C-CC32F41FEEB0}", the result is the same.
Viki
 
Posts: 6
Joined: Aug 03 04 12:32 pm
Location: Poland

Postby Pascal » Aug 04 04 8:22 pm

I'll have to scour Microsoft's website then, see if they have any suggestions. I'll try again tomorrow - out of the office now - so to confirm:

The current situation is:

You have PureSight 1.1 installed in an indeterminite state.
You have WinGate 6.0 (???) installed.

Is that correct ?
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby Viki » Aug 04 04 9:04 pm

True, but Wingate 5.2.3.
Viki
 
Posts: 6
Joined: Aug 03 04 12:32 pm
Location: Poland

Fixed

Postby Viki » Aug 06 04 10:15 am

Ok, I have just fixed this problem.
I copied all files and PureSight-related registry keys from another computer. After that I removed PureSight successfully and then installed again :-)

thanks for help, Viki
Viki
 
Posts: 6
Joined: Aug 03 04 12:32 pm
Location: Poland


Return to PureSight for WinGate

Who is online

Users browsing this forum: No registered users and 11 guests

cron