It seems that you get exception from client side, then you turn on DFS trace and get a new error from server side.
For the exception from DFS server, it's a 3rd party bug and has been fixed in a HFX. You may contact Tech Support for the HFX if you're using DFS 6.5 SP1 or later versions.
For the exception from DFS client, it seems that there is something wrong with document format setting. Can you attach here your sample code?
- simon
Hi,
Please check the code you have attached. The below two line getting null value.
contentTypeValue);
Hi Bibhu,
The code is not giving null value. These values are getting picked up from a property file.
Code to get values from property file and setting these variables value is there in the main method of client code.
I am setting a_content_type as pdf with every call.
Thanks
since there is a bug when enabling DFS tracing, you can disable tracing. Then run your DFS client again and get the application server log, which may include the underlying exception.