http://bugs.winehq.org/show_bug.cgi?id=21673
--- Comment #17 from Nikolay Sivov bunglehead@gmail.com 2010-02-18 12:34:35 --- (In reply to comment #16)
You were right - lib32-libxml2 is not a dependency on the wine package in AUR so I was missing this. Installed it, though it doesn't seem to alter the situation. The log I gave you (from setup) still looks exactly the same. Nothing in there hinting at why Office setup would crash?
So it still gives you ELFCLASS64 dll load errors and object creation errors later? It probably means that you're still using 64bit modules, maybe libxml2.so symlink points to 64-bit module that's reasonable on 64-bit system. Honestly I don't know how it's managed to have 32/64 bit modules at same time, probably two lib dirs - lib32/lib64. Also I don't know how Wine acts for this case, we obviously can't use 32bit Wine with 64bit external modules for pointer length reason for example.
What I can tell you for sure - msxml3 is linked statically to libxml2, I mean we don't have dlopen() for it, so any libxml2 load failure causes load failure for msxml3, which is a reason for next create object failure. We have to find out what's going wrong with your libs and proceed further to real problem if it's here. Note that distribution bug is possible too. You may want to use wine-users mail list or forum to ask, if nobody helps you here in some reasonable time.