[ACK] Smart Tags broken in 6.3 SR1

However, the first time I attempted your fix I had a space between Remote and Signed and it did not work. 

That is unfortunate that the rendering of RemoteSigned in the forum post appears to have a space in it, in fact it does not! I suppose remotesigned would not have that issue and would work just as well. 

I'm glad it worked for you!

Bryan

I am also having issues applying the fix... my system does not like the command please see the attached screen shot.  I need help!!

The error message you are getting point to a path problem.

Are you running 32 bit or 63 bit office? If 32 bit then try running the Powershell available in Bryan's post 

I´m running the 32 bit office, so I will try the Powershell.  

Thank you very much!!

Blessings,

Nelson A.

Bryan,

My name is Nelson Aguillon, and I just tried running the Powershell. It failed.  Please the attached screen shot.  

Thank you,

Nelson A.

My name is Nelson Aguillon, and I just tried running the Powershell. It failed.

Does the path to ...\Logos5 exist? Does the folder 6.3.0.0074 exist?

I will check and post my reply.  

Thank you,

Nelson

Dave,

I did a search for the two items (I hope I did it correctly, I am not an expert at this) and I took screen shots of the results.

Thank you,

Nelson

I'm not sure why PowerShell failed as the Logos folders do exist. Does LogosCom.exe exist in the 6.3.0.0074 folder?

Brother Dave,

There is only one file inside the folder.  Please take a look at the attached screen shot.

Thank you,

Nelson

The smart tag doesn't appear to be the correct version, never mind it being the only file!

Update to the latest version 6.4 as that will provide a new 'system' folder and try PowerShell again if the update itself does not fix Smart Tags

Dave,

Just making sure... update the whole Logos application?

Nelson

Correction,

I´m actually running this version... 

Logos Bible Software 6.4
6.4.0.0037

Nelson

Smart Tags should now work from files in the folder 6.4.0.0037

No, Dave.  I started having the problem when I upgraded to version 6.4.

I am right where I started

Nelson

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. 

1. Run PowerShell as Administrator (Windows key, type PowerShell, right-click on Winodws PowerShell in the list and choose Run as administrator, click Yes on the User Account Control dialog). In the PowerShell window, type Set-ExecutionPolicy RemoteSigned <Enter>. Hit Y <Enter> to make the change. Close PowerShell.
2. Download the RegisterSmartTags.ps1 script from http://downloads.logoscdn.com/LBS6/Support/RegisterSmartTags.ps1.
3. In Windows Explorer, find the script, right-click and choose Run with PowerShell. Since the script is signed by Logos Bible Software, choose Open from the Open File - Security Warning dialog, if displayed.
4. The script calls RegSvr32.exe to register the Logos Smart Tags dll, L4SmrtTg.dll, which should display a RegSvr32 dialog message similar to, "DllRegisterServer in C:\Users\Bryan\AppData\Local\Logos\6.3.0.0074\L4SmrtTg.dll succeeded.", click OK.
5. The PowerShell window should list details about registering, ending with the message "Finished successfully. Hit a key to exit..." Logos COM and Logos Smart Tags for 32 bit Office should now be registered.
6. If you see an error message, such as "Failed to...", please post back here and I'll check it out, otherwise hit any key to exit PowerShell.

You can also register COM and Logos Smart Tags for Verbum and Noet:

1. Open PowerShell (Windows key, type PowerShell and click)
2. type cd <path-to-RegisterSmartTags.ps1> <Enter>, e.g. cd C:\Users\Bryan\Downloads <Enter>
3. type RegisterSmartTags.ps1 -Noet <Enter> or RegisterSmartTags.ps1 -Verbum <Enter>

Hopefully this script will help resolve any lingering COM registration issues. Please let me know if you have problems or questions.

Thanks,

Bryan

Nelson, smart tags were not working for me in Logos 6.4. I followed the instructions above and they are now working. I recommend following Bryan's instructions.

IT WORKED!!!

I am happy again [:)]

Thank you Timothy and EVERYBODY else for your patience and priceless help.

Blessings,

Nelson A.

Good to hear. Good work

Hello everyone,

The original problem came back!!!

The solution to my problem worked TEMPORARILY.  The smart tags option is not available.  I did not make any changes to my system.  The solution worked for a couple of days, and then, it put back to where I started.  

