IT Process Automation

  • 1.  bad handle to generic_activity_log

    Posted Jan 09, 2018 04:39 PM

    Using CA Pam to add a comment to a Request I'm getting the following error. I've been working with CA SDM / PAM for about 2 years and this one is new to me. 

     

    Any help appreciated. 

     

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <soapenv:Fault>
    <faultcode>soapenv:Client</faultcode>
    <faultstring>bad handle to generic_activity_log</faultstring>
    <faultactor/>
    <detail>
    <ErrorMessage>bad handle to generic_activity_log</ErrorMessage>
    <ErrorCode>1000</ErrorCode>
    </detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>



  • 2.  Re: bad handle to generic_activity_log

    Posted Jan 09, 2018 06:51 PM

    Hi,

     

    Are you using the CA provided Log Request Comment operator or Invoke SOAP Method?  The CA Log Request Comment Operator needs the request number as it's input while using Invoke SOAP Method needs the persistent_id of the request.

     

    If you're using the Invoke SOAP Method operator can you share the dynamic parameters that you're passing?



  • 3.  Re: bad handle to generic_activity_log

    Broadcom Employee
    Posted Jan 16, 2018 09:01 AM

    Any Luck on this Joel?   It looks like you are getting an error back from Service Desk about the activity log, but after a bit of searching internally I am not seeing anything quick I can provide about why this is occurring.   If this is ongoing I would suggest a support ticket so we can investigate this in more depth.



  • 4.  Re: bad handle to generic_activity_log

    Posted Mar 02, 2018 10:09 AM

    You're going to laugh but i sorted this out a few weeks ago... For the life of me I can't remember what I was doing wrong. All I can remember is that i did something dumb, corrected it and it's behaving itself.