I've been trying RealSecure 6.5 WGM on Windows XP (pre-SP1). For the most
part it appeared to be working and worked for a week or two.
This WGM is managing several network sensors running on Nokia (RS NS 6.5).

It wasn't until last week I tried to add another domain user to the same
workstation that I ran into problems. 
The user was part of the local admin group. I was hoping that I could start
up WGM after logging that user in and by magic an enryption key pair would
be generated. No such luck. Then I thought back to the old days when we
could start up a new install on a box where it was already running, and
bring
up some sort of maintenance window. That didn't happen. I was prompted for
confirmation on uninstall. Not knowing any other option, I figured it would
keep my old key (as well as my backup in another directory) and I could
uninstall/re-install and have the new keys generated for me. After doing
this I could no longer use the original ID. In addition to the "CerticomNRA"
and "RSA" directories under the "RealSecure 6.5 Console\Keys" directory, I
had a new one called "P24". The additional ID did not create a key within
CerticomNRA. 

Here is the message when I try to use the WGM:

"
The export agreement file wkexport.rtf does not contain a valid digital
signature.  You cannot download upgrade or service release updates unless
the file has a valid signature.  Reinstall the RealSecure console to replace
the export agreement file with the correct file.
"
I rebooted the PC, same thing.

So I went into add/remove programs and removed the WGM.
It seemed to work.

I went into regedit and saw the ISS registry keys were still there. But I
couldn't open most of them. Which meant I also couldn't delete them.
I rebooted the PC again, in case something, somehow, was locked. There
wasn't anything different.

I then tried to reinstall again anyway. Now I get the following error
message:

"
An error was encountered while populating the RealSecure Console registry
hivel. Setup will now abort.
"

I will now try the XP system restore feature to see if I can go back in time
and start over from there, but this is my last hope before reloading the
PC's OS.

Has anyone else seen this? If so, was there any workarounds?
Support told me about being able to upgrade the console to 6.6 without
having to manage a 7.0 network sensor, so I may try that and then use the
createkey utility.



Reply via email to