The Logos COM API is not registered with Windows

Page 1 of 1 (7 items)
This post has 6 Replies | 3 Followers

Posts 355
Michel Pauw | Forum Activity | Posted: Sun, Dec 4 2016 10:06 PM

I'm using Logos and ParaTExt, which should be able to work/scroll together.

However, when I try to enable the that scrolling together, I get the message:

- The Logos COM API is not registered with Windows

I think I've gone through all the suggestions regarding Smart Tags on the forum, but it doesn't seem to make any difference. I still get the error.

I have:

- Windows 10 Pro, 64-bits
- Office 2010 + 2013, 32-bits
- Logos Now

Posts 9151
LogosEmployee

Try running the following command in Start > Run:

%LOCALAPPDATA%\Logos\Logos.exe /register

This will re-register the COM API.

Posts 3
Academic Dean | Forum Activity | Replied: Tue, Dec 6 2016 5:18 AM

Done several times.

I have two Logos.exe files: one in the Logos folder and one in the Logos\System folder. I tried to register both.
I also tried to register the LogosCom.exe in the Logos\System folder.

Without success

Posts 9151
LogosEmployee

Academic Dean:
one in the Logos folder

What happened when you ran that one with the /register switch. Did a dialog box appear? What was the message?

Posts 355
Michel Pauw | Forum Activity | Replied: Thu, Dec 8 2016 10:26 PM

I'm having:

1. C:\Logos5\Logos\Logos.exe (21-11-2016 / 141kb)
2. C:\Logos5\Logos\System\Logos.exe (21-11-2016 / 34.374kb)
3. C:\Logos5\Logos\System\LogosCom.exe (21-11-2016 / 188kb)

Which is / are the one(s) that should be registered?

If I remember correctly, I first registered 1, then a message appeared saying something like registering succeeded. But there was no effect.
Then I found that I had to register the other two as well, but both don't give any message.

I also followed instructions on https://wiki.logos.com/Smart_Tags, but found out:

  1. If “HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{319A0316-DF84-4B3C-8117-349B7E98E613}” exists, delete it. --> DONE
  2. If “HKEY_CLASSES_ROOT\TypeLib\{81490292-5570-4D02-A2AC-7B828DBD0A8A}\1.0\0\win32” exists, delete it.
  3. “HKEY_CLASSES_ROOT\TypeLib\{81490292-5570-4D02-A2AC-7B828DBD0A8A}\1.0\0\win64” should exist and contain the path to LogosCom.exe.

2 and 3 were not possible to check, because the register didn't let me go into HKEY_CLASSES_ROOT\TypeLib\{81490292-5570-4D02-A2AC-7B828DBD0A8A}, due to an unspecified error.

Posts 9151
LogosEmployee

Michel Pauw:

I'm having:

1. C:\Logos5\Logos\Logos.exe (21-11-2016 / 141kb)
2. C:\Logos5\Logos\System\Logos.exe (21-11-2016 / 34.374kb)
3. C:\Logos5\Logos\System\LogosCom.exe (21-11-2016 / 188kb)

Which is / are the one(s) that should be registered?

#1

Michel Pauw:
If I remember correctly, I first registered 1, then a message appeared saying something like registering succeeded. But there was no effect.

This should be all that you need to do.

Michel Pauw:
Then I found that I had to register the other two as well, but both don't give any message.

The other two don't support the /register flag; you do not have to register them.

Michel Pauw:
2 and 3 were not possible to check, because the register didn't let me go into HKEY_CLASSES_ROOT\TypeLib\{81490292-5570-4D02-A2AC-7B828DBD0A8A}, due to an unspecified error.

If Registry Editor is giving you errors when you attempt to browse the registry, that may indicate registry corruption which would be a significant problem on your system (and is likely to be the reason that the Logos COM API doesn't work). Sorry, but I don't have any knowledge of how to repair a corrupt registry.

Posts 1
David Millard | Forum Activity | Replied: Mon, Aug 17 2020 3:43 AM

This little gem is all i needed for mine to finally work.

Page 1 of 1 (7 items) | RSS