Don't know if it's 7.9 SR-1 or the /ngen speed up script, but SmartTags has been destroyed again in Logos. Is anyone else experiencing this?
Mine were with some recent update, ran their shell program to fix it, & forgot about it. It has happened so often I have numerous fixes downloaded & installed & can always find one of them.
Grace & Peace,BillMSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050MaxiPhone 12 Pro Max 512GbiPad 9th Gen iOS 15.6, 256GB
I'm experiencing something very strange indeed. I have Logos installed on an SSD drive, the D: drive. I tried running the PowerShell script to fix the loss of SmartTags, and it first indicated it couldn't find the 64-bit dll. I found that, put it in the Logos/System path and ran the PowerShell script again. This time it says it was successful. However, as an Action, Logos Bible Software does not show up as an option in Word/AutoCorrect/Actions, and the 64 bit dll is no longer in the path I placed it in. Completely gone. Any ideas? Many thanks if anyone can help.
T.P. Johnston: as an Action, Logos Bible Software does not show up as an option in Word/AutoCorrect/Actions
Check this support link.
- Office 2013 works for current Office version.
T.P. Johnston:I have Logos installed on an SSD drive, the D: drive... and the 64 bit dll is no longer in the path I placed it in.
Did you put it in Logos\System on D:\ drive? When you run the PowerShell script with -Office64Bit does it find the dll?
Dave===
Windows 11 & Android 13
Thank you for your response! Yes, I did put the dll in D:\Logos\System, and the PowerShell script with -Office64Bit does find the dll, at least it says it was successful. But once that is done, when I navigate to D:\Logos\System the dll is no longer there. What is interesting is that I discovered both dll files for SmartTags is found in D:\Logos\Pending folder. However, editing the script for that folder yields only error messages.
Also, I am aware of how to enable Actions in Word, but Logos Bible Software is no longer listed as a possible action.
Any further ideas, much appreciated!
Now this is really messing with my mind! Yesterday, I tried rebooting the computer, and the only thing in the Logos/System folder was Logos. Whenever I copied the 64 bit dll there, and ran the PowerShell script, it would indicate it registered, but the actual dll file would be missing. Also, Logos Bible Software was not available as an Action in Word/Options/AutoCorrect/Actions. Today, in the Logos direction, there is no Pending folder, and everything is populated in the Logos/System folder. I ran the PowerShell script again, it successfully registered the dll, and the Action became available and checked in Word, but it still does not actually work.
Btw, I have the exact same computer system at my church office, and while SmartTags did not work, so I tried running the PowerShell script on it, but it did not succeed, however, SmartTags suddenly started working again.
I am completely confused!
T.P. Johnston: Today, in the Logos direction, there is no Pending folder, and everything is populated in the Logos/System folder.
That folder should not have been visible if you had restarted Logos for a (pending) software update - rebooting accomplished that.
T.P. Johnston:I have the exact same computer system at my church office, and while SmartTags did not work, so I tried running the PowerShell script on it, but it did not succeed, however, SmartTags suddenly started working again.
After an update, when registered or re-registered as an Action, I have found Smart Tags can initially take some seconds to work, or will work after closing and re-opening Word.
Is there a way to re-register the Action, since I have Logos installed on an SSD D: drive, there is no AppData except for an installation folder on the C: drive? In other words, for the Command Prompt register command, there is no such path for "%AppData%D:\Logos\Logos.exe" /register
T.P. Johnston: Is there a way to re-register the Action, since I have Logos installed on an SSD D: drive, there is no AppData except for an installation folder on the C: drive? In other words, for the Command Prompt register command, there is no such path for "%AppData%D:\Logos\Logos.exe" /register
If Logos is installed in D:\Logos, the command is D:\Logos\Logos.exe /register. But the PowerShell script knows how to get the path, so you aren't gaining by doing it manually.
Thank you, as always, for your expert help, Dave! Looks like for now I'm stuck with a properly executed PowerShell script, Word Action that is available, but simply not working. I'm grateful for your taking the time to reply!
Dave, thank you, thank you. Remembered something from a previous post of yours elsewhere about trying a Control Panel repair of Logos. That fixed my problem!
Glad to be of help