General Error / Central Configuration AOO 4.1.3

[White Phoenix]

I install AOO 4.1.3 on Linux and Windows 7. Everything seemed okay, but the Windows version complained about the Java not being right. However, it closed before I could go into Tools and fixed it and refuses to open. I even re-installed and disabled the user profile. It still gives the following message:

A general error occurred while accessing your central configuration.

This gives me no clue as to what it wants, and for a while I thought I had been tricked into downloading a fake, but no there really is a 4.1.3 and I did go to the official download site. So what is the “central configuration” that is being referred to?

UPDATE: I just tried to access the LibreOffice that is installed on my Windows 7. It is giving the same error message. Fortunately, whatever is wrong only affects Windows, not Linux.

[Bill]

For the Java problem, try the solution posted in Re: JRE not found (Java 8). If that doesn't also fix the "Central Configuration" problem, try searching the forum for a solution.

[White Phoenix]

For the Java problem, try the solution posted in Re: JRE not found (Java 8). If that doesn't also fix the "Central Configuration" problem, try searching the forum for a solution.

So it’s a bug. I just figured AOO needed to be pointed to the correct file which is why I wasn’t looking for that fix. It didn’t seem to be a real problem.

So, I will replace the 64 bit DLL file with the 32 bit version and see what happens. Thank you for pointing out that the Java problem was more serious than I thought.

Yes, that was the problem with AOO not wanting to run also. I had to replace the bad file in the program subfolder though. There were a lot of 32 bit MSVCR100.DLL files throughout my system. So I guessed that AOO had to have it in its folder. LibreOffice still doesn’t work, but I will get around to that eventually... maybe.

[Bill]

Windows should search for msvcr100.dll in the program subfolder first, then look in C:\Windows\SysWOW64 if it isn't found in the program subfolder. If it's only being found when it's in the program subfolder, then you may need to run the System File Checker. The msvcr100.dll may even be removed from the program subfolder in the next release.

[White Phoenix]

Thanks I will check, although of all the places msvcr100 was, I don’t recall it being in SysWOW64. So naturally if it isn’t there, it cannot be found there. I have the file backed up in my Archives folder in any case.

I am in the Windows side of my system now. Um. Wouldn’t a 32 bit DLL file be in System32 instead of SysWOW64?

[Bill]

...of all the places msvcr100 was, I don’t recall it being in SysWOW64. So naturally if it isn’t there, it cannot be found there. I have the file backed up in my Archives folder in any case.

I am in the Windows side of my system now. Um. Wouldn’t a 32 bit DLL file be in System32 instead of SysWOW64?

No. The 32-bit DLL would be in System32 on a 32-bit system. On a 64-bit system, the 64 bit DLL would be in System32 and the 32-bit DLL would be in SysWOW64. Your signature says that you have a 64-bit system.

[White Phoenix]

On a 64-bit system, the 64 bit DLL would be in System32 and the 32-bit DLL would be in SysWOW64. Your signature says that you have a 64-bit system.

I think you have that backwards, right? The 64 bit DLL would be in WOW64 and the 32 bit DLL would be in System32. The other way around doesn’t make sense.

True, I have a 64 bit system, but AOO is a 32 bit program. So it everything about it is treated as if you are using a 32 bit system. That is why the 64 bit DLL in its program folder is causing the problems. As you pointed out the program would look in its own program folder first for any DLL files it needs.

Just putting the 32 bit DLL file in WOW64 would be wrong for three reasons. First, AOO would look in its program folder and find the 64 bit version and fail. Second, 32 bit files do not go in WOW64, but in System32. Third, other programs may be using the 64 bit version, so if you replace it with the 32 bit version, that is going to cause a problem.

If the 64 bit DLL file is deleted from the 64 program file AOO should then look in System32. If it isn’t there, it might look in WOW64, but that would not make sense for a 32 bit program to look for a 32 DLL file there.

But if you are going to delete the 64 bit version from the AOO program file, why not just put the 32 bit version (which would have been installed there by AOO anyway) in the program folder? So that is what I did.

[jaragon]

On a 64-bit system, the 64 bit DLL would be in System32 and the 32-bit DLL would be in SysWOW64. Your signature says that you have a 64-bit system.

I think you have that backwards, right? The 64 bit DLL would be in WOW64 and the 32 bit DLL would be in System32. The other way around doesn’t make sense.

No, actually, he doesn't have it backwards. 64-bit DLLs would be in System32 and 32-bit DLLs would be in SysWOW64. "WOW64" stands for "Windows-on-Windows 64" and it's the component that allows 32-bit programs to run on a 64-bit system, so the things in this folder are for 32-bit programs despite the name.

See http://www.samlogic.net/articles/32-64- ... swow64.htm for an explanation of the SysWOW64 folder.

[White Phoenix]

Then WOW64 is a really bad name since it is misleading, and System32 should have been renamed to reflect that it is for 64 bit system files. Or they should have just not separated them. I have had 32 bit programs that are coded to automatically install in Program Files. They run just fine. Oh well, this is one of the reasons why I have been switching to Linux.

[Bill]

Microsoft has published Information online about the use of System32 for 64-bit and SysWOW64 for 32-bit in 64-bit Windows. A Google search including the two terms should clear up any misconception.

Running 32-bit Applications

File System Redirector

[White Phoenix]

There is no misconception on my part. SysWOW64 is for 64 bit and System32 is still for 32 bit, just as System is for whatever System was for. When you install programs that have 64 bit DLL files those files go to SysWOW64.

[Bill]

Read the articles. The name WoW64 stands for Windows 32-bit on Windows 64-bit. While System32 if for 32-bit on 32-bit Windows, on 64-bit Windows, System32 is for 64-bit and SysWoW64 is for 32-bit.

[White Phoenix]

And yet, my programs still work.