WMI problems again

Hi,

My customer is getting an errro code 0xB "The hardware id couldn't be generated...". I've screenshared with them and I have found out that Windows Management Instrumentation service is in fact running. Can you provide specific things which should be checked for it to be solved? Unfortunately we are working with end customers who are usually not very tech savvy. There is a tip that one can look in compmgmt.msc to further debug the issue but no mention of what should be checked if the service is in fact running.

We need specific things we can check on customer's computer to make sure the hardware key can be generated.

Thank you for your consideration.

Much more information is needed. Versions (TA, OS, etc.), functions called, steps taken, etc.

This information is needed on every "bug" report (whether it's a bug or user-error).

See: https://wyday.com/limelm/help/faq/#useful-reports

After you provide enough information so that we can even begin to help, tell me did you try running your app and/or the TurboActivate Wizard as admin?

/* MessageId: TA_E_COM Message code (in Hex): 0xB Message code (in Decimal): 11

MessageText:

The hardware id couldn't be generated due to an error in the COM setup. Re-enable Windows Management Instrumentation (WMI) in your group policy editor or reset the local group policy to the default values. Contact your system admin for more information.

This error is Windows only.

This error can also be caused by the user (or another program) disabling the "Windows Management Instrumentation" service. Make sure the "Startup type" is set to Automatic and then start the service.

To further debug WMI problems open the "Computer Management" (compmgmt.msc), expand the "Services and Applications", right click "WMI Control" click "Properties" and view the status of the WMI.*/#define TA_E_COM ((HRESULT)0x0000000BL)

I am running the newest version 4.0.9.6 on Windows.I am using the sample C code from your download almost verbatim.The function which is failing is TA_CheckAndSavePKey I've sent the customer 2 versions, one tried to called it with TA_SYSTEM flag and one with TA_USER flag. Both failed with the same error code.We tried restarting the WMI service, it didn't help. We've restart the computer and the service starts automatically but the key still can't be generated.Unfortunately the customer's Windows version is in Swedish which makes things a bit difficult. As you can imagine they are just a normal computer user who doesn't tamper/change anything on the system on purpose. What kind of things can we check/verify to help to solve it?

TA_CheckAndSavePKey() will *never* return TA_E_COM. Something else is going wrong. Either you're logging the wrong things, something else is returning the error.

>> "What kind of things can we check/verify to help to solve it?"

Provide the actual function that is failing or provide the actual error code TA_CheckAndSavePKey() is returning. I can guarantee you it is not TA_E_COM (it cannot be).

Also,

1. Run the TurboActivate Wizard as admin, and go through the activation process. What happens?

2. What OS is the customer on (7, 8, XP, 10)? What architecture (x86, x64, ARM)?

3, from the error code: To further debug WMI problems open the "Computer Management" (compmgmt.msc),expand the "Services and Applications", right click "WMI Control" click"Properties" and view the status of the WMI.

Hi,

Thank you for your answer. Unfortunately I've looked at my original source for line numbers and not for debug version. I am sorry for the confusion.I managed to get some more information about the customer's system and it seems CPU/RAM information is not showing in Control Panel -> System. I am concluding the system is just not working properly then.

As to debug information: it seems that if there is a problem you ask us every time for informatoin about which exact function is failing and with what arguments. The problem is that reality of working with end customers (not corporate ones) is that you rarely get a chance to put a debug version on their computer and got them to call/screenshare with you. Usually they just get discouraged, ask for a refund and you don't get any chance to debug/solve problems.

Please consider adding an option to produce error_log file. It can even be in whatever format (even not readable to us). If it was produced when licensing fails we could just send it to you and got more information. The way it happens now is that you are always assuming our code is incorrect but that's just not the case as it works for thousands for other people. When there is a problem, the customer is usually long go before we go through the back and forth of "which function is failing with what exact argument" while the problem is almost always where something on customer's system isn't working with TurboActivate and we are left clueless about what it might be.

Thank you for your consideration 🙂

Reply
Discard post