Users Receiving 'Not IStream-Specific Node' Message When Adding IStream Documents To The DM Server

Last updated on OCTOBER 25, 2017

Applies to:

Symptoms

On : 6.3.0 version, IStream Document Manager

When users are attempting to add IStream objects (CMS/CDS/CLG) to the DM Server regardless of which method ( Author/Assembler/Web UI) ,
the following message is reported;


ERROR
-----------------------
versionFile = 'C:\Windows\TEMP\otup770993A9288048A9A7BF78864CA2F7FC0'
versionFile_content_type = 'application/octet-stream'
versionFile_dcsMimeTypeStatus = 'failure'
versionFile_filelength = '1221120'
versionFile_filename = 'G:\testcase\2015_2093447406.CDS'
***Request2: C:\Windows\TEMP\otup770993A9288048A9A7BF78864CA2F7FC0
***Request3: G:\testcase\2015_2093447406.CDS
>>>About to check type<<<
--@@@-- create temp file: \tngtemp\719894B.tmp
2015/12/09 08:13:14 Checktype 0 0 Attempting to check version type
2015/12/09 08:13:14 Checktype 0 0 Fetching Version file
2015/12/09 08:13:14 Checktype 0 0 Version number: 1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ GET TYPE @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
idm63-pdf-helper istmIsPDF begin @19790
idm63-pdf-helper istmIsPDF end @19790
$TNGCheckErrorMsg = Not IStream-specific node


The document is added to the DM Server however the mimetype is 'application/octet-stream'.
The object icon appears to be non-istream
Users can add Doc/PDFs document to the system and it appears correct ( only IStream objects (CMS/CDS/CLG) are affected).



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Confirm that all IStream Services are running.
2. Use one of the following method ( Author/Assembler/Web UI) for adding an IStream objects (CMS/CDS/CLG) to the DM Server.

Cause