FileLoadException: Could not load file or assembly 'Libronix. COMException 0xB1 : The application has failed to start because its side-by-side configuration is incorrect. Main String[] astrArgs. For Method 2 it is important that your original installation is the same version you are installing. If not the case then you will have to use Method 3. That has nothing to do with this issue but just so you know! If you have installed. NET 4. It is best to completely uninstall Logos4 Prerequisites as well from Control Panel.
Remove all traces of the Logos4 folder except for your backup which should be in another folder. Set up Diagnostic Logging and install as per Method 2 or 3 you can still do a custom install with Method 3. Make sure you install from an Administrator user account but do not right click and "run as Administrator".
Thanks Dave for your response. I am not sure about. NET 3. NET anything in "Programs anf Features". I was using method 2 because I had to the best of my knowledge, deleted all reference to Logos 4 in the registry before I installed it again. I also did use the control method of starting. I will try the logging methods to get more details which I will upload as soon as I can.
Actually the log info that I gave in my first post is all that appears when I use the Control key stat method. I'll check out the other methods to see if they give anything more.
I made sure that the registry was showing the correct settings for logging and started Logos again with the same result. I get two files one called Logos4. These are the details in my original post with no changes in the result.
There is no indexing log as it hasn't got past being able to start. One question I have is how do I know that I have successfully deleted the prerquisites. I ran uninstall on prerequisites in "Programs and Features" but is there some way of knowing it is completely gone. Sorry to bombard you like this, I guess that its what happens when I'm at the other side of the world to most who might post here.
Note: you should start a new thread if a thread s is older than 2 months or does not have feedback confirming the recommended fix! Do this by calling and asking for Technical Support remember to add the international code for the US if dialling from outside North America. Alternatively you can email Tech Support, see Contact for email address. Beta and unsupported releases are discussed in appropriate forum, refer to The Forums above.
Logs record the activity of the software in a way that assists identification of the feature or module that is causing a problem. Logs can be found in the Logos Log Files folder in My Documents and they should always be uploaded to the forum i. Logos will create logs automatically if it crashes. In other situations you have to enable logging, then rerun Logos to reproduce the problem see Diagnostic Logging for more details. In some situations you may be requested to provide a Crash Dump.
Crashes are one of the most difficult issues to diagnose, so it may take a little time to work out the problem. Logos should create logs when it crashes, so upload the logs or obtain them as mentioned above. Prefix the title of the thread with Crash: e. Crash: whilst searching NAS bible. Note that a complete Logos crash log will contain at least 10 lines.
Logs are produced automatically for this activity e. So upload them to the appropriate forum and quote any error message from a dialog box. Prefix the title of the thread with Crash: or Bug:.
A common error when updating the software is:- Error writing to file The best solution is to modify the Logos folder ownership , but you may have to reinstall Logos. Some problems can be resolved by simply restarting Logos or rebooting the computer, so try these first. Wherever possible illustrate your problem with a screen shot.
0コメント