I'm unfortunately still getting this message. Does the process generate a log i can check to see where there might be an issue?
i did fresh uninstall/reinstall this morning. made sure a/v exception was listed. closed down all my background processes. there have been no other changes to the pc im using since before i installed viewer and configured the first MSI package (the one that worked) all other attempts have had told me the incorrect code when i try add the connection.
I even tried generating it on a different PC that only has windows installed on it then importing that key
Edited:albert schroter - Feb 09, 2018 1:39:26 pm EST
Code import has only worked for the first MSI i configured on the same machine. I've played with the configurator to test various options. ive tried deleting the old key.dat before generating a new one, but every new MSI i've configured is giving me this same error when i try to add by code. the knowledge DB only address importing to other machines. is there a registry entry i need to blank out when generating a new configuration?