Any ideas from anyone?

Thank you,

Nelson A.

Any ideas from anyone?

What have you done to restore it (from previous suggestions)? What version of Logos and how did you update?

A previous screenshot shows you have a C:\Windows.old folder. Whilst it won't help here, you can permanently delete that folder as it is a previous version of your Windows operating system.

Never mind, Dave.  

I was able to reapply Ryan's fix and the issue was resolved, again [:)]

Hopefully, it will stay that way.  

Thank you for the suggestion about the Windows.old file.  I got rid of it also.  

Blessings,

Nelson 

I was able to reapply Ryan's fix and the issue was resolved, again 

I don't understand why it was necessary, but create a new thread should it reoccur.

Friends,

My smart tags failed again after a recent update, and this plan worked beautifully to restore that critical function. 

Thanks!!!

Paul

6.4 SR2 broke my Smart Tags, too. Since I executed the script right AFTER updating to SR3 (I couldn't tell from L6's notification message whether it was a resource update or a software update, & I was expecting resources), I don't know which fixed the problem Either way, it's fixed now.

OK, I have joined the broken Smarttags club at Logos. For me, it is now broken with 6.4 SR-3. I am running a Windows 7 64 bit system with 64 bit Office 2013.

I think I've tried everything. I tried registering L4SmrtTg.dll again. It seemed to register OK. But when I right click a reference Word "stops responding" for several minutes before finally coming out of the "waiting" and nothing has happened.

I tried using the powershell script. Still broken.

I tried registering LSmtTg64.dll, and I get the message that it successfully registers, but Word 2013 never sees anything except the L4SmrtTg.dll

I know that the right click of references worked fine up until a few weeks ago. I can only surmise that 6.4 SR-3 breaks the feature again, but it seems no one else is commenting about it in the forum.

I would appreciate any help I can get. I don't use the feature every day, but I do have a project right now where it would save me a lot of work and hassle.

Thanks.

Bob Landon

OK, I have joined the broken Smarttags club at Logos. For me, it is now broken with 6.4 SR-3. I am running a Windows 7 64 bit system with 64 bit Office 2013.

It's also broken for me on a similar system with 32 bit Office 2013 and it was working in previous versions.

I have tried ALL the fixes!

This is no help, but smart tags are working for me with 6.4 SR-3, 32 bit MS Office and Windows 8.1. They were broken previously and I used Bryan's fix (above) at the end of June.

The first time I commented on my problems with smart tags I think I may have misdirected the post. Here is what I wrote:

OK, I have joined the broken Smarttags club at Logos. For me, it is now broken with 6.4 SR-3. I am running a Windows 7 64 bit system with 64 bit Office 2013.

I think I've tried everything. I tried registering L4SmrtTg.dll again. It seemed to register OK. But when I right click a reference Word "stops responding" for several minutes before finally coming out of the "waiting" and nothing has happened.

I tried using the powershell script. Still broken.

I tried registering LSmtTg64.dll, and I get the message that it successfully registers, but Word 2013 never sees anything except the L4SmrtTg.dll

I know that the right click of references worked fine up until a few weeks ago. I can only surmise that 6.4 SR-3 breaks the feature again, but it seems no one else is commenting about it in the forum.

I would appreciate any help I can get. I don't use the feature every day, but I do have a project right now where it would save me a lot of work and hassle.

Thanks.

I've tried everything suggested in the thread, but without success. I am hoping there will eventually be a solution.

Thanks.

Bob Landon

I've tried everything suggested in the thread, but without success. I am hoping there will eventually be a solution.

After commenting it was also not working for me, it starting working when I tried it later that day!

I've tried everything suggested in the thread, but without success. I am hoping there will eventually be a solution.

After commenting it was also not working for me, it starting working when I tried it later that day!

This may not have been the case with you, but sometimes I think smart tags aren't working and then remember that they only work when Logos is running.

It's a good reminder, anyway, that Logos has to be running!

This is a call for help! I have a similar problem as others in this thread, but when I run the registersmarttags script in Powershell, I get this error message.

I am using Logos 6 on a 64-bit machine.

That implies a registry problem. Can you run Logos ok?

If you open the registry editor, Regedit, expand HKEY_CURRENT_USER, expand SOFTWARE, then click Logos4, what values appear against InstallDirectory and InstalledVersion? Example

