Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dheiskell]

I recently upgraded from MC 17 to MC 19. I have an app that called the Automation interface on MC17, it can't find the interface on 19. I get an invalid class string from the following code which is still the method documented.

      HRESULT hr = m_pMJ.GetActiveObject (L"MediaJukebox Application");
      if (hr != S_OK)
      {
         hr = m_pMJ.CreateInstance(L"MediaJukebox Application");
         if( hr == S_OK )
         {
I tried building with Media Center 19.tlb versus the one from 17 and that had no effect. Both GetActiveObject and CreateInstance fail where MC19 is already running or not. I am wondering if MC 19's COM interface wasn't registered when it was installed? MC 17 was on the machine and then it was uninstalled after installing 19. Could this lead to the automation interface disappearing?

[JimH]

Did you try the DevZone?
http://wiki.jriver.com/index.php/DevZone

[dheiskell]

Yes Jim I did that's where the original code came from.

[Mysticeti]

Was the "Automation Interface" dropped in newer versions or is there an option on install we need to check?

[JimH]

Not as far as I know.

[Mysticeti]

Thanks.  It's been forever since I've upgraded and I think I installed the 64 bit version.  Uninstalling and then re-installing the 32 bit version seemed to fix my issue (cav66.exe couldn't find the automation interface).

[JimH]

That brings back memories.

[Mysticeti]

My CAM6.6 is still tickin' thank goodness.   

It's way out of warranty at this point.

No idea what I'll do when it finally gives up the ghost.

[Mysticeti]

Thought about creating a new topic for this but having context from the thread seems useful...

I hit this error again after installing MC31 ("this error" being the Automation Interface not being found).  This time I did use the 32-bit version of the Windows app so that was most likely a red herring. 

I think what happens is that my process is to

• do a Library Backup of the current version
• install the latest version
• restore the old library into the new version
• verify that things basically look/work right with the new version
• uninstall the old version
• panic when I notice that CAV66.exe now can't find the Automation interface

I'm guessing that uninstalling the old version is what's messing me up as reinstalling the new version seems to fix the problem.

Hopefully by jotting these notes down I'll remember not to panic next time 

Still pondering what I'll do when my CAM6.6 joins the choir invisible