Issue 94226 - office doesn't start
Summary: office doesn't start
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.0 RC2
Hardware: Unknown All
: P1 (highest) Trivial (vote)
Target Milestone: OOo 3.0
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
: 91661 93696 (view as issue list)
Depends on:
Blocks: 88888
  Show dependency tree
 
Reported: 2008-09-23 11:52 UTC by Martin Hollmichel
Modified: 2013-01-07 15:27 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2008-09-23 11:52:24 UTC
cloned internal issue c158466
crashdebug -- Version: 1.37
retrieving data for id 100018988 using reportmail ... done
MSVCR90.dll could not find checksum in database
USER32.dll could not find checksum in database
kernel32.dll could not find checksum in database
ntdll.dll could not find checksum in database
calling r:\windbg\kd.exe -srcpath
o:\OOO300\src.m5;o:\OOO300\wntmsci12.pro\inc.m5 -y
symsrv*sosymsrv.dll*C:\WINDOWS\TEMP\crashdata-2192-1221338280.pathes -z
C:\WINDOWS\TEMP\crashdata-2192-1221338280_user.dmp -cf
C:\WINDOWS\TEMP\crashdata-2192-1221338280.starter | grep32 -d10000 -i "ChildEBP
RetAddr"
ChildEBP RetAddr
014ae2f0 5eed1e51 sotmi!SotObject::~SotObject+0xc
[o:\ooo300\src.m5\sot\source\base\object.cxx @ 110]
014ae2fc 5ef67923 sfxmi!SfxObjectShell::`vbase destructor'+0x1b
014ae308 5c75f9d5 sfxmi!SfxObjectShell::`vector deleting destructor'+0x36
014ae310 5eed9713 tlmi!SvRefBase::QueryDelete+0xd
[o:\ooo300\src.m5\tools\source\ref\ref.cxx @ 53]
014ae31c 5ef66452 sfxmi!SfxObjectShellRef::~SfxObjectShellRef+0x29
[o:\ooo300\src.m5\sfx2\inc\sfx2\objsh.hxx @ 829]
014ae354 5ef66f9a sfxmi!SfxObjectShell::Close+0x50
[o:\ooo300\src.m5\sfx2\source\doc\objxtor.cxx @ 482]
014ae384 6d49dc57 sfxmi!SfxObjectShell::~SfxObjectShell+0x77
[o:\ooo300\src.m5\sfx2\source\doc\objxtor.cxx @ 390]
Unable to load image
C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91\msvcr90.dll
*** WARNING: Unable to verify timestamp for msvcr90.dll
*** ERROR: Module load completed but symbols could not be loaded for msvcr90.dll
WARNING: Stack unwind information not available. Following frames may be wrong.
014af17c 5f9d6454 msvcr90+0x5dc57
014af1bc 5efb28ac scmi!ScDocument_createInstance+0x70
[o:\ooo300\src.m5\sc\source\ui\unoobj\unodoc.cxx @ 68]
014af1f4 5efb2f85 sfxmi!sfx2::SfxModelFactory::impl_createInstance+0x21
[o:\ooo300\src.m5\sfx2\source\doc\sfxmodelfactory.cxx @ 138]
014af234 5efb2c6b sfxmi!sfx2::SfxModelFactory::createInstanceWithArguments+0x80
[o:\ooo300\src.m5\sfx2\source\doc\sfxmodelfactory.cxx @ 204]
014af26c 656e0ab2 sfxmi!sfx2::SfxModelFactory::createInstance+0x2b
[o:\ooo300\src.m5\sfx2\source\doc\sfxmodelfactory.cxx @ 144]
014af2a4 656ddab4
cppuhelper3MSC!cppu::ORegistryFactoryHelper::createInstanceEveryTime+0xc0
[o:\ooo300\src.m5\cppuhelper\source\factory.cxx @ 762]
014af2d4 656de381
cppuhelper3MSC!cppu::OSingleFactoryHelper::createInstanceWithContext+0x21
[o:\ooo300\src.m5\cppuhelper\source\factory.cxx @ 218]
014af30c 663a3126
cppuhelper3MSC!cppu::OFactoryComponentHelper::createInstanceWithContext+0x91
[o:\ooo300\src.m5\cppuhelper\source\factory.cxx @ 494]
014af358 6639fefe
bootstrap_uno!stoc_smgr::OServiceManager::createInstanceWithContext+0x81
[o:\ooo300\src.m5\stoc\source\servicemanager\servicemanager.cxx @ 1276]
014af390 5ef671b9 bootstrap_uno!stoc_smgr::OServiceManager::createInstance+0x26
[o:\ooo300\src.m5\stoc\source\servicemanager\servicemanager.cxx @ 1386]
014af3d4 5ef6769a sfxmi!SfxObjectShell::CreateObject+0x4d
[o:\ooo300\src.m5\sfx2\source\doc\objxtor.cxx @ 1174]
014af40c 5eee6e8b sfxmi!SfxObjectShell::CreateObjectByFactoryName+0x25
[o:\ooo300\src.m5\sfx2\source\doc\objxtor.cxx @ 1165]
014af560 5eee7a08 sfxmi!SfxApplication::NewDoc_Impl+0x144
[o:\ooo300\src.m5\sfx2\source\appl\appopen.cxx @ 525]
014af738 5efbbb4c sfxmi!SfxApplication::NewDocDirectExec_ImplOld+0x38c
[o:\ooo300\src.m5\sfx2\source\appl\appopen.cxx @ 625]
014af8b0 63ac6515 sfxmi!SfxFrameLoader_Impl::load+0x1253
[o:\ooo300\src.m5\sfx2\source\view\frmload.cxx @ 442]
014af934 63ac664c fwkmi!framework::LoadEnv::impl_loadContent+0x563
[o:\ooo300\src.m5\framework\source\loadenv\loadenv.cxx @ 1195]
014af978 63ac0365 fwkmi!framework::LoadEnv::startLoading+0x87
[o:\ooo300\src.m5\framework\source\loadenv\loadenv.cxx @ 420]
014af9dc 63ac055a fwkmi!framework::LoadDispatcher::impl_dispatch+0x16d
[o:\ooo300\src.m5\framework\source\dispatch\loaddispatcher.cxx @ 173]
014afa20 63a6a1e5 fwkmi!framework::LoadDispatcher::dispatch+0x2d
[o:\ooo300\src.m5\framework\source\dispatch\loaddispatcher.cxx @ 99]
014afa54 5c7310af fwkmi!implDispatchDelayed+0x23
[o:\ooo300\src.m5\framework\source\services\backingwindow.cxx @ 843]
014afa64 5bd79ab9 tlmi!Link::Call+0x11
[o:\ooo300\src.m5\tools\inc\tools\link.hxx @ 142]
014afa6c 5bd7abb2 vclmi!ImplHandleUserEvent+0x46
[o:\ooo300\src.m5\vcl\source\window\winproc.cxx @ 1999]
014afac8 5bc5aed1 vclmi!ImplWindowFrameProc+0x2cc
[o:\ooo300\src.m5\vcl\source\window\winproc.cxx @ 2499]
014afae0 5bdbe195 vclmi!SalFrame::CallCallback+0x16
[o:\ooo300\src.m5\vcl\inc\vcl\salframe.hxx @ 286]
014afaf0 5bdc3e76 vclmi!ImplHandleUserEvent+0x24
[o:\ooo300\src.m5\vcl\win\source\window\salframe.cxx @ 4503]
014afb30 5bdc4088 vclmi!SalFrameWndProc+0x714
[o:\ooo300\src.m5\vcl\win\source\window\salframe.cxx @ 6047]
014afb7c 77141a10 vclmi!SalFrameWndProcW+0x30
[o:\ooo300\src.m5\vcl\win\source\window\salframe.cxx @ 6204]
Unable to load image C:\Windows\System32\user32.dll
*** WARNING: Unable to verify timestamp for user32.dll
*** ERROR: Module load completed but symbols could not be loaded for user32.dll
014afba8 77141ae8 user32+0x21a10
014afc20 77142a47 user32+0x21ae8
014afc84 77142a98 user32+0x22a47
014afc94 5bdd8f15 user32+0x22a98
014afca0 5bdd9483 vclmi!ImplDispatchMessage+0x15
[o:\ooo300\src.m5\vcl\win\source\app\saldata.cxx @ 192]
014afcb0 5bdd94df vclmi!ImplSalDispatchMessage+0x26
[o:\ooo300\src.m5\vcl\win\source\app\salinst.cxx @ 676]
014afce8 5bdd95c2 vclmi!ImplSalYield+0x47
[o:\ooo300\src.m5\vcl\win\source\app\salinst.cxx @ 693]
014afd10 5bc5d2cf vclmi!WinSalInstance::Yield+0x9f
[o:\ooo300\src.m5\vcl\win\source\app\salinst.cxx @ 750]
014afd24 5bc5e795 vclmi!Application::Yield+0x3d
[o:\ooo300\src.m5\vcl\source\app\svapp.cxx @ 503]
014afd34 5e6ebe12 vclmi!Application::Execute+0x1e
[o:\ooo300\src.m5\vcl\source\app\svapp.cxx @ 461]
014afe58 5bc63dc1 sofficeapp!desktop::Desktop::Main+0xfd9
[o:\ooo300\src.m5\desktop\source\app\app.cxx @ 1551]
014afe8c 5bc63e6c vclmi!ImplSVMain+0x3c
[o:\ooo300\src.m5\vcl\source\app\svmain.cxx @ 196]
014afe98 5e701f2e vclmi!SVMain+0x1c [o:\ooo300\src.m5\vcl\source\app\svmain.cxx
@ 237]
014afef8 0040101b sofficeapp!soffice_main+0x81
[o:\ooo300\src.m5\desktop\source\app\sofficemain.cxx @ 54]
014aff04 0040103c soffice!main+0x16 [o:\ooo300\src.m5\desktop\source\app\main.c
@ 37]
014aff10 004011e6 soffice!WinMain+0x15
[o:\ooo300\src.m5\desktop\source\app\main.c @ 37]
014affa0 77083833 soffice!__tmainCRTStartup+0x140
[f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c @ 574]
014affac 7759a9bd kernel32+0x43833
014affec 00000000 ntdll+0x3a9bd
0:000> q
quit:
Comment 1 Mathias_Bauer 2008-09-23 13:24:10 UTC
I remember another crash that happened when the TemplateDialog was opened after
starting OOo. It resulted from an uncaught RuntimeException that was caused by
the inability to instantiate the css.xml.dom.DocumentBuilder service or the
failure to create a new document with it.

If I force the code to throw this exception always, I get exactly the stack
shown here. So this might be the same problem here.

Unfortunately we couldn't find the root cause for the problem in the DOM code.
At least we now have something to investigate.
Comment 2 Stephan Bergmann 2008-09-23 16:13:23 UTC
Problem appears to be that at least for wntmsci12.pro, from external modules
like libxml2, DLLs are delivered that do not include (via mt.exe) their
corresponding .dll.manifest files.
Comment 3 Stephan Bergmann 2008-09-23 16:39:48 UTC
.
Comment 4 Stephan Bergmann 2008-09-24 08:46:15 UTC
Fixed as solenv/inc/tg_ext.mk:1.90.18.1.22.1 on
<http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=OOO300%2Fsb97>.

At least for the Sun Hamburg wntmsci12.pro OOO300m7 build, executing the
following in the solver bin directory under 4NT

for /r %i in (*.bin *.com *.exe) do (mt -nologo -validate_manifest
-inputresource:%i%;1 || echo XXX %i) | grep XXX
for /r %i in (*.dll) do (mt -nologo -validate_manifest -inputresource:%i%;2 ||
echo XXX %i) | grep XXX

shows a number of files that do not contain a manifest; inspecting each one with
depends shows that ten of the files do not find MSCVR90.DLL due to the missing
manifest:

libcurl.dll
libexslt.dll
libxml2.dll
libxmlsec-mscrypto.dll
libxmlsec.dll
libxslt.dll
lpsolve55.dll
stlport_vc7145.dll
stlport_vc71_stldebug45.dll
xmllint.exe

Repeating this with the tg_ext.mk fix applied, all of the ten files above are
fine now (include a manifest and, per depends, find MSVCR90.DLL as installed in
the system), except for xmllint.exe (the tg_ext.mk fix only handles DLLs) which
is not used, anyway.

However, that stlport_vc7145.dll (against which virtually all DLLs and
executables are linked) is also in the above list makes me wonder whether our
assumption is correct that the cause for the RuntimeException is that
libxml2.dll does not find MSVCR90.DLL due to a missing manifest.
Comment 5 Mathias_Bauer 2008-09-24 20:34:30 UTC
It seems that the reason for the crash is that instead of the libxml2.dll in the
OOo folders a newer version in a Windows system directory is used.

I could reproduce the crash that way and in case of one of the submitters of a
crash report removing a libxml2.dll from c:\windows solved the problem.

So now we must find a way to prevent Windows from loading the "wrong" dll.
Comment 6 Stephan Bergmann 2008-09-25 13:05:41 UTC
Indeed, a libxml2.dll from a Windows system directory will take precedence over
the URE layer libxml2.dll (which the soffice.exe wrapper puts into the PATH of
soffice.bin), see <http://msdn.microsoft.com/en-us/library/ms682586.aspx>.  As a
quick hack, for now place an additional copy of the URE layer libxml2.dll into
the brand layer program directory (where in turn it will take precedence over a
libxml2.dll from a Windows system directory).

The modifications already done on CWS sb97 (see above) appear to not be that
urgently necessary after all, so we should not include that CWS in OOo 3.0.0,
but rather in OOo 3.1.0.

A proper fix for this issue would involve a manifest file for our URE layer
libxml2.dll (and other external libraries bundled with OOo), so that OOo
executables would no longer "by accident" pick a libxml2.dll from a Windows
system directory.  This will be done later, in a separate issue.
Comment 7 Stephan Bergmann 2008-09-25 14:30:43 UTC
fixed as scp2/source/ooo/common_brand.scp:1.16.36.8.2.1 on
<http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=OOO300%2Fsb98>
Comment 8 Stephan Bergmann 2008-09-25 14:32:55 UTC
To verify, copy iconv.dll and libxml2.dll from Sun-internal
/share/staroffice/tausch/mba to C:\WINDOWS and in soffice do "File - Templates -
Organize..." (which lead to the crash).
Comment 9 thorsten.martens 2008-09-26 07:28:24 UTC
Checked and verified in cws sba98 -> OK !
Comment 10 Regina Henschel 2008-09-28 13:52:13 UTC
*** Issue 93696 has been marked as a duplicate of this issue. ***
Comment 11 thorsten.martens 2009-03-25 14:51:30 UTC
closed
Comment 12 Martin Hollmichel 2010-03-05 14:31:06 UTC
*** Issue 91661 has been marked as a duplicate of this issue. ***
Comment 13 arkytrails 2010-03-28 21:11:52 UTC
I downloaded the recommended upgrade.  After I received ok that the program was 
in stalled, I clicked on the icon put on my desktop and all it will do is 
install the program over again, neither icon will open the program.
          Help
              Howard
Comment 14 Jim Turner 2013-01-07 15:27:12 UTC
have been running 3.4.0 for a very long while on my iMac OS.X Lion.   I installed Mountain Lion a few days ago and downloaded 3.4.1.  Now it keeps giving me a “OpenOffice.org” is damaged and can’t be opened. You should move it to the Trash.
message every time I go to launch the framework.  Any ideas
Comment 15 Jim Turner 2013-01-07 15:27:28 UTC
have been running 3.4.0 for a very long while on my iMac OS.X Lion.   I installed Mountain Lion a few days ago and downloaded 3.4.1.  Now it keeps giving me a “OpenOffice.org” is damaged and can’t be opened. You should move it to the Trash.
message every time I go to launch the framework.  Any ideas