Thanks for the response, Dave Hooton!

I can run Logos, but I'm in a location at the moment with an expensive internet connection. I have automatic updates turned off. I had to recently re-install everything on my computer, including Logos 6. Logos wants to download 2.3GB of updates. I imagine that when I have completed that step, this current problem should work itself out and I'll be able to register Smart Tags.

After my earlier post, I followed the steps in this thread and got the smart tags successfully registered on another machine of mine which was having similar trouble. Paratext and Logos are now communicating on that machine. But, the wireless is dead on that one.

I live in Papua New Guinea. The internet cost here for 2.3GB will be about U$40.00. Ouch!

Steve

to answer your previous question about the registry, I have only two entries under Logos4 as shown

My current version of Logos 6 is 6.3.0.0056.

to answer your previous question about the registry, I have only two entries under Logos4 as shown

The PowerShell script fails because InstalledVersion is missing. You need to update to the latest version, 6.5 and that should correct the registry.

To avoid downloading, you can copy resources from the other installation onto a removable drive and use the Scan command as follows

Scan \Resources

where (or E:, etc) is the removable drive and Resources is the folder with the resources.

Hi Dave,

Thanks for this information. How does one go about copying the Logos resources onto a removable drive? I would need to know where they're stored.

How does one go about copying the Logos resources onto a removable drive? I would need to know where they're stored.

See https://wiki.logos.com/Installation_and_Indexing_Questions#Where_does_Logos_install_resources.3f  Note that your "Logos" folder is called "Logos5", from your previous screen shot.

PTL! It worked. You have been extremely helpful, Dave. You have saved me a from a very expensive download.

I now have Logos 6.5 SmartTags registered, and Paratext is communicating with Logos too. God is GOOD.

Many Thanks,

Steve

Just wondering about the title of this post. What does ACK mean? Is it just a computer geeks way of saying "dang it" or does it actually stand for something?

Just wondering about the title of this post. What does ACK mean? Is it just a computer geeks way of saying "dang it" or does it actually stand for something?

It's an internal note meaning the post has been ACKnowledged by Logos.

This day I installed Office 16. In Office 2013 smart tags worked very well (in every version of Logos). However it ís impossible for me to get them working in Office 16. Does anyone have the same experience and is there a solution available?

Kind greetings

Hans

This day I installed Office 16

Too soon, as my Office 365 subscription is still on the 2013 version.

I take it you tried the Powershell fix from this thread? If you installed 64-bit Office look at https://wiki.logos.com/Smart_Tags#Smart_Tags_for_64-bit_Office

Have you tried http://www.logos.com/articleviewer/530 under Office 2013? MS may have further deprecated "Actions". What do you see under Word Options >> Add-ins e.g.

Clicking Go.. (for Actions) gets the panel shown in the web page. But Word 2016 could be very different!

This day I installed Office 16

Too soon, as my Office 365 subscription is still on the 2013 version.

didn't know it was out....I must live under a rock these days...my Office365 is 2013 also and this is the first time I've seen any mention of 2016...guess it shows Office has along with most other software has become just an occasional tool for me these days.. Logos is the only software besides web browser that I really use on my computer on a regular basis.

didn't know it was out..

Ditto. It was released on the evening of Sept 22!

I have 32 bit Office current installed (Office 2016), I tried the troubleshooting and I don't get anything in the menus for smart tags.

A screen shot of Word Options >> Add-ins may help + other Word menus

I now have 64 bit installed - not sure why it defaulted to loading Word x32 and not x64. Here is the screen shot:

So I checked, the Additional Actions was now there, which was NOT there for the 32 bit version of Office 2016. So I thought it might work. I saw this next when I tested it:

Not there, yet I see this when I click on options:

These were ok:

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

However it ís impossible for me to get them working in Office 16.

The Logos Smart Tag will need to be updated to indicate support for Office 2016 before it will work in that version. (It will also require Office 2016 to support Smart Tags; Microsoft has been calling that feature "deprecated" for several versions now.)

I'll create a case to investigate Office 2016 compatibility. We'll update https://www.logos.com/articleviewer/530 when support is available. (As currently noted there, smart tags "may not work on versions of Office newer than 2013". I guess we can change that to "will not"...)

Thanks Bradley!