• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MS Office 2007

hazeman

Member
I recently built a new computer, slapped on XPSP3 and ran some updates.

I wanted to do some benchmarking of the new build and located a copy of SysMark. When I was all done with it, the uninstaller hung on a few of the apps. Some of which were from the Office Suite it came with.

This is the only thing I can think of that may be related to the problems I'm having now. The Office 2007 installation goes without warning or concern. Reboot. Try opening Word and NOTHING! Went on to Excel, nothing. Same with all the apps, none of them will load.

I've ran registry scans, etc... I need some help. I'd rather not format the drive and start over again. 🙁
 
Errors:

Faulting application osa.exe, version 12.0.4518.1014, faulting module mso.dll, version 12.0.4518.1014, fault address 0x00007241.

Faulting application setlang.exe, version 12.0.4518.1014, faulting module mso.dll, version 12.0.4518.1014, fault address 0x00007241.

The description for Event ID ( 5000 ) in Source ( Microsoft Office 12 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: offdiag12, ab35515f-8d10-4406-955b-3ddb559624a72c05a06a-4d2d-4e41-9a6b-79ca6ca436fe, NIL, NIL, NIL, NIL, NIL, NIL, NIL, NIL, NIL.


Warnings:

A provider, OffProv12, has been registered in the WMI namespace, Root\MSAPPS12, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

TraceLevel and TraceFileName (countless entries, several per day)
 
I know you're not insulting me with that reply... but yes. I uninstalled Office 2k7, ran a registry scan to delete any keys left behind, ran the Office 2k7 setup again and still have the same result.

I'm unhappy with the installation of XP atm anyways. I didn't use the nLite copy I had used prior. I'm seriously considering dumping XP and moving to Vista now that SP2 has been released.
 
Really? Is this documented anywhere? I even went to micrshaft's website after I ran the MSO installation verification app... came up with nothing.

I'll keep it in mind if I don't switch over. Luckily I still have my old rig running with Office on it-- for now.

Thanks for the reply Vinyl.
 
It's just an idea. I believe there are some issues with 4GBs of ram in 32 bit Windows. This could possible be one of them? I remember reading about tests where games would crash because of it.
 
Well, I decided to stop fuggin around and wiped the slate clean. I got me a copy of Vista x64 SP2 and so far I'm very pleased. Just about everything has been given an immediate boost. There are some minor problems, but nothing at all that's permanent. (most of which are driver related)

Thanks again.
 
Back
Top