Verbum stand-alone product? / Crash on startup

Hi I recently purchased your Verbum Foundations+ product and have been unable to get it running at all. Reading through some of the support information it occurred to me this may not be a stand-alone product and requires Logos 5 or something else to function. Is this right?

Find more posts tagged with

Comments

abondservant

I am not a verbum user, so perhaps someone will pop up that knows better than I. However I do recall someone saying that once l5 is installed one can change it into verbum and back again if one so chose... I would recommend installing l5, and then using the command to switch the branding over to Verbum. My understanding is at this juncture L5 is the "all features" version, and Noet, vryso, etc have a lesser feature set. Verbum is unique in that it has a better way of displaying some sort of product or other that my protestant tradition does not use. Lectionaries? Or something like that... I don't recall.

MJ. Smith

You do have to install either Logos 5 or Verbum. Instructions should have come with Verbum Foundations + which is a base package. When you say you are unable to get it running, what is it that you are trying to run (name of file)?

Travis Coles

https://community.logos.com/discussion/comment/577960#Comment_577960

Okay that's good to know (I don't own Logos in any capacity). I've purchased and downloaded the Verbum installer, gone through the install process and when I run Verbum.exe the title banner shows up, it flicks briefly to the login page but before I can do anything the program crashes.

The reason I questioned whether I was missing half the software is that the log files (attached) indicate there are modules missing. I have tried redownloading the installer and re-installing the software multiple times without luck.

8625.VerbumLogs.zip

MJ. Smith

https://community.logos.com/discussion/comment/577964#Comment_577964

If I recall correctly there is a prerequisites install that you need to run before the Verbum install.

Travis Coles

https://community.logos.com/discussion/comment/577968#Comment_577968

Do you know what that might be? There is nothing mentioned in my order email, the System Requirements page, Installation Guide or FAQ's which allude to any additional software. This morning I did update the .NET Framework to see if that fixed the issue, but no luck.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/577974#Comment_577974

This morning I did update the .NET Framework to see if that fixed the issue, but no luck.

Welcome [:D]

Verbum uses .NET Framework 4.5 or newer.

Verbum install => https://www.logos.com/support/verbum/install

Does Control Panel - Programs and Features have "Logos 5 Prerequisites" or "Verbum Prerequisites" ? If not, suggest uninstalling Verbum

Thread => "Logos 5 Prerequisite" program includes replies from Logos employees about prerequisites.

Curious about user account for Verbum installation ? (administrator does not work since Verbum has some user specific files, even when choosing custom install)

Keep Smiling [:)]

Travis Coles

https://community.logos.com/discussion/comment/577993#Comment_577993

Hi Keep Smiling,

I have followed that install process. Actually, Programs and Features list both 'Verbum' and 'Logos 5 Prerequisites' in the list, I assume this is correct? I have tried multiple combinations of uninstalling and reinstalling them without success.

Thanks for your suggestions, I will keep trying different things.

Regards,
Travis.

Travis Coles

https://community.logos.com/discussion/comment/578003#Comment_578003

Okay, I seemed to have fixed the issue. I found that the Verbum log files referred to an invalid registry entry which pointed to explorerframe.dll.

I performed two steps, one or both of which contributed to fixing the issue.
The first was to perform a windows system file checker. This can be done by going to Start - Run and typing in 'cmd'. Once the dialogue comes up, type 'sfc /scannow'. This will scan your system files and attempt to locate corrupt or invalid references and repair them. This is a fairly straight forward function of Windows.

Secondly, I use a free Registry Cleaner to scan and remove invalid registry references. This can be a little complex for a normal user, but doing a quick Google search can give you the instructions you require. In my case, I used a product called Wise, but there are a few out there.

This allowed me to login to Verbum and begin downloading my library.

Dave Hooton

https://community.logos.com/discussion/comment/578011#Comment_578011

I found that the Verbum log files referred to an invalid registry entry which pointed to explorerframe.dll.

That is a valid registry entry for Logos 5 in so far as the dll does exist. If it is considered a "system file" (being needed for Windows Explorer!!), then sfc would replace it from Windows\winsxs as the log message states "could not be found".

The diagnostic is too technical/complex for the majority of Logos users, so congratulations for your efforts.

Dan Francis

https://community.logos.com/discussion/comment/578013#Comment_578013

I am glad you have it working now...and all i can say is thank God I am on a mac (not saying macs cannot have issues, but usually less complex to fix than what you described).

-Dan