There is a topic on the BSN about this error message (see copy below). Let us know if that worked for you.
We believe this to be a result of WMI misconfiguration in a user's
system. You can see if this is the case if your Windows is unable to see
your system's hardware components (ie. processor, RAM, etc). You can
verify if you are in this situation by doing the following:
WinXP:
1) Right click on My Computer and click on Properties
2)
Incorrect information will be displayed for your system's Processor and
potentially other hardware components in the bottom right
Win7/Vista
1) Go to the Control Panel
2) Click on System.
3) You should see something similar to this: http://i.imgur.com/HN86i.jpg
If
this is what you're seeing, your WMI configuration has been corrupted.
As a result, Windows is unable to determine your Processor and other
hardware components and therefore DA2 is unable to determine your
hardware components during activation.
To fix this, you will need to rebuild your WMI repository. I
want to stress that this fix is not for users who are not running as
Administrators. You must be logged in as an Administrator. In
addition, if you are at all uncomfortable with the process of touching
your system's WMI files, please wait for a more official fix.
WinXP:
Download the WMI Diagnosis Utility from Microsoft's site and execute the VBS script within. http://www.microsoft.com/downloads/en/details.aspx?FamilyID=D7BA3CD6-18D1-4D05-B11E-4C64192AE97D
Win7/Vista:
1) Open a Command Prompt (Windows Key + R, then enter 'cmd')
2) Within the command prompt, execute the following command: ' net stop winmgmt ' without quotations.
3) Rename your Repository folder (%SystemRoot%\System32\WBEM\Repository) just in case you wish to restore it.
4) Within the command prompt, execute the following command: 'winmgmt /salvagerepository' without quotations.
5) The above command will rebuild the repository if it is corrupted and then restart the WMI service.
After your WMI repository has been rebuilt, please try and activate DA2. If you're still seeing the same symptoms, it could be that you're running on an older BIOS that needs to be updated. We've also had user reports of having to enter "c:\>net localgroup administrators NetworkService /ADD" in the command prompt as a final step. Another user reports that their winmgmt service was disabled. They were able to run msconfig and enable it, then start winmgmt from the command prompt, which finally fixed it for them.
(Source)
