Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Can't open docx files in office 2003 with compatibility update...
170 views
Skip to first unread message
Jaime
Mar 20, 2010, 3:28:01 AM3/20/10
to
Any suggestions??
I have reinstalled office, reinstalled the compatibility update, removed
word and then reinstalled it, reinstalled sp3 updates. I'm at a loss...
xlsx file work perfectly fine in excel, problem seems to be with only word
docx files.
need help! thanks.
Jaime
Mar 20, 2010, 3:39:01 AM3/20/10
to
Forgot to mention that I also downloaded the converter program but still
receive the same error.. "there was an error opening this file"
receive the same error.. "there was an error opening this file"
Peter Jamieson
Mar 20, 2010, 3:59:59 AM3/20/10
to
Jaime
Mar 20, 2010, 6:03:02 PM3/20/10
to
This did the trick!!! Thank you!!!
"Peter Jamieson" wrote:
> .
>
chris
Apr 7, 2010, 5:35:02 PM4/7/10
to
this worked great thanks!
buz
Apr 12, 2010, 3:59:01 PM4/12/10
to
Hi, I believe I too have the same issue. All my windows updates are up to
date. I have followed the instructions from the support centre article but
get the following window:
date. I have followed the instructions from the support centre article but
get the following window:
"DllRegisterServer in C:\WINDOWS\system32\ole32.dll failed.
Return code was: 0x80070005"
P.S. sorry to Hijack your thread a little.
Dan
Peter Jamieson
Apr 13, 2010, 2:54:54 AM4/13/10
to
AFAIK that error message+code means that regsrv32 did not have
sufficient permissions to alter the registry or write to the system32
folder, which is precisely what "Run As Admiistrator" is supposed to
give you. So I don't know what's wrong. If I faced this problem I would
probably
a. make sure I had "Run As Administrator" rather than rely on the
assumption that my own account had sufficient privileges to do the job
and/or
b. actually log in as Administrator (if I could) and run regsvr32 from
there
sufficient permissions to alter the registry or write to the system32
folder, which is precisely what "Run As Admiistrator" is supposed to
give you. So I don't know what's wrong. If I faced this problem I would
probably
a. make sure I had "Run As Administrator" rather than rely on the
assumption that my own account had sufficient privileges to do the job
and/or
b. actually log in as Administrator (if I could) and run regsvr32 from
there
I cannot help feeling that not having ole32.dll registered correctly
would likely have a rather big impact on any system but there you go.
Peter Jamieson
0 new messages