web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Batch Alert Group ,Error
Microsoft Dynamics AX (Archived)

Batch Alert Group ,Error

(0) ShareShare
ReportReport
Posted on by Community Member

Hi All,

All of sudden when I run Batch Alert Job , unfortunately ending up with an error.

I have debugged the Class "EvenJobCud"  , run() method as soon as the breakpoint hits the below highlighted  code , the following error pops up

I have also written a job for EventCud table and found that there 2260924  exists which all are in "Waiting" state , I doubt that if this could be the problem ?. (I am not sure).

6102.err.JPG

eventJobCud.JPG

Also when I right the table and try to open the Table Browser for EventCud table the AX system is getting freezed for forever.

Please provide suggestion .

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    The error message suggests that it cannot handle the data to be generated for some object, most likely the origin record for the alert message. It can happen if an alert was raised, while the table structure has been modified (i.e. by deleting a field, or removing a data type behind the field).

    The quickest fix is to remove pending alerts from the queue, if you cannot find specifically that which record entry is raising the error. Before doing this you should consult with your business if it has any impact if they do not get specific alert notifications.

    The freezing could be just a performance bottleneck because you are not maintaining index fragmentation and statistics on your AX database within SQL Server. Have a look at the tables' index fragmentation, last updated statistics, and query execution plan (for possible missing covering index) - you may read up about these topics online with a simple search. Alternatively you could just return the records from within SQL directly, which would most likely not "freeze", and see what is going on there.

  • Community Member Profile Picture
    Community Member on at

    Thanks you so much Vilmos. Your suggestion gonna help me a lot.

    Just a query .  Deleting records from EventCud table whose status is "waiting" will impact any other processes in ax ?

    Thanks a lot to you once again.....

  • Verified answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    EventCUD is the unsent alert messages. The only impact it has is that alerts which were supposed to be received will not go out after the event processing batch runs, if you remove entries in there. I would focus on removing the problematic ones only, which you should be able to find with the debugger.

  • Community Member Profile Picture
    Community Member on at

    Thanks  a lot Vilmos I successfully resolved the issue, as I have cleaned up all the pending alerts from the table as you have suggested.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
Ali Zaidi Profile Picture

Ali Zaidi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans