Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
3 replies Latest Post - ‏2013-12-13T04:55:07Z by DR1R_Stuart_Norton
DR1R_Stuart_Norton
DR1R_Stuart_Norton
6 Posts
ACCEPTED ANSWER

Pinned topic DQC: can't retrieve exceptions for descriptors

‏2013-12-10T23:40:58Z |

Hi all,

 

I've got an issue where I run a rule and while I can see the exception descriptor in the DQC, clicking on the exception link produces the following error:

The INVALID_EMAIL exception descriptor was deleted in the console, the project, or both. Refresh the Exception Descriptors pane and then try again.

Any ideas?

 

Cheers,

Stuart.

 

  • RobertDickson
    RobertDickson
    72 Posts
    ACCEPTED ANSWER

    Re: DQC: can't retrieve exceptions for descriptors

    ‏2013-12-11T14:57:33Z  in response to DR1R_Stuart_Norton

    Hi Stuart,

    I've had this when the IP address of the server changes.  Like a Windows-only image on DHCP.

    Regards,

    Robert

    • smithha
      smithha
      162 Posts
      ACCEPTED ANSWER

      Re: DQC: can't retrieve exceptions for descriptors

      ‏2013-12-11T19:26:13Z  in response to RobertDickson

      Hi Stuart,

      If Robert's suggestion does not resolve the issue, you may want to check the DQC log.

      On Windows, it's usually in:  C:\IBM\WebSphere\AppServer\profiles\InfoSphere\dqc_all-server1.log

      Path would be the equivalent for Unix/Linux.

      If that doesn't identify anything obvious in approximate timeframe when you tried to review the Exceptions, you may want to raise as an issue with technical support.

      Harald

    • DR1R_Stuart_Norton
      DR1R_Stuart_Norton
      6 Posts
      ACCEPTED ANSWER

      Re: DQC: can't retrieve exceptions for descriptors

      ‏2013-12-13T04:55:07Z  in response to RobertDickson

      Hi Robert,

       

      Thanks for the quick response.

      That was the problem: it was a VM that was having some issues keeping its networking straight. All fixed now.

       

      Cheers,

      Stuart.