CoCreateInstance() failing after switch to NET4

Follow

Tom Eckert

July 31, 2015 18:43

We have 3 apps that use the QlmLicense object: an install applet that registers and stores the key, a windows service that verifies the key, and a key manager applet that we use for development. All use the same LicencseValidator class and all were working when we were using the NET 2.0 version.
We switched to the NET 4.0 version and now the windows service works but the other two fail.
I've verified the registry keys for the QlmLicense object (CLSID {8A2FA042-8632-4B0B-9914-596C31BEAB4E}).
The first time an app calls CoCreateInstance() the error returned is 0x80040154, if it's called again it returns 0x80070002 thereafter.

I should mention that I unregistered the NET 2.0 TLB file and registered the NET 4.0 (with the codebase option) on my build machine before building the apps, using the respective RegAsm.exe from NET 2 and 4. And our installer registers on the test machines. I've tried doing this step manually as well to no effect.

Does QLM have a simple app (with or without source) that could simply verify that the object is installed correctly for COM?

Thanks,
Tom

Thomas Eckert
Sr Software Engineer
AudioScience, Inc

0

• Official comment

  

  Soraco Technologies August 07, 2015 11:29

  Update from Thomas Eckert:

  I had the library registered but the path I had it in when I did that
  was in the user directory, so it was failing when I tried to access from
  a service.
  I copied it to the Program Files branch and re-registered and that fixed it.
  Thanks,
  Tom

  Comment actions Permalink

Please sign in to leave a comment.