Reposting this in a new thread (previous discussion here) https://community.logos.com/forums/p/104760/732011.aspx#732011
Since installing 6.3 SR1 I Smart Tags no longer work for me. Previous fixes no longer work, nor do other suggestions.
This is a feature I use almost daily in my ministry and I could really do with having it back!!
I don't know if this makes any difference, but when I run the two commands, the first one (the register command) no error message appears, but neither does it say it is successful. Rather, Logos 6 comes to the front, as if I had clicked on a minimized icon. The second command when run does give a successful notice. Still SmartTags, though listed as an available Action in Word 2010, does not work.
I get the same behaviour with the first command.
If I run the second command [regsvr32 “%LOCALAPPDATA%\Logos4\6.3.0.0056\L4SmrtTg.dll”] but WITHOUT quotation marks [regsvr32 %LOCALAPPDATA%\Logos4\6.3.0.0056\L4SmrtTg.dll] then I also get a succesful notice, but no Smart Tags.
Richard, this feature saves me an enormous amount of time, and like you, I am very, very interested in finding a solution. I think I may have found a clue at least. Don't know if this is the case with you or not, but there are several other additional actions enabled in my Word for the AutoCorrect right-click menu. And the fact is, now NONE of them work, not just Logos Bible References. I'm going to use the Microsoft Community to see if someone there might have an answer. Apparently, our great Logos forum users have not replied because they too are stumped! Let's not give up hope!
Another clue. Means nothing to me but might make sense to someone else!
When I run "%localappdata%\Logos4\Logos.exe" /register as per the wiki instructions and get the message "Logos Bible Software failed to register."
However, the other command - regsvr32 %LOCALAPPDATA%\Logos4\6.3.0.0056\L4SmrtTg.dll - succeeds.
Richard, I discovered the fix. You need to edit the first register command to read as follows:
"%LOCALAPPDATA%\Logos4\6.3.0.0056\LogosCom.exe" /register
Note that the change is you are registering LogosCom.exe rather than Logos.exe.
Worked for me ... hope it works for you as well!
Richard, I discovered the fix. You need to edit the first register command to read as follows: "%LOCALAPPDATA%\Logos4\6.3.0.0056\LogosCom.exe" /register Note that the change is you are registering LogosCom.exe rather than Logos.exe. Worked for me ... hope it works for you as well!
BY JOVE, HE'S DONE IT!!!
Well done, that man! And a thousand thank yous!
Just want to be sure the credit goes where it really belongs. I had no clue. I cried out to the Lord for the answer, and He reminded me of something I read on the SmartTags wiki page about editing the registry and the mention of a key containing the path to LogosCom.exe. The Lord said that was my answer, and it was! Let's praise Him together. He knows everything, including technology!
Let's praise Him together. He knows everything, including technology!
[Y]
I discovered the fix. You need to edit the first register command to read as follows: "%LOCALAPPDATA%\Logos4\6.3.0.0056\LogosCom.exe" /register
I discovered the fix. You need to edit the first register command to read as follows:
Well done. This should have been done during the software update!
You might be able to help me. I also with the latest release lost my smart tag capability and I use it a lot also -- or did till this week. Most frustrating. I was thankful to see your posts but I still having trouble -- I presume it is my lackof skill in using command prompt. I am using windows 7, 64-bit, and Word 2010 32-bit
My Logos 6 software is on my drive not C: That is, my copy of LogosCom.exe is in \Program Files\Logos4\6.3.0.0056\LogosCom.exe
How does that change the register command land in command prompt. I have gone to \ and entered it to no effect, and have done so down through the chain sub directory at a time and still to no effect. am I missing something? Please excuse my ignorance.
Thanks in advance for any help you can give.
John
My Logos 6 software is on my drive not C:
"D:\Program Files\Logos4\6.3.0.0056\LogosCom.exe" /register
After you open the command prompt
Ensure your Logos folder name is Logos4 as it could be Logos5 or Logos
Hi Dave, Thanks for your response. I tried this but upon hitting 'enter' it returned to the drive prompt \>, and eve restarting both Logos 6 and Word there was still no availability of the smart tag. I even tried both with a space before /register and without a space, but no difference. So, so far no joy.
Are you sure the path is correct? Did you include the quote marks "....."
Yes, but to just make sure I did it again and still no recognition in the command prompt window that anything happened, returning simply to \> , and no change in Word options despite it being enabled in the Word's options for Actions
Working now! I saw from the wiki page (https://wiki.logos.com/Smart_Tags#Smart_Tags_and_64-bit_Logos) that I may need to check settings in the Windows Registry):
Having first backed up the registry (exported it) I went in and saw that as per 1 and 3 these were there, so I deleted them; and that item 2 was there as should be and left it. Then exited.
I then re-ran the command line you recommended. and it now works!
Thanks Dave. Much appreciate your time and patience. so thankful.
John (from 'Down Under')
I'm glad it is working (also from Oz!).
How does one find the correct path? And how does one enter the correct path in the Command Prompt? Nothing works for me. Thanks!
I obviously don't know anything about this.
Paul
The Logos folder is within c:\Users\your_username\AppData\Local (look for Logos4, Logos5 or Logos). Within the command prompt it is quicker to type as shown below, where the Logos folder is called Logos4.
Thanks very much for your input, Dave. I successfully made the various entries as directed, but nothing works. I'm not at all sure why - fresh out of ideas too.
I successfully made the various entries as directed, but nothing works. I'm not at all sure why - fresh out of ideas too.
Tech Support should be able to get onto your computer to diagnose this.
We're looking into this some more and will report back soon. Sorry for the trouble!
All,
Sorry for the following post, but this is an ongoing problem with Logos and Smart Tags. I'm trying to be patient with this, but I've been struggling with this issue for years with Logos. I love this company and program, but I absolutely LOVE the smart tag feature.
I just got off the phone with Tech Support and they said they while they don't support this feature, they are looking into it. While on the phone they sent me an email with a link to a beginner basic level 101 type of how to enable the options in Word! When I explained that this was way beyond activating a "click-box" they said they were looking into it. There was no reference to possibly checking out the wikiforum for "registry fixes" or REGSVR32 suggestions, just thanks and have a great day. The tech didn't even ask what version 32 or 64 bit version, just here's a link, read it and see if it fixes your problems.Are there only a few that use this feature and that is why it is unsupported? I assumed, perhaps wrongly, that for many, Smart Tags is a MUST feature for LOGOS customers. It's always an anxious moment for me to see if Smart Tags will continue to work after each update or whether I will have to head to these forums for a solution. This isn't a one time thing, but an ongoing issue. I can honestly say I love the program, but this is a must feature for me in writing sermons, papers, study guides, white papers, etc.
Are Smart Tags not supported by Microsoft anymore, so that is why LOGOS doesn't support it? I could understand that, but sadly there is rarely any communication from LOGOS to consumers unless the USER seeks answers in the forums. I've spent thousands of dollars over the years on LOGOS and don't want to abandon it, sell my library and seek another solution, but I would love to have this supported. I use many products, Proclaim(Subscriber), Logos 6 (Portfolio Owner),Bible Study Mag (Subscriber), Lexham Press (owner of many titles), MobileED (Student) etc. but I'm just a little frustrated today as I once again waste hours trying to fix something that I previously had fixed for Logos.
Thanks for listening during this counseling session! I appreciate your time and thank all of you for your support over the years with Smart Tags and the great Bible program LOGOS. I will now step away from the keyboard and get into His Word to ease my frustration and remind myself of what's really important in life! Him and His Word!
Thanks all and have a GREAT DAY!
Jeff
Jeff,
You reflect my sentiments exactly here, except that I've never had this problem before. After applying all the "fixes," mine still do not work. I have no idea where to go from here because I use "smart tags" or so-called "actions" constantly. Now what?
Sincerely,
PS
And why did they remove them from PowerPoint? They were great there too.
Dave,
Tech Support refused to help in any way. "Smart Tags are not supported," they said rather curtly.
And why did they remove them from PowerPoint? They were great there too
Bradley commented on this question at https://community.logos.com/forums/p/55480/401118.aspx#401118
Are Smart Tags not supported by Microsoft anymore, so that is why LOGOS doesn't support it?
This article - https://www.logos.com/articleviewer/530 - sheds some light on this question
Thanks, Graham, for the links. I think I've looked at them before, and they are interesting. However, nothing so far has restored by Smart Tag usage. I'll keep trying and not give up!
Dave, Tech Support refused to help in any way. "Smart Tags are not supported," they said rather curtly. Paul
I was hoping you might get a more sympathetic ear, but Bryan (Faithlife) says it is being looked at, so hope still prevails.
I am very happy to hear that. I know they have the capacity to solve this problem, and I look forward to its resolution. It is such an efficient feature to be able to use.
I'm glad I've never tried to use SmartTags. I just use Copy Bible Verses to do this, so there's nothing to keep breaking every time Logos updates. I know I'm perhaps not saving one or two seconds every time I want to insert Bible verses into my Word documents, but I do find CBV very handy, and I love having more control over how the verses look when they get pasted into Word.
Hi all,
I am writing this mainly to the developers that monitor this forum. It's late and I can't get this working as I have a limited timeframe - I will go through the wiki later. In the meantime I will use your competitor's product InstaVerse to do something similar (but not as well).
While I understand that SmartTags are a low priority Microsoft Office item for Microsoft, for many of us Logos users this is a daily use thing and I really hope that Logos supports this better while the functionality exists. I know a lot of customers really appreciate and use this feature (if they know about it). Frankly, it's one of my most used things about Logos.
For years this feature has been de-prioritized by Logos and I'm sure a large part of that is to ensure that they line up with Microsoft's priorities or perhaps because they think that people will use one of their own products (at one point I think they had a sermon composition module, not sure if there's one now). I'm not sure of the marketing strategy, but, from a user level in the trenches, I just want to raise my hand with the others and say I would really like them to support this a bit better in the future and to keep this feature (or something like it) in future releases. Please allow us to continue to have this instant verse smart tagging. Being able to almost instantaneously include any Scripture verse is a real help - it saves time. Thanks for listening.
Friends,
I had some help, and we reran the instructions that worked for others, and this time it worked. Not sure why!
Thanks everyone for your help.
In 6.3 SR-2 which has just shipped, we fixed an issue where the application's /register function for COM registration wasn't working properly. This should get Smart Tags working again.
The /register feature allows one to register COM (used by Smart Tags) via the Logos Splash Screen application.
To use it:
That should do it! We're currently investigating an issue that may affect some users who have both the 32 bit and 64 bit versions of the Logos COM server registered at the same time. I'll post back soon with more information.
Bryan
Installed 6.3 SR2. Went through Bryan's steps from his 1:04pm post. First 3 steps worked fine. Received an error (In italics below) when I get to step 4.
The module L4SmrtTg.dll failed to load.
Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL Files.
The Specified module could not be found.
I don't know if this is a function of the fact that so many of us have tried for weeks to get this working and something may have changed in our files/registry, but it's still not working for me.
64Bit WIndows 8, 64bit Office 365, Logos 6.3. SR2-
Logos Smart Tag appears in Word/Option/Add-ins listed as "C:\Users\AppData\Local\Logos5\6.3.0.0074\L4SmrtTg.dll.
Go into Actions Submenu and Logos Smart Tag is enabled.
Restarted Word several times as well as Logos. Tried registering L4SmrtTg.dll in the C:\Users\AppData\Local\Logos5\6.3.0.0074\L4SmrtTg.dll. and it says it succeeded, but no luck .... FRUSTRATED.
Will this be the 3rd week where I will have no Smart Tags in Logos/Word to write my sermon? Hard enough to write the lessons and studies I teach, but would love to have it by Saturday. Should I uninstall and reinstall???? I just don't want to download 40 GIGABYTE again!
Any Suggestions??? PLEASE HELP US!!!
Thanks.jeff
I don't know why it is not registering for you. I doubt a reinstall of the program will fix the problem.
I'm sorry you continue to have trouble with the Smart Tags.
This error message means that the regsvr32.exe program was not able to find the L4SmtTg.dll file, which probably means that there was a typo in the path you gave to the L4SmtTg.dll file. Note that the file name L4SmtTg.dll has two t's in a row...
The L4SmtTg.dll is for 32 bit Office and does not work with 64 bit Office. See https://www.logos.com/articleviewer/530 under System Compatibility and Troubleshooting. However, we do have an experimental 64 bit Smart Tags dll, see https://wiki.logos.com/Smart_Tags#Smart_Tags_for_64-bit_Office. Some users have had success with that. I not sure that this is really the issue, though, since you had Smart Tags working before. Are you sure your Office 365 is 64 bit?
This is a good sign, it suggests that Word recognizes the Smart Tag dll, and that the problem is the COM connection between Logos and the Smart Tag dll. I'll get back to you on this shortly.
How did you successfully register the dll? Did you use a different mechanism than the regsvr32.exe program discussed above?
Hopefully we can get this figured out quickly...
I complained when SmartTags stopped working. Now I offer kudos to the Logos programmers for fixing it and "supporting" it even though they don't support it. The various posts about it indicate that it is a very valuable tool for many Logos users. I know it saves me, not seconds, but hours as much as I use it. Those who have the versions of Word that support SmartTags or Additional Actions should give it a try if they haven't ever utilized it. Sure beats the Copy Verses function by miles! Thanks again, Logos programmers!
I received this message. Is there anything further that I could do? Thanks for your help in advance...
I got the same message... so far no solutions.
Patiently we wait!!!
Thanks Bryan!
I tried it again with same results. I even had someone else read me the commands and then we both verified. I see now another person is having the same problem below. Jeff
All I can say to that is Amen! and Amen!
... Open a Command Prompt (hit the Windows key, then type command prompt and choose Command Prompt from the list. In the Command Prompt, type cd C:\Users\YOU\AppData\Local\Logos Enter, where You is your Windows user name. You can hit the Tab key while you're typing and it will cycle through matching folder names (such as your user name when you get to the C:\Users\ part). Note also that if you upgraded from Logos 4 or Logos 5, the name of the Logos folder could be Logos4 or Logos5. Type Logos.exe /register Enter, you should see a dialog that says, "Logos Bible Software was registered successfully." If you are running a 64 version of Windows, you'll need to register the Smart Tags dll manually: Type C:\Windows\System32\regsvr32.exe 6.3.0.0074\L4SmrtTg.dll Enter. You should see a dialog that says, "DllRegisterServer in 6.3.0.0074\L4SmrtTg.dll succeeded." ... Bryan
...
This restored SmartTags for me, too, upon installing Logos Bible Software 6.3 SR-26.3.0.0074.
My config is in my signoff.
I received this message. Is there anything further that I could do?
Please show the complete command in a screenshot. Are you sure you have the correct Logos/Verbum folder name?
we do have an experimental 64 bit Smart Tags dll, see https://wiki.logos.com/Smart_Tags#Smart_Tags_for_64-bit_Office. Some users have had success with that.
This worked for me tonight.
Thanks for the attempts, but, none of the wiki options or regedits worked for me. I've done everything here and followed the instructions on the wiki - even tried the custom dll. Nothing. Wish I could go back in time. Any ideas?
We've created a Windows PowerShell script (the modern equivalent of a Command Prompt batch file) to register Logos COM and Logos Smart Tags for 32 bit Office. On most Windows versions, PowerShell comes with script execution disabled by default, so if you haven't already, you'll need to set the PowerShell execution policy to allow script execution, as described in step 1.
You can also register COM and Logos Smart Tags for Verbum and Noet:
Hopefully this script will help resolve any lingering COM registration issues. Please let me know if you have problems or questions.
Thanks,
Thanks for the response. I have a Logos folder with only an Install folder inside of it (i.e. Local\Logos\Install) and a Logos5 folder with 2 different smart tag files. One file located in Local\Logos5\6.3.0.0056\L4SmrtTg.dll and another in Local\Logos5\6.3.0.0074\L4SmrtTg.dll.
Does that help at all? I really like smart tags convenience and believe it to be a selling point, but can live with copy paste.
Bryan Albert,
Thanks for the instructions for using the Windows PowerShell script. It fixed my problem with Logos and Paratext not scrolling together. I think the scrolling problem started after the latest update from Logos since it was working fine before that.
David Matti
Translation Consultant
SIL Islands Asia
Bryan,
Thank you. This also worked for me. However, the first time I attempted your fix I had a space between Remote and Signed and it did not work. Then going back and removing the space, everything worked exactly how you have it detailed step by step. After all of this do I need to run PowerShell as administrator again and Set the Execution Policy back to No?
Thank you for all of your help, and for everyone's suggestions!
