[ACK] Smart Tags broken in 6.3 SR1

Thanks for the quick answer! I highly appreciate that kind of support!

Hans

Hi Bradley,

I wholeheartedly second this request! After upgrading to Office 2016 (on Windows 10) a few days ago, I immediately noticed that when the Additional Actions menu that appears when you right-click a passage only lists two items:

Open Bible to Ephesians 3:2
Passage Guide

I crucially need the Insert Passage item since I use that all the time! Please let us know if this issue can be fixed. Otherwise I'm tempted to write my own Office Add-In because this feature is so essential for me. Thanks!

hello Bradley

I am running Office 2016 and Logos version 6.6 SR-16.6.0.0059.  The Smart Tag is partially working.  The only options available are

• Open Bible to Scripture reference
• Passage Guide

The one feature that I do use the most which is to copy the verse to Word and is no longer available.

Thanks for the additional detail. As mentioned, I've created a case for us to investigate Office 2016 compatibility with the Smart Tag; we'll look into the "replace with passage" issue when we work on that case.

Dear Bryan, 

Thanks for the clear instructions to run the fix for SmartTags for Windows. I have Windows 7 and use MSOffice 2010 to run Logos 6. For months I was so frustrated because of my inability to use one of my favorite functions of Logos, and today, thanks to your instructions, I was able to see SmartTags work again. From the bottom of my heart, thanks Bryan.

Thank you, Timothy Brown, this did the trick!  [:D]

Windows was crashing just by scrolling over "Additional Actions." 

Now it is working beautifully and allowing Logos features.

1. Most users can probably skip to # 2 of Tim's list. 

2. In Windows Explorer, you will find the file in your download folder, Continue with # 3. 

Thank you, Timothy Brown, this did the trick!  

As you are referring to this post then the thanks go to Bryan Albert.

Yes, Bryan deserves the credit and thanks!

I tried Smart Tags again with Verbum 6.6 SR-3 (64 bit), and I am using Office 2016 64 bit. What I can add is that the manual regedit changes worked fine, but the regsvr32 of Verbum.exe failed. When I do the right click on a verse I too get the Open the Bible to... and the Passage Guide, but I do not get Replace with Passage or Copy Bible Verse. Fixing the problem that causes regsvr32 of Verbum.exe to fail (maybe Logos.exe does as well?) might fix this one issue?

Also - for what it's worth, I Had CCleaner scan my registry, and it reported a "ActiveX/COM Issue" :

ActiveX/COM Issue LogosBibleSoftware.Application - {FD24A0E8-C3F2-4821-A456-35DA2DC4BB8F} HKEY_CLASSES_ROOT\LogosBibleSoftware.Application

Maybe this is a side effect of the regsvr32 command failing.

When I do the right click on a verse I too get the Open the Bible to... and the Passage Guide, but I do not get Replace with Passage or Copy Bible Verse.

This is because the Logos Smart Tag has not yet been updated to support Office 2016. A future update to the Logos Smart Tag will resolve this issue.

When I do the right click on a verse I too get the Open the Bible to... and the Passage Guide, but I do not get Replace with Passage or Copy Bible Verse.

This is because the Logos Smart Tag has not yet been updated to support Office 2016. A future update to the Logos Smart Tag will resolve this issue.

Good! Thanks Bradley.

I just called Logos support and they said it was a MS problem? So is there a fix coming?

A future update to the Logos Smart Tag will resolve this issue.

I am having the same problems on my MacBook Pro.  Has anyone had this problem on their Mac?  If so what steps are necessary to fix the problem?

Thanks for your time and assistance.

Blessings,

Glen

I am having the same problems on my MacBook Pro.  Has anyone had this problem on their Mac?  If so what steps are necessary to fix the problem?

Thanks for your time and assistance.

Blessings,

Glen

Glen, I believe you were given a bum steer in your original thread as this thread is for the Windows problem. As a Mac user see https://community.logos.com/forums/t/115655.aspx, especially the last two pages.

Hi Dave, I can't stop laughing.  It's not the first nor the last bum steer!  Unfortunately the link you provided doesn't work.  I get a notice "access denied" from what appears to be a secured page.

Thanks for the blessings of laughter!  Blessings,

Glen

Unfortunately the link you provided doesn't work.  I get a notice "access denied" from what appears to be a secured page.

Glen, the link is working for me. 

I will try it again, thanks!

 Unfortunately the link you provided doesn't work.  I get a notice "access denied"

I fixed it shortly after posting, so you must have tried too soon!

A future update to the Logos Smart Tag will resolve this issue.

Initially I had no Logos Smart Tag in Word 2016. It is now fully functional in Word 2016 (32-bit) and Logos 6.7 RC1 after manually registering the Smart tag (dll). Note that the Smart Tag has returned to the ...\Logos\System\ folder in v. 6.7

Unbelievable! With the arrival of Logos 6.7, SmartTags no longer work (again). Does anyone have an idea what the secret might be to fixing it this time around? It's a feature I use every time I use Logos and is a huge time-saver for me. Any suggestions greatly appreciated! I am NOT using Word 2016. I'm using Word 2010.

Unbelievable! With the arrival of Logos 6.7, SmartTags no longer work (again)

Take a cue from my previous post, above, and look at the wiki registration.

I have the same problem.

“%LOCALAPPDATA%\Logos\Logos.exe” /register doesn't work

Hans

Please look at my post above where I registered the Smart Tag dll

I suppose you mean: “%LOCALAPPDATA%\Logos\System\Logos.exe” /register? But that doesn't work for me either. Do I make a mistake?

I mean the Smart Tag dll  -- L4SmrtTg.dll  (I'm in a hurry so the name may be wrong) as per the wiki link I provided

Dave, I'm having the same issue as AJ. I tried your register command, with the System folder, and it fails. Mine indicates the User module does not load and the module cannot be found. But I know absolutely that the dll is in the specified path. I've tried everything, including copying the dll to windows/sysWOW64 and trying to register it there as well, but nothing has worked. I'm trying to figure out what changed with Logos 6.7 in addition to reverting back to the Logos\System folder for the L4SmrtTg.dll. Any further ideas from anyone would be greatly appreciated.

Dave, I'm having the same issue as AJ. I tried your register command, with the System folder, and it fails. Mine indicates the User module does not load and the module cannot be found

What is the command you used?

Thank you for replying, Dave. The second command I used was: regsvr32 %LOCALAPPDATA%\Logos\System\L4SmrtTg.dll

This is the one that results in the error message that the module could not load and could not be found.

The first command, which was successful (at least there was no error message after executing it), was "%LOCALAPPDATA%\Logos4\System\LogosCom.exe" /register

The wki tries to explain that your Logos install folder may not be called \Logos, so try the command regsvr32 %LOCALAPPDATA%\Logos4\System\L4SmrtTg.dll as \Logos4 appears to be your Logos folder.

Dave, your direction on the other SmartTags post to repair Logos through Control Panel did the trick! Many thanks!

I have to say that I spend way too much time repairing Logos Bible software than using it for its intended purpose. After attempting several fixes in this thread, and wasting too much time, I'm simply going on a Logos strike. When they fix it, I'll start purchasing again. 

I have spent several thousand on this software, only to have some features I use all the time, repealed by bug. 

You listening, Logos?

Initially I had no Logos Smart Tag in Word 2016. It is now fully functional in Word 2016 (32-bit) and Logos 6.7 RC1 after manually registering the Smart tag (dll). Note that the Smart Tag has returned to the ...\Logos\System\ folder in v. 6.7

I had success in getting Smart Tags working again in Word 2013 by following the wiki instructions re manual registering. The key was figuring out that for me the correct folder was \Logos5\System. It doesn't take too long to run the commands indicated in the wiki, trying the different possibilities (Logos\System, Logos4\System,  Logos5\System or Verbum\System).

I've tried all the above to no avail. Previously I found Bryan Adam's 'PowerShell script' to work for each new update, but now that L4SmrTg.dll has been moved back into the Logos4\System folder it won't work as it looks for the .dll as previously as a separate folder for the update number under Logos4. I don;t suppose that 'PowerShell script' can be reworked to acocutn for this reversal of policy.

Otherwise any other ideas? Thanks

I've even gone right into the System folder to register the .dll

Previously I found Bryan Adam's 'PowerShell script' to work for each new update, but now that L4SmrTg.dll has been moved back into the Logos4\System folder it won't work as it looks for the .dll as previously as a separate folder for the update number

Yes, I've been trying to get some information from Faithlife about the change of folder and the updated Smart Tag dll. It would help if you state what you have tried (the exact commands used), version of Office (32-bit or 64-bit) and your OS (32-bit or 64-bit).

Sorry, that should read 'Bryan Albert'

Sorry, that should read 'Bryan Albert'

Your first attempt made sense!!

Thanks Dave, I have Win 7 (64bit), MS Office 2010 32bit.

My Logos in not in the C: directory having put it in \Program Files so the path name is \Program Files\Logos4\System\L4SmrTg.dll

I checked the registry as follows:

1. Does “HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{319A0316-DF84-4B3C-8117-349B7E98E613}” exist? If so, delete it. (This did exist so I deleted it)
2. “HKEY_CLASSES_ROOT\TypeLib\{81490292-5570-4D02-A2AC-7B828DBD0A8A}\1.0\0\win64” should exist and contain the path to LogosCom.exe. (This did exist and gave path)
3. If “HKEY_CLASSES_ROOT\TypeLib\{81490292-5570-4D02-A2AC-7B828DBD0A8A}\1.0\0\win32” exists, delete it. (Did not exist)

I have applied the basic command line you indicated taking account of \Logos4 and obviously it couldn't find the module.

I then used the actual path for my system and was able to register logos.exe, and then tried to register the dll module as below with the error message as indicated:

Previously I found Bryan Adam's 'PowerShell script' to work for each new update, but now that L4SmrTg.dll has been moved back into the Logos4\System folder it won't work as it looks for the .dll as previously as a separate folder for the update number under Logos4. I don;t suppose that 'PowerShell script' can be reworked to acocutn for this reversal of policy.

I plan on fixing (and updating) the PowerShell script to work in the current environment.

Bryan

so the path name is \Program Files\Logos4\System\L4SmrTg.dll

It's L4SmrtTg.dll (two t's).

I then used the actual path for my system and was able to register logos.exe, and then tried to register the dll module as below

1. \Program Files\Logos4\Logos.exe  is the one to register!

2. a. Copy and paste would serve you better - the dll is L4SmrtTg.dll

    b. Run the Command Prompt "as Administrator" to get the right path for regsvr32 i.e. C:\Windows\System32

Thanks Dave, and Bradley.  They did the trick allowing it to be registered. But then I noticed my MS Word had dropped the logos smart tag. A computer reboot brought it back into play. So all working again now.  I appreciate your patience and skills.

I have tried all the solutions here, and still no smart tags.

I have rebooted.

Directory: C:\Users\Scott\AppData\Local\Logos

Running Logos 6

I have tried all the solutions here, and still no smart tags.

I have rebooted.

Directory: C:\Users\Scott\AppData\Local\Logos

Running Logos 6

what exactly was the command you used?

Thanks for looking into this, Bryan. It means a great deal to many of us!

I look forward to the new and improved PowerShell script.

Paul

I just experienced the same issue all over again: Smart Tags broke.

I tried to do what worked for me before: applying the fix recommended by Timothy Brown, but this time, even such fix did not work.  

This is very annoying,

Nelson Aguillon 

I tried to do what worked for me before: applying the fix recommended by Timothy Brown, but this time, even such fix did not work.  

The Powershell script hasn't been fixed. Try the two registration steps in https://wiki.logos.com/Smart_Tags#Smart_Tags_and_64-bit_Logos and look at the other recent threads on Smart Tags.

Here is a copy of the error I receive when I try to RegisteSmartTags.

Nelson