Smart Tags Problem
Comments
-
Fred Greco said:
Is there a way to install it for PowerPoint?
Hi Fred
I can enable it by going into Powerpoint Options, selecting Add-Ins, at the bottom of the screen selecting "Manage Smart Tags" and clicking Go. This enables you to turn on Logos SmartTags. (Hope this is clear, in a rush and haven't got time to include screen shots at the moment)
However, as per your comment on Excel, it provides the ability to open a Bible but not to replace a passage. It would be really useful if the replace feature were there as well.
Graham
0 -
PowerPoint 2010 is not supported for two reasons:
1) It passes single words to our implementation of ISmartTagRecognizer::Recognize, yet tags them as IF_TYPE_PARA not IF_TYPE_SINGLE_WD.
2) It passes null as the Target parameter to ISmartTagAction::InvokeVerb.
Microsoft said that Smart Tags are deprecated in Office 2010, but I didn't expect them to break the internal implementation; it may just be an oversight on their part.
0 -
BillS said:Bradley Grainger said:
Can you check the following key in Registry Editor (as shown in the status bar at the bottom of the window below) and verify that it exists and it has the same value on your system?
Yep. Mine is pictured right under yours.
Anything else you'd like to try? I could be reached all day today if someone would like a peek under the hood...
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Bradley Grainger said:
PowerPoint 2010 is not supported for two reasons:
1) It passes single words to our implementation of ISmartTagRecognizer::Recognize, yet tags them as IF_TYPE_PARA not IF_TYPE_SINGLE_WD.
2) It passes null as the Target parameter to ISmartTagAction::InvokeVerb.
Microsoft said that Smart Tags are deprecated in Office 2010, but I didn't expect them to break the internal implementation; it may just be an oversight on their part.
Thanks Bradley. It's OK if it does not work; I wanted to be sure it was not just me.
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
{Pasted from Word so arrives with the "bafflegab" etc Line)
Late to his
discussion, and same problem. (I am running the 4.1 Beta 10)Used to
have Smart Tags in an earlier version of Word with L3.Now have Word
2007 on new laptop with L3 and L4WHICH OF YOUR STEPS HAVE I MISSED?
Word 2007 has “Smart Tags” option “clicked”
Bradley, I have ensured that I don't have either Logos 4 or
Word running elevated.Bradley’s Smart Tags
log is now in Logos 4 Log Drawer , 6710.L4SmrtTg.zipBradley I have identical Registry key: etc ie. Can you
check the following key in Registry Editor
Mitch’s
suggestion: Mine appears as you have described. Ie I see "Logos Bible Software 4
(Bible References) under the "Active Application Add-ins?Per Rosie: I
have “poke through this thread you'll
find instructions for how you're supposed to be able to get it
working.”Regards, SteveF
0 -
SteveF said:
Now have Word 2007 on new laptop with L3 and L4
Hi Steve,
Smart Tags for L3 runs fine on Office 2007 (both of which I have). But L4 smart tags aren't yet working for some of us. If you've got the log file, sounds like you're similarly affected: it's installed but not yet working.
We're all waiting for a Logos "next step."
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
BillS said:
Anything else you'd like to try?
The most likely explanation for the error you're seeing is that standard COM marshalling isn't working. To repair, try this:
- Open an Administrator Command Prompt
- Enter the following commands:
cd C:\Windows\System32
regsvr32 oleaut32.dll
cd C:\Windows\SysWow64
regsvr32 oleaut32.dll0 -
Bradley Grainger said:
To repair, try this:
HI Bradley,
All commands were successful. Still no wavy line.
Here's the log file:
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Bradley,
Does the Word SmartTags DLL use the COM API to interact with Logos4, or some other methods?
If via the COM API, maybe a tiny stand-alone app (outside of Word), that connects to Logos4, and attempts to access John 3:16 etc, might help determine failings such as above?
Clearly, if the COM API can't talk, any kinds of messing around with settings, macros, or otherwise of Word will change nothing.
(And if SmartTags is NOT using the COM API, then nothing I've said here is very useful.)
A little related: Is the limit against SmartTags in Word-64bits, a limit on Word-64 using a 32-bit DLL, rather than some limit in COM API or Logos4 itself?
[Off Topic of SmartTags: And if you are still reading: Would a 64-bit build of Logos4 and/or the SQL subsystem deliver any useful performance gains?]
0 -
Bradley Grainger said:BillS said:
Anything else you'd like to try?
The most likely explanation for the error you're seeing is that standard COM marshalling isn't working. To repair, try this:
- Open an Administrator Command Prompt
- Enter the following commands:
cd C:\Windows\System32
regsvr32 oleaut32.dll
cd C:\Windows\SysWow64
regsvr32 oleaut32.dllBradley, I tried this too, and I have the same error messages in my SmartTag.log file: 5265.SmartTag.log
0 -
Rosie Perera said:
Bradley, I tried this too, and I have the same error messages in my SmartTag.log file: 5265.SmartTag.log
OK, so much for that theory. It's maybe a typelib registration error... or... something else. I'll take a look and see what might be wrong.
0 -
JimT said:
Bradley,
Does the Word SmartTags DLL use the COM API to interact with Logos4, or some other methods?
If via the COM API, maybe a tiny stand-alone app (outside of Word), that connects to Logos4, and attempts to access John 3:16 etc, might help determine failings such as above?
Clearly, if the COM API can't talk, any kinds of messing around with settings, macros, or otherwise of Word will change nothing.
(And if SmartTags is NOT using the COM API, then nothing I've said here is very useful.)
A little related: Is the limit against SmartTags in Word-64bits, a limit on Word-64 using a 32-bit DLL, rather than some limit in COM API or Logos4 itself?
[Off Topic of SmartTags: And if you are still reading: Would a 64-bit build of Logos4 and/or the SQL subsystem deliver any useful performance gains?]
The Word Smart Tags DLL implements all its functionality by calling the Logos 4 COM API. (This is why Logos 4 must already be running; we felt it would be rude to start Logos 4 in the background whenever you open Word.)
Creating a test program is a good idea. It would probably return the same error codes as the Smart Tag addin (that's loaded in Word), but an additional source of data would still be useful.
The restriction on smart tags in 64-bit Office is an OS limitation: a 64-bit process is unable to load a 32-bit DLL. If we created a separate 64-bit Smart Tag DLL, we could support 64-bit Office, but it would complicate the installer for a rare situation (64-bit Offfice is not installed by default, and Microsoft recommends against it).
A 64-bit build of Logos 4 would probably eliminate Out of Memory Exceptions because it would increase the available address space from 2GB to 16TB. (Even if you have 32GB of RAM, Logos 4 is limited to 2GB due to the limitations of 32-bit processes, and the actual limit is closer to 1GB due to the overhead of .NET and other DLLs that are loaded.) However, allowing the application to use an (effectively) unlimited amount of memory isn't necessarily a good idea; on most systems it could cause a huge amount of paging, which would drastically slow down the application. Additionally, slowly leaking memory would slow down each .NET garbage collection, causing the application to run slower and slower over time. Sticking with a 32-bit process is probably better because it requires us to keep our long-term memory usage low, leading to an overall better application.
Furthermore, in a 64-bit process, each pointer (or reference, in .NET) is 64 bits, rather than 32, which (simplistically) doubles the memory usage of the application. The 32-bit process might run just fine on a computer with 2GB of RAM, but the 64-bit process could require 3-4GB just to achieve the same performance. This may not be a big concern once all new desktop computers are shipping with 8GB+ of RAM, but it's still an issue right now.
It's not clear that running a 64-bit process delivers obvious immediate performance gains. In some cases, loading and processing 32-bit data incurs a performance penalty.
Finally, it complicates the installer (and doubles the download size!) to deliver both 32-bit and 64-bit builds of the application. We may consider it again in future, but right now, delivering a single 32-bit build of the application seems like the optimal approach.
0 -
Bradley Grainger said:
The Word Smart Tags DLL implements all its functionality by calling the Logos 4 COM API. (This is why Logos 4 must already be running; we felt it would be rude to start Logos 4 in the background whenever you open Word.)
Creating a test program is a good idea. It would probably return the same error codes as the Smart Tag addin (that's loaded in Word), but an additional source of data would still be useful.
Bradley,
Thanks for the feedback and answers.
I would knock up a quick COM API stub myself, but I wont have time until after Friday due to work demands. I expect someone there could knock out the few lines required in VC# or VB. It only needs a single button and a text box. Attempt to make an app object to the COM API and pull back the version number and the text to John 3:16 or something. It will be interesting if it would then work for Rosie. If yes, look into Word issues. If not, maybe Reflection and manually loading the DLL would give you more complete error reporting than calling it "directly". I expect you have all the good debugging toys and goodies there.
Re the possible 64-bit build of Logos4: This sounds like a task to give one of the interns to explore. Rather than add it into the main installer, make a 64bit one as a seperate build. It could warn if you had less than 6 GB ram or whatever. As for any memory leaking or related, I'm sure there is a way to get on top of that too. I skim-read your blog post of memory-leaks and memory-presure for bitmap graphics. There must be some way to let some of the Logos modules or code-blocks to track their usage in some ways for your internal builds. I get "Not Responding" messages very common when I open something new, so maybe thats a memory thing and garbage-collection needs to run or something. I have yet to attempt to monitor the threads or memory usage of the Logos4 application. Maybe I'll do so some time ...
Sorry to other readers here, for all the geek-speak.
Regards,
Jim.
0 -
Bradley Grainger said:
The restriction on smart tags in 64-bit Office is an OS limitation: a 64-bit process is unable to load a 32-bit DLL. If we created a separate 64-bit Smart Tag DLL, we could support 64-bit Office, but it would complicate the installer for a rare situation (64-bit Offfice is not installed by default, and Microsoft recommends against it).
Hi Bradley,
I'm running Vista 64, even though I'm running Office 32. I think Rosie may be doing the same, if I remember right. Is there any possibility that the 64bit OS is throwing things off?
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
BillS said:
Hi Bradley,
I'm running Vista 64, even though I'm running Office 32. I think Rosie may be doing the same, if I remember right. Is there any possibility that the 64bit OS is throwing things off?
I run Win 7 64 bit version and Office 2010 32 bit (Czech version [:)] ) and it works.
Bohuslav
0 -
Bohuslav Wojnar said:
I run Win 7 64 bit version and Office 2010 32 bit (Czech version
) and it works.Hi Bohuslav,
Good to hear for W7... Anyone running Vista 64 with L4 Smart Tags successfully installed?
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Bradley Grainger said:
OK, so much for that theory. It's maybe a typelib registration error... or... something else. I'll take a look and see what might be wrong.
Beta 11 installed.... still no wavy line... log attached.
3603.SmartTag.logGrace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
BillS said:
I'm running Vista 64, even though I'm running Office 32. I think Rosie may be doing the same, if I remember right. Is there any possibility that the 64bit OS is throwing things off?
A 64-bit OS does make COM registration work slightly differently, so it is a possibility that it's causing the problem. However, we've tested here with Vista x64 and Windows 7 x64 and can't reproduce the problem.
0 -
Hi Bill,
I've written a standalone diagnostic program to check various registry values and try to start the Logos 4 COM server in the same way that the smart tag does; it may provide some additional information on what's preventing the smart tag working on your system.
To run it, open a regular command prompt and execute the program. It will print its results to the screen by default; you can send them to a file by running (for example):
SmartTagDiagnostics.exe > C:\Temp\Diagnostics.txtIt will try to communicate with Logos 4, so please have Logos 4 running before you run the diagnostics. You can then post the Diagnostics.txt file here.
0 -
Bradley Grainger said:
Hi Bill,
I've written a standalone diagnostic program to check various registry values and try to start the Logos 4 COM server in the same way that the smart tag does; it may provide some additional information on what's preventing the smart tag working on your system.
To run it, open a regular command prompt and execute the program. It will print its results to the screen by default; you can send them to a file by running (for example):
SmartTagDiagnostics.exe > C:\Temp\Diagnostics.txtIt will try to communicate with Logos 4, so please have Logos 4 running before you run the diagnostics. You can then post the Diagnostics.txt file here.
Thanks, Bradley. I've run this on my machine, and here's my diagnostics.txt file with a couple of failures in it towards the end:
0 -
Bradley Grainger said:
Hi Bill,
I've written a standalone diagnostic program to check various registry values and try to start the Logos 4 COM server in the same way that the smart tag does; it may provide some additional information on what's preventing the smart tag working on your system.
To run it, open a regular command prompt and execute the program. It will print its results to the screen by default; you can send them to a file by running (for example):
SmartTagDiagnostics.exe > C:\Temp\Diagnostics.txtIt will try to communicate with Logos 4, so please have Logos 4 running before you run the diagnostics. You can then post the Diagnostics.txt file here.
Thanks, Bradley. Here's my log...
5736.Diagnostics.txtGrace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Rosie & Bill,
Both your log files show the same error message as before (which I'm unable to duplicate here so far). I've added some more diagnostics to the program. Please run the attached version and report back--thanks!
0 -
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Hi Bill,
We have finally managed to reproduce the problem here. The fundamental issue is a bug in Windows Vista related to UAC and per-user COM registration.
We know of three workarounds:
- Upgrade to Windows 7 (this is what I was primarily testing with, and is why I couldn't reproduce the bug)
- Enable UAC
- Install the KB971138 hotfix for this issue (we haven't tested this, but it's supposed to correct this problem)
0 -
Yea Bradley !!!!!!!
Yea Bill !!!!!!!
Praise the Lord!!!!!!!!!!!!!!!!!!!!!
0 -
Bradley Grainger said:
Install the KB971138 hotfix for this issue (we haven't tested this, but it's supposed to correct this problem)
L4 Smart Tags are now working on my system. The hotfix worked.
PTL! Bradley, you're the best! Thanks SO MUCH!
Blessings to you!
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
-
Bradley Grainger said:
Hi Bradley, Ed, & Todd, I can see why Logos is such a great place to work. You folks make a great team. You're the best!
Blessings to you all,
Bill
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
And let's not forget to thank Chris Jackson for blogging about the problem, Microsoft for creating the hotfix, and Google for finding them both.
0 -
Thanks, all! It's working for me now, too. And I will surely be making a note of this thread in case others report problems with SmartTags on Vista in the future.
0
