Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

On 10/10/2012 12:06 AM, Jay Lozier
On 10/09/2012 09:02 AM, Carl von Bell wrote:Friends

I got this really strange problem affecting Windows Explorer. I
noticed that it started happening after I installed a data managing
program called FieldWorks and started exporting interlinearized files
into LibreOffice .odt format from within that program. I store my
LibreOffice files that FieldWorks outputs in one folder (there are
other files there too). Sometimes several times in a row if I open
that folder in Windows Explorer then the Windows Explorer crashes and
I get the error below. Sometimes there is no way to get to the files,
except rebooting the system! Otherwise I cannot open the folder to get
to the files. :-(
The funny thing is that I do not even need to click on any of the .odt
files and still the Explorer crashes. And sometimes I can work for
hours and there is no problem.

Another person who also has the same setup, but Win 7, experience
similar things. It is very annoying.

Here is the error message I get. I am not sure if my friend gets exact
the same error but the behaviour is similar.

Windows Explorer has stopped working.
Windows can check online....
Check online ...
Restart the program

Then view problems details.

If you click the View problem details then do you see something like
thisProblem signature:
  Problem Event Name:    BEX64
  Application Name:    Explorer.EXE
  Application Version:    6.0.6002.18005
  Application Timestamp:    49e02a1e
  Fault Module Name:    MSVCR90.dll
  Fault Module Version:    9.0.30729.6161
  Fault Module Timestamp:    4dace4e7
  Exception Offset:    00000000000552d4
  Exception Code:    c0000417
  Exception Data:    0000000000000000
  OS Version:    6.0.6002.
  Locale ID:    1033
  Additional Information 1:    46e0
  Additional Information 2:    4ce498f1e2ebb3719af008d4ef97bedc
  Additional Information 3:    7d05
  Additional Information 4:    729ac305dabb24e28fbe99019ecbbab7

Read our privacy statement: know it is 
possible that it has nothing to do with LibreOffice at
all, but I need to try to start somewhere in resolving the possible
cause. So I wonder does the LibreOffice use the MSVCR90.dll file or
not? If it does, then is there something I could try to do so that
this would not happen again?

Wiindows Vista Pro 64Bit
LibreOffice 3.5.2

Thanks a lot,

According to this 
link is part 
of Visual Studio 2005. I doubt LO uses this library.
My guess is that you have corrupted file.Thanks, JayI uninstalled all instances of Visual Studio 
and rebooted. But the
    problem persists.I searched the web for a solution, but did not find anything that
 talking about the exact same problem, and they also use
    LibreOffice on a Windows 7 64 bit machine. I use Vista 64 bit and
    have the same issue, as have my friend who just recently started
    using LibreOffice. We never experienced this before installing
    LibreOffice.The reply to the report in the link above suggests that it is a
    LibreOffice problem. I tried the free program they suggested,
    ShellExView, but it did not find the MSVCR90.dll.We are trying to finish a project here where 
we rely on LibreOffice,
    so it would be really good to be able to get this solved.ThanksCalle

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.