QAID # 14248 Published
Question / Problem:
Using the Ascent 7.x Release Script for FileNet Content Manager 4.x, why is a
“Failed to release document”
error occurring on a consistent basis with all Documents?
Answer / Solution:
The Ascent 7.x Release Script for FileNet Content Manager 4.x supports the DIME protocol provided with .NET Framework 1.1. The MTOM protocol provided with .NET Framework 2.0 is not supported.
Verify that the FileNet Content Manager system has been configured to use the DIME-based Web Service instead of the MTOM-based Web Service. Also, verify that the .NET Framework 1.1 and the Web Services Enhancements (WSE) 2.0 SP3 for Microsoft .NET are installed on the machine running the Release Script.
Verify that a document can be inserted into the FileNet Content Manager system through the use of the browser interface using the DIME-based Web Service. If this step fails, it indicates a FileNet communication issue between the machine performing the Release and the FileNet Content Manager system.
Examine the Capture error log (ERR_yymm.TXT) for more details as to the error.
For example, the following error message in the Capture error log points to FileNet making use of an unsupported MTOM- based Web Service:
2010-10-12 16:37:03, 0x00000018, 0, 0x80131500, 0x00000000, 0x00000000, E:\Kofax\CaptureSS\ServLib\Bin, Kofax Capture Release, MVMPDOCSAVIAP01, 8.00.1238, P8REL45_V75:KfxReleaseScript.ReleaseDoc, 0, EXCEPTION DETAILS: Failed to release document. Kofax.P8Rel45_v75.Connector.ReleaseException: Failed to release document. -- -> System.InvalidOperationException: Client found response content type of 'text/plain', but expected 'text/xml'.
This error is also known to occur when the FileNet system is configured to restrict valid content types. If this is the case, the same behavior will be exhibited when attempting to insert a document to the FileNet Content Manager system through the use of a browser interface.