Clarity Service Management

Expand all | Collapse all

Error: Unknown method:'CMassUpdate::Free_uncheck', when opcode: ' mass_update' passed to CMassUpdate

  • 1.  Error: Unknown method:'CMassUpdate::Free_uncheck', when opcode: ' mass_update' passed to CMassUpdate

    Posted 02-13-2019 05:19 AM

    Hello Everyone,

     

    CA SDM 17.0 hosted on Linux environment. We have seen the below error recently in the stdlog files:

     

     kt_daemon           21101 ERROR        MassUpdate.c           491 Unknown method:'CMassUpdate::Free_uncheck', when opcode: ' mass_update' passed to CMassUpdate

     

    Prior to this error, we do not see any message related to the kt_daemon. Was wondering what kt_daemon is doing massupdate? Can someone please elaborate what this daemon is trying to do, why it failed and if it has any negative effect?

     

    Thanks,



  • 2.  Re: Error: Unknown method:'CMassUpdate::Free_uncheck', when opcode: ' mass_update' passed to CMassUpdate

    Posted 02-18-2019 03:40 AM

    Any update on this error?



  • 3.  Re: Error: Unknown method:'CMassUpdate::Free_uncheck', when opcode: ' mass_update' passed to CMassUpdate

    Posted 02-18-2019 05:37 AM

    Hi Subbarao,

     

    Are you trying to extract KT document and use the export to excel functionality? What is the patch level that you are running on your environment?



  • 4.  Re: Error: Unknown method:'CMassUpdate::Free_uncheck', when opcode: ' mass_update' passed to CMassUpdate

    Posted 02-19-2019 02:54 AM

    Hi Maheshwar,

     

    No we are not doing any extract using export functionality to excel. we are having v17.0 with few test fixes.

     

    we would like to know what the error is and is it having any negative impact on KT document or it can be ignored?



  • 5.  Re: Error: Unknown method:'CMassUpdate::Free_uncheck', when opcode: ' mass_update' passed to CMassUpdate

    Posted 02-19-2019 04:45 AM

    Thanks for your update Subbarao,

     

    I have noted this behavior on another case and this what they have identified the reason to be .

     

    Due to using pdm_load to import knowledge documents and other data, some attachments had become orphaned and were causing errors when referenced.

     

    I am not sure if this is in your case but just wanted to validate if you have such scenario in your environment?