[Bug 21673] Office 2007 Enterprise installation fails

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=21673





--- Comment #19 from Nikolay Sivov <bunglehead at gmail.com>  2010-02-18 14:04:47 ---
>
> No those errors are fixed now. What I meant was that the winecfg output is
> fixed now (no more errors)

Good.

>  but Office still doesn't install and thus the log at
> http://bugs2.winehq.org/attachment.cgi?id=26284 which I posted before is still
> valid (installing msxml lib32 didn't change the output).

Not good, I don't see actually how could this happen in the same time.

> So what I'm thinking is that we need to find the bug that's causing Office
> setup to crash. Looking at the log (I an not experienced in Wine at all) I see
> an "err:ole:CoGetClassObject no class object
> {f5078f32-c551-11d3-89b9-0000f81fe221} could be created for context 0x1" line,
> and something tells me that err's are more critical than fixme's. Could the ole
> err be the culprit?

Yes this indicates problem indeed, but it's nothing to do with ole itself. It's
an output of CoGetClassObject that looks at registry class data, picks up
corresponding dll (msxml3 in this case) and calls its DllGetClassObject
function to get class factory pointer.

Attach +relay,+tid,+msxml log that ends with this 'err:ole:CoGetClassObject...'
please (no need for lines after that). To activate debug output use
'WINEDEBUG=+relay,+tid,+msxml wine <yourapp.exe>', cd'ing to app dir before
that.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.