Error opening .jpg files in a TS outllok session

  • Thread starter Thread starter Brad Pears
  • Start date Start date
B

Brad Pears

We have Office 2000 installed on our Windows 2000 Terminal Server. Anytime a
user attempts to open a .jpg file attachment from their Outlook client by
double-clicking it, they get a "The system cannot find the path specified"
error.

However, if they save the attachment to their Terminal Server session
desktop (or any other location), they can then double click the file and
voila, up it comes.

Does anybody have any ideas as to why one cannot launch the attachment from
within the Outlook client?

The TS users do not have access to the iexplore.exe file so instead I set up
a file association so that Kodak "Imaging For Windows" application is
launched to display .jpg files.

Could there be a problem with the Outlook app finding the required
application to launch the jpg file?

Any help would be most appreciated!

Thanks,

Brad
 
Thanks for that info.

Unfortunately, I am logged in as the administrator on a TS session and
still getting the exact same message when I try to double click a .jpg
attachment.

Our Office software is installed on the D: drive as opposed to the C drive
due to space constraints at the time. Might this have something to do with
it? Maybe there is a hardcoded "c:\program files" somewhere in on eof the
registry keys??

Anything else to try?

Thanks,

Brad

Patrick Rouse said:
The problem is due to insufficient registry permissions on Microsoft Photo
Editor that installs with Microsoft Office.
 
Mathew... Thanks so much for that!!!

It nailed down what the system is looking for exactly to generate the "path
not found" error.

However, here is my next question...

The error is being generated on the following line (copied out of filemon)
----------------------------------------------------
11:56:29 AM OUTLOOK.EXE:5440 OPEN
C:\progra~1\window~1\access~1\imagev~1\kodakimg.exe PATH NOT FOUND Options:
Open Access: All

----------------------------------------------------

As you can see, in the path, the directory "ImageVue" has been changed to
"imagev~1". Because the directory ImageVue is only 8 chars to begin with, it
cannot find the 'Imagv~1" directory. Why would it be converting an 8 char
directory name to the "~1" name? If I can resolve this issue, I think we'll
be good.

Thanks,

Brad
 
Back
Top