Asset Suite / PassPortGeek

Use SQL to find the TIDOBLOK entry.

TIDTPCOL.OWNER_CODE_50 is the X293 Owner Key.

select * from passport.tidtpcol
where owner_code_50 = '0000078446000';

More than 1 row might be returned. Use the one with the matching X293 Notes value.

select * from passport.tidoblok
where ole_object_id = tidtpcol.ole_object_id;

TIDOBLOK.OLE_OBJECT_CLASS is what Portal/J cannot find a Windows registered application for. OLE_OBJECT_CLASS might be the actual Windows Registry Class entry or it might be matched with a P/J Global Definition to find the Windows Registry Class.

When the user receives "Can not determine Class ID for RICHTEXT", what's happening is that there is no Application Name in the Portal/J Administration, Global Definitions, Define Param, where Application Name = RICHTEXT (or whatever Class ID is in the message). Most Portal/J's will have an entry of Application Name = "RichText", Parameter Value = "Word.Document.8". Use Windows regedit, then Edit, Find on word.document to see what Word applications are registered.

For example the following will result in the user receiving the error message.

P/J Application Name = RichText and Parameter Value = Word.Document.8

TIDOBLOK for the embedded document has OLE_OBJECT_CLASS = RICHTEXT

For the example, the least risky fix is to change all TIDOBLOK.OLE_OBJECT_CLASS to "RichText" where OLE_OBJECT_CLASS = "RICHTEXT". Note that when the user accesses the data on X293 the OLE icon does not display data content, i.e., the OLE icon does not have lines in it. After the embedded document is accessed, changed and saved the OLE icon will display data content.

It might be possible to make a new entry in the P/J Administration for Application Name = RICHTEXT, but this will take some doing.

Another solution that will work with most embedded objects that you think are text, Word, RichText, but not all, is to change OLE_OBJECT_CLASS to "Word.Document.8" and make sure OLE_OBJECT_LEN does not have leading zeros. This solution is not recommended because if the document cannot be opened by the new OLE_OBJECT_CLASS, Portal/J can hang and the embedded object become corrupted.

The problem most likely occurred during an upgrade of Asset Suite/PassPort when a mass data load was done.