T
Tribble
Looking for any insight into this issue - note that the Office 2007
Compatibility pack IS installed.
I support a user environment with about 200 users on Office 2003. In
recent weeks, I have had several tickets opened by users who are
receiving .ppt files received in email (Exchange 2003) and get this
error:
PowerPoint can't read the outline from <file path\filename.ppt>. No
text converter is installed for this file type.
This message is one of the potential messages a user will receive if
they try to open an Office 2007 file without having the Office 2007
Compatibility Pack installed - but all the computers at this company
have the pack installed.
One thing I find very interesting is that the extension is .ppt, and I
would have thought it might be .pptx (changing it manually to .pptx
does nothing, nor does installing PowerPoint Viewer 2007).
Another thing - in one case we sent the file back to the originating
user and they could not open it either. It appears to be truly
corrupted by the time it gets to the Office 2003 user.
Has anybody seen this happening anywhere else, or have any ideas of
things I can try?
Compatibility pack IS installed.
I support a user environment with about 200 users on Office 2003. In
recent weeks, I have had several tickets opened by users who are
receiving .ppt files received in email (Exchange 2003) and get this
error:
PowerPoint can't read the outline from <file path\filename.ppt>. No
text converter is installed for this file type.
This message is one of the potential messages a user will receive if
they try to open an Office 2007 file without having the Office 2007
Compatibility Pack installed - but all the computers at this company
have the pack installed.
One thing I find very interesting is that the extension is .ppt, and I
would have thought it might be .pptx (changing it manually to .pptx
does nothing, nor does installing PowerPoint Viewer 2007).
Another thing - in one case we sent the file back to the originating
user and they could not open it either. It appears to be truly
corrupted by the time it gets to the Office 2003 user.
Has anybody seen this happening anywhere else, or have any ideas of
things I can try?