Error: 'Client submitted invalid key'
This error comes up when ASGS cannot access your hardware, or you are trying to run Allegiance within a Virtual Machine. It is usually encountered on a machine that cannot access the harddrive's SMART information.
Virtual Machines
Allegiance does not run within any VM. Products such as VMWare, Microsoft Virtual Machine, and Parallels Desktop are not supported by Allegiance. The only way around this is to boot into Microsoft Windows natively. This has been tested and confirmed to work with the latest intel-based Apple computers.
Enabling SMART
SMART must be enabled for each harddrive installed on your system. This is enabled by default on most systems, however sometimes it is not. You can usually enable this feature in your system's BIOS screen before Windows boots. For more information on this process, please consult the documentation for your motherboard or hard disk controller.
RAID Arrays
If you have a RAID array (striped or mirrored drives) you must enable SMART on each individual harddrive, as well as your RAID controller. You can usually configure this in your RAID controller's setup screen which is usually accessible before Windows boots. Some newer RAID controllers may support configuring this setting within Windows through a customized utility. For information on enabling SMART on your RAID controller, consult its documentation.
Workaround: the verifier tool
If you have a Silicon Image RAID controller, there is a workaround that has been confirmed to work on a few of their controllers.
Open up a command prompt (Start -> All Programs -> Accessories -> Command Prompt or Start -> Run -> cmd -> OK) and type in the following command:
verifier /flags 0x80 /driver scsiport.sys
Restart your computer after this command runs. ASGS should now be able to read SMART info from your RAID array (and so should any monitoring programs like SpeedFan). To disable this work around, type the following command at a command prompt:
verifier /reset
What the verifier command does is enable a monitor on the Silicon Image drive that monitors the DMA calls it makes.
Links : MSDN article on the command, and the one for the specific flag we are setting and the root article for the Driver Verifier.
Enabling the driver verifier somehow forces the SiL driver to properly transmit the SMART info. The downside to enabling this is that whenever your SiL driver does something bad with DMA, a BSoD will occur with bug check 0xE6 (DRIVER_VERIFIER_DMA_VIOLATION). This would be data corruption that otherwise will go unnoticed, so it may not be a bad thing after all. I am not aware of any performance difference with the verifier being enabled (other than the usual sub-par performance of SiL RAID compared to other solutions).
The solution has been tested to work on a SiL 3112A, 3114, 3512 and 0680A on Windows XP SP2. This solution DOES NOT work for Intel chipset RAID (a different driver file, but the chipset itself has broken SMART support). nVidia chipset based RAID reports SMART info correctly without any work arounds. Vista support is untested. However, the command does exist in the OS.
If all else fails...
- Make sure SMART is still enabled on each of your hard disks and RAID controllers. Adding/removing hardware components or updating system software can sometimes have an affect on these settings even if you've already enabled them. Double-check to make sure they haven't become disabled.
If you still receive this "Client submitted invalid key" error, Send a private message to Tigereye, the Community Administrator and he will validate your key as soon as he is able.
If you do not get a response within 2 days, post a new topic in the Helpline forum with the title "Client submitted invalid key" and your account will be validated as soon as an administrator is available.
