Error opening embedded TIF files

HCL Domino Domino Forum
1

Some users are embedding TIF files into documents. We’re on Domino 6.0.2CF1 and Client 6.0.3.

It appears whenever any Windows XP client tries to right click on the embedded TIF files, and click Open, they get:

The object’s application or class is not available.

How do I fix this? I can go to my file system on any of these WinXP machines, double click on a TIF file and it opens the Windows Picture and Fax Viewer just fine. This error does NOT occur on Windows 98 and Windows 2000 computers. What else can I check?

Thanks!

Michael

2

Subject: Error opening embedded TIF files

Michael,

I guess you are not having any tif viewer in registry settings (launch association) or you simply didn’t install Imaging for Windows?

Hope it helps.

Regards,

Bine.Zerko@imis.si

http://www.imaging4notes.com

3

Subject: RE: Error opening embedded TIF files

I already checked to verify the TIF viewer was set correctly and you can’t install Imaging for Windows in Windows XP, I verified this directly with Microsoft.

Any other ideas?

Thank you.

Michael

4

Subject: RE: Error opening embedded TIF files

Michael,

the problem is, that this image has been created by Imaging for Windows (ie Wang’s imaging) while the newest “Microsoft Office Imaging” is not able to recognize that OLE object.

My suggestion: check the same sample on a W98 machine, with Imaging for Windows…

We can enhance our IMiS/Migrator in a way to convert such embedded objects into standard TIFF attachments. Let me know if you are interested in.

Hope it helps.

Regards,

Bine.Zerko@imis.si

http://www.imaging4notes.com

5

Subject: RE: Error opening embedded TIF files

Hello,

We have same problem on a Notes application with embedded TIF. I try to install some several free application and same problem !

It’s a real great problem with older document !!!

I hope Lotus found solution !

6

Subject: RE: Error opening embedded TIF files

I too had this problem and did find a (rather complex!) solution too it. You can actually install the pre XP kodak imaging software on your PC, as detailed here: http://techrepublic.com.com/5100-6270-5034679.html.

I then also had to add these registry entries:

(You can paste this into a .reg file and double click to merge)

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}]

@=“Image Document”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\AuxUserType]

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\AuxUserType\2]

@=" "

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\AuxUserType\3]

@=“Imaging”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\DefaultExtension]

@=“.tif, Image Document (*.tif)”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\DefaultIcon]

@=“C:\PROGRA~1\WINDOW~1\ACCESS~1\ImageVue\kodakimg.exe,1”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\DocObject]

@=“0”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\InprocHandler32]

@=“ole32.dll”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\Insertable]

@=“”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\LocalServer32]

@=“C:\PROGRA~1\WINDOW~1\ACCESS~1\ImageVue\kodakimg.exe”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\MiscStatus]

@=“32”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\Printable]

@=“”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\ProgID]

@=“Imaging.Document”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\Verb]

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\Verb\0]

@=“&Edit,0,2”

[HKEY_CLASSES_ROOT\CLSID{02B01C80-E03D-101A-B294-00DD010F2BF9}\Verb\1]

@=“&Open,0,2”

hope this helps.

-ross

7

Subject: RE: Error opening embedded TIF files

We too had the same issue. I traced it to the fact that Windows XP SP2 changes the program Packager.exe, which is the Windows Object Packager program. We haven’t gotten as far as what the problem is with the new program but if you replace this program with one from XP SP1 or Windows 2000 professional and place it in the SYSTEM32 directory under Windows, it will fix the issue. You should also copy it so ServicePackFiles\i386 in the windows directory.