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 was executing the wrong dll. The correct one was hidden in a different folder. Found it, and it works.
Thanks for all the work you put into this.
Here is a copy of the error I receive when I try to RegisteSmartTags.
Nelson, please read my previous post as that comes from the unfixed PowerShell script.
Thank you, Dave. I will.
Nelson
PLEASE can someone provide me the link to download version 6.4 as I am trying to address the 'system' folder issue.
Thank you,
Nelson Aguillon
What gave you the idea that this was necessary? Did you click the link in my post about registering the Smart Tag?
My bad, Dave!
I was doing something incorrectly. Please forget my previous comment. Everything is working fine again.
Blessings,
I've updated the Windows PowerShell script to register Logos COM and Logos Smart Tags for Logos 6.7 and newer. It's works with Logos installed to the System folder, has enhanced messages and a few fixes. There's a new feature for registering the LSmtTg64.dll for 64-bit Office, too.
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:
You can also register COM and Logos Smart Tags for Verbum and Noet. To do this, you need to specify a command line switch to PowerShell, which requires a PowerShell console (a PowerShell window):
Your can also register our Smart Tag file LSmtTg64.dll which will enable Logos Smart Tags for 64-bit Office. To do this, you need to specify a command line switch to PowerShell, which requires a PowerShell console (a PowerShell window):
In testing, I was able to use the script to register both L4SmrtTg.dll (for 32-bit Office) and LSmtTg64.dll (for 64-bit Office) at the same time, and my Logos Smart Tags worked in 32-bit Office. If someone with 64-bit Office could register our LSmtTg64.dll file with the -Office64Bit switch and report back here if it works, then register the L4SmrtTg.dll too (run the script without the -Office64Bit switch), and report, that would be great.
Please let me know if you have problems or questions.
Thanks,
Bryan
PS I think I've found a problem with the way Windows Installer is registering L4SmrtTg.dll and hope to have it fixed for Beta 3.
Does it also work for Office 2016?
Hans
Does it also work for Office 2016? Hans
Yes
I've updated the Windows PowerShell script to register Logos COM and Logos Smart Tags for Logos 6.7 and newer.
Thanks Bryan
I also updated the wiki for Smart Tag and 64-bit Logos to reflect use of the updated PowerShell script
I've tried the 64-bit option using the PowerShell but I got the error message: "Failed to find System folder at: C:\Users...\Logos4\6.7.0.0036. I checked the folder and find a sub-folder 6.6.0.0069, so I assume this is the problem.
How can I correct this? Be glad of help.
Paul.
I've tried the 64-bit option using the PowerShell but I got the error message: "Failed to find System folder at: C:\Users...\Logos4\6.7.0.0036.
You're using the wrong version of the script. Download it from http://downloads.logoscdn.com/LBS6/Support/RegisterSmartTags.ps1
Thanks, Dave, for the help. I downloaded the version for which you gave the link and it seemed to load correctly with no error message. However, when I tried to use the Smart Tag, I got the message "You're using the wrong version of the script"!
Seems like I'm stymied again!
Appreciate your input.
Paul
However, when I tried to use the Smart Tag, I got the message "You're using the wrong version of the script"!
Please explain "tried to use" (the message is a repeat of what I said in my previous post!). Were you following instructions at https://community.logos.com/forums/p/105737/780081.aspx#780081 ?
I used the instructions given by Bryan Albert: I right-clicked the downloaded file and chose 'Run with PowerShell'. It seemed to execute correctly—at least there was no failure notice. When I said I tried to use the Smart Tag, I mean that in Word I typed in a verse reference and right-clicked it. As soon as I tried to choose a paste option, I got the "You're using the wrong version of the script" notification.
I used the instructions given by Bryan Albert
OK?? Let's check what you are using:-
OK?? Let's check what you are using:- Logos 6.7? Operating System and whether it is 32-bit or 64-bit (check Control Panel >> System) Which version of Word e.g. 2013? Is it 32-bit Word (Task Manager will state that it is 32 bit, else it is 64 bit)?
I'm using Logos 6.7 as shown here:
Operating System is 64-bit as shown here:
Word 2013—Task Manager does not state that it is 32-bit as shown here:
Hope this will somehow reveal my problem! Thanks, Dave.
Since writing the above, I have tried again to use the Smart Tags but now, when I right-click a verse reference in Word, there is no paste option available—it's grayed out.
I also noted that Word was working in Compatibility Mode, but turning this off made no difference.
It is shown on the Processes tab
Dave, it worked and then it quick working. When I attempt to run Smart Tag and 64-bit Logos with PowerShell script, the black dos screen flashes open quickly I see red letters and it closes before I can read it.
Like I said it work at one time. Any thoughts?
Thanks
Thanks, Dave. It is 32 bit:
Is this the problem? What should I do about it?
The script should work, then. Rather than right click to run it, open a Powershell window and run it as described by Bryan.
When I attempt to run Smart Tag and 64-bit Logos with PowerShell script, the black dos screen flashes open quickly I see red letters and it closes before I can read it.
Run it from a Powershell window as described by Bryan
Dave I have been running it from the powershell window but it takes it to a black dos screen quickly and disappears. Could I have messed something up with the RegEdit?
I did what the Forum suggest.
Dave I have been running it from the powershell window but it takes it to a black dos screen quickly and disappears. Could I have messed something up with the RegEdit? I did what the Forum suggest.
Show me a screen shot of your input before pressing <Enter>
Thank you, Dave, for your time and expertise. I have tried running the script from the PowerShell window with no joy. I think I'll abandon the whole thing and not waste any more of my time or yours. I'll just use cut and paste!
I appreciate your patience with folks like me who just don't know what they're doing!
Thank you, Dave, for your time and expertise. I have tried running the script from the PowerShell window with no joy. I think I'll abandon the whole thing and not waste any more of my time or yours. I'll just use cut and paste! I appreciate your patience with folks like me who just don't know what they're doing! Paul.
Logos 6 is 64-bit so you will experience problems if you recently upgraded from Logos 4 or Logos 5, but you may also experience problems after updating Logos 6 e.g. from v6.6 to v6.7.Most users should use the PowerShell script below but if you are confident to do it manually start by running these commands in a Command Prompt:
Note 1 the \Logos\ folder could be \Logos4\, \Logos5\ or \Verbum\ for your installation.Note 2 the \System\ folder for v6.3 to v6.6 is replaced with a folder like \6.6.0.0069\. If more than one use the latest.
To open a Command Prompt, press the Windows key, type Command Prompt, and click on that. Then run the commands in steps 1 and 2, taking note of Note 1.
Joe,
Sorry you're having trouble, computers can be pretty finicky when it comes to running a script. Basically, the red error message is saying that PowerShell doesn't know what the term RegisterSmartTags.ps1 is (it doesn't recognize it as the name of a script name, which is what it is.) There are two possible reasons for this. First of all, you have to have a period and a backslash before the name of the script: .\RegisterSmartTags.ps1. Second, the script has to exist in the folder PowerShell is working in. In your screenshot, your PowerShell is in the the folder C:\Users\Joe, (as displayed on the prompt, PS C:\Users\Joe>. If you downloaded the script from the link in the instructions, your web browser probably downloaded the script to the folder C:\Users\Joe\downloads. So first you need to change to that folder, with the cd command (for change directory): cd downloads.
One trick you can use to make sure that PowerShell likes what you type is to use the Tab key to complete the command you're typing. For example, you could type register <Tab> and if you're in the right directory and the script is there, PowerShell will fill it out for you: .\RegisterSmartTags.ps1, adding the dot and backslash, then you just hit <Enter> and it will finally run the script.
Hope that helps!
Herzlichen Dank,
ich war auf der Suche nach einer Lösung für dieses Problem, auch in Office 2016 unter Windows 10 funktioniert jetzt wieder alles bestens!
Daniel
You're welcome, Daniel
Greetings Brian, I am posting here per the direction of a FaithLife employee.
They were working last week, now they aren't. I guess I should have anticipated this. I have done the "Easier method" That Mr. Brian Wooten had posted numerous times throughout the last few years renaming the latest file download to "system". But alas that doesn't work. Tried following the instructions under Run "RegisterSmartTags.ps1", but got a "Fail" on that. I am started a bug thread because that is what the other instructions said to do, but the Faithlife employee linked me back to this thread.
Any ideas?
Running Windows 10, Microsoft office 365, Logos Bible Software 6.9 SR-16.9.0.0044, platinum v5 (IH).
This really drives me nuts and costs me a lot of time on so many of logos updates.
Sorry I meant Dave Hooten
Tried following the instructions under Run "RegisterSmartTags.ps1", but got a "Fail" on that.
I wonder if you got the right version of the Powershell script. Download and execute as per this wiki article. If it fails report the complete error message.
Those were the instructions that I followed - at least I think I did. I right clicked the file with the Powershell window open and it gave me the option of run with in the Powershell, but I got a failure.
I posted just as the wiki article instructs, but was sent here by the FL employ.
By the way, thanks for your easier method of renaming the latest downloaded file to "System" that method served me well through many iterations. I guess somebody made an adjustment so that it doesn't work any more.
I don't know what I did, but the problem resolved itself. The Actions showed up as before. Thanks for your help.
That's why I pointed you to the wiki and downloading the latest Powershell script because the "adjustment" was made with v6.7 and later
I don't know what I did, but the problem resolved itself. The Actions showed up as before.
Great! If this happens again don't forget to post the full error message you get from the Powershell script
All,
Not sure if this is the right way to do this but is anyone familiar with why smart tags stopped working again. I run Logos 6 core engine and an older version of word. Last fall I upgraded to 6 and first noticed it quit working. For some reason it resolved itself. After several calls with no real help. I ran un update recently on both laptops smart tags no longer work on both. Frustrated!
Not sure if this is the right way to do this
A new thread is better.
I ran un update recently on both laptops smart tags no longer work on both
Restarting the computer often fixes things.
Have you tried http://www.logos.com/articleviewer/530 and/or the Powershell fix?
If not successful tell us about your version of Office, whether it is 64-bit or 32-bit and your version of Logos.
