Has anyone else experienced this particular error and have any advice on how to fix it? Every time I try to log into Logos on my computer this happens. I skimmed through some of the other forums but didn't find this mentioned.
Blessings,
Ken from LU
Has anyone else experienced this particular error and have any advice on how to fix it? Every time I try to log into Logos on my computer this happens. I skimmed through some of the other forums but didn't find this mentioned. Blessings, Ken from LU
Most of us are volunteers although now and again you may see someone with a Logos Symbol indicating that they are Logos Staff.
Ken, I've never heard of this before; and I think if you keep your eyes open, others will be "chiming in," sharing their experience.
Thanks for posting and I hope we can give you a helpful boost of information.
Is there any other information that we should know about? Are you Windows or Mac?
Edit: It is Saturday night of the weekend here in Eastern Canada. The Logos Community Forums do slow down a bit over the weekends; so you may have to be patient waiting for a response.
Just remembered, this is the weekend with the extra hour in it! *smile* Where is LU?
Edit 2: aahhh! Liberty University! Yes!
George, I think Ken is talking about starting Logos 5?!? Ken, could you clarify, please?
Milton, George & Friends,
I'm on my PC using Windows 7. It's my work laptop on which the installed program has always run error-free until about a week or so ago when I started getting this message. I don't recall doing anything at that time that might have altered anything related to Logos. I'm running Logos 5, by the way. I've experienced the same error message while on my campus's network, at home on my own wireless, and from home through my school's VPN connection. It's the same error every time. Since I can't access the program, I don't have access to any help topics in the program itself, so I thought I'd try this forum to see if anyone else had heard of this problem.
I do love Logos 5, by the way. I use it in class sometimes and for my own personal studies a lot. I'm a fan. I just haven't been able to get on lately.
Ken
Hopefully, Ken, someone more technical might come along .......
OR!!! Perhaps some Logos Staff!
Keep your eyes open and your hopes up! I'm an older guy and non-technical! Sorry!
It's my work laptop on which the installed program has always run error-free until about a week or so ago when I started getting this message.
Does your I.T. department update the laptop with security patches through wireless or some other way without you giving it to them? If so, I would say that they have definitely blocked the program the last time that they connected to it.
Perhaps they use a program such as TeamViewer to connect to it.
EDIT: P.S. I get the exact same message when trying to access certain internet sites at work. I can't speak for software though since we have absolutely no ability to install anything that is not authorized ahead of time, and then it is done by the I.T. folks.
Thanks, Rick! I'm pursuing that possibility. I just submitted a work order to see if our IT guys can associate this error message with a security patch or something else they do in their weekly updates they send to my laptop remotely. I'm authorized to install software on my company laptop, but I wouldn't be surprised if there was some inadvertent change that resulted in my inability to access this program. I also e-mailed my colleague who teaches our Logos Bible Software course to see if he or any of his students experienced the same problem. I'll post an update here when I hear back from them. Thanks again for your help.
This is an 'IT person' responding [;)]
You have a Windows desktop or notebook computer which is joined to a Windows Active Directory domain. When you log onto your computer your account is user@some.domain.name rather than user@computername.
What likely (you will need to check of course) is happening is your IT department has implemented a Windows Active Directory Group Policy policy which looks like it is impacting your running of Logos. If this is happening just recently it possibly will be down to the fact that your IT department has (like we have) implemented restrictions on computers to stop running of applications in the user's AppData folder. This folder is commonly used by virus writing ratbags to drop viruses into the folder and execute them as (out of the box) that user folder has less restrictions.
The folder is in this location - C:\Users\Your.Username\AppData. To see on your specific computer open a Windows Explorer window and type (without the quotes) '%appdata%' in the address bar. It will go to your AppData folder which usually you can't navigate to as the folder is hidden.
If you are feeling adventurous you could open a DOS prompt window and type (no quotes) 'gpresult /v'. Which will show you all the group policies enforced on your computer.
I don't run Logos on Windows (Mac user personally) so I don't know which Logos application may be sitting in there. Given that the AppData folder is used to store application specific stuff (including likely by Logos also) it is very likely something is in there which may be a small app that the main Logos 5 application is calling. Or... it may be that the main Logos 5 application was installed into this folder instead of the usual Program Files folder structure.
don't run Logos on Windows (Mac user personally) so I don't know which Logos application may be sitting in there. Given that the AppData folder is used to store application specific stuff (including likely by Logos also) it is very likely something is in there which may be a small app that the main Logos 5 application is calling. Or... it may be that the main Logos 5 application was installed into this folder instead of the usual Program Files folder structure.
don't run Logos on Windows (Mac user personally) so I don't know which Logos application may be sitting in there. Given that the AppData folder is used to store application specific stuff (including likely by Logos also) it is very likely something is in there which may be a small app that the main Logos 5 application is calling. Or... it may be that the main Logos 5 application was installed into this folder instead of the usual Program Files folder structure. I'm not an IT guy, but I do know that there is not a small program in the AppData file that Logos calls—the entire program is located in AppData.
I'm not an IT guy, but I do know that there is not a small program in the AppData file that Logos calls—the entire program is located in AppData.
Well that's going to cause a world of hurt. It's called AppData for a reason — it's meant for data... not executables. Executables should go into \Program Files, you know where... program files are meant to go. I have just confirmed this myself on my Windows 7 virtual machine on my Mac. The default install folder for everything is \Users\Username\AppData\Local\Logos5
Expect to find more people who have Windows machines joined to domains reporting problems with Logos because IT administrators are/will be more aggressively blocking program execution from AppData to stop viruses downloaded from Internet from running. And I can tell you (what I would be saying) that they will refuse to change the IT policy. Logos is in the wrong here - the program files should not be installed in AppData. If they have per user config files telling program how to run then fine they can, and should, be installed in AppData but executables, Logos.exe, not.
Also, the easy way to handle hidden folders is simply to show them. I show hidden folders and system files as well.
In a corporate environment we 'discourage' users from playing with their systems [:P]
So, to summarise:
If they have per user config files telling program how to run then fine they can, and should, be installed in AppData but executables, Logos.exe, not.
I just checked my %AppData% folder, and I have 87 executable files there, including DropBox and Microsoft's own SkyDrive. Chrome used to install there, too. %AppData% is the correct place to install executables that are per-user, not per-machine, as Logos 5 is.
Executables should go into \Program Files, you know where... program files are meant to go. I have just confirmed this myself on my Windows 7 virtual machine on my Mac. The default install folder for everything is \Users\Username\AppData\Local\Logos5 Expect to find more people who have Windows machines joined to domains reporting problems with Logos because IT administrators are/will be more aggressively blocking program execution from AppData to stop viruses downloaded from Internet from running. And I can tell you (what I would be saying) that they will refuse to change the IT policy. Logos is in the wrong here - the program files should not be installed in AppData. If they have per user config files telling program how to run then fine they can, and should, be installed in AppData but executables, Logos.exe, not.
Executables should go into \Program Files, you know where... program files are meant to go. I have just confirmed this myself on my Windows 7 virtual machine on my Mac. The default install folder for everything is \Users\Username\AppData\Local\Logos5
Executables should only go in Program Files for per-machine installations. Logos is--by design--a per-user program, so we do not install there. As per the Windows Installation documentation (http://msdn.microsoft.com/en-us/library/dd765197.aspx), for a per-user installation context, the "ProgramFilesFolder" is defined as being under %LocalAppData%.
If your IT administrator has decided to block the installation of software on your computer, that's a different problem (and I can't see how making our installer install into Program Files would be any better--if anything, that would be more locked down).
Re-installing Logos in a different folder (ideally c:\program files (x86))
I would strongly advise against this. The default security permissions for C:\Program Files (x86) make it essentially read-only (so that installed programs aren't modified by regular users); Logos was not designed for this scenario. Even if you elevated the initial installation to try to get around it, automatic updates and resource downloads would most likely fail in the future.
Logos was designed to be a per-user app that installs in a per-user folder.
