Workflow error gets stopped (temptb error)

(0) Share

Report

Posted on by Community Member

Hi Guys,

I am seeking your valuable suggestions or experiences for the very generic issue that we are facing in our live environment as below.

when we submit any workflow, it gets stopped ,gives tempdb error and it happens for the all workflows submissions .

Below error is in the case of purchase requisition workflow submission whereas in other cases the nature of error is same i.e. tempdb but points different tables.

Stopped (error): session 51 (Sync) INSERT INTO tempdb."DBO".t100010_E2759EE689DC4C7B83621F066B2CBF04 (ACCOUNTINGDATE,SOURCEDOCUMENTLINE,RECVERSION,PARTITION) SELECT T1.ACCOUNTINGDATE,T2.SOURCEDOCUMENTLINE,1,5637144576 FROM tempdb."DBO".t100011_0A120DCEDACB461F99FF22E071430

our work around for this issue:

Done full CIL and AOT sync but however only AOS restart helps us.

we do AOS restart to resolve the issue as it happens in our live environment but it appears again at some time in future.

Appreciate any suggestions or opinions.

Thanks,

Tirupathi Rao

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

André Arnaud de Cal... 303,667 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi Tirupathi,

There might be two logical causes for this issue:

- SQL failover occured. In that case indeed an AOS restart is certainly solving the issue

- The TempDB might have raised an error, e.g due to full disks or limited space.

Please check above assumptions.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Andre for the reply,

I will check the scenarios that you suggested.

Was this reply helpful? Yes No
Dick Wenning 8,705 Moderator on at

Like (1)

Report
Copy link

Link copied!

start with finding the class. can be done with sysDictTable(100011)

small secret about ax (DBO".t100011_0A120DCEDACB461F99FF22E071430)

the red part is the AOT table ID ;-)

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report
Copy link

Link copied!

If possible, take a downtime during non business hours and restart the AX and SQL services.

this will clear the tempDb data. Also make sure that your tempDB file size hasn't gone beyond your max size.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks for your replies.

Hi Dick Wenning,

I can see several error messages (as posted above) in my work flow history

Also similar error messages sometime when end user tries to run reports in production system.

Based on your suggestion, I find out table names based on ID mentioned in error message (secret)

I could find out 4 such tables and believe there could be many more like this.

Now what can I do with these tables? Also I see there are several such tables I feel something wrong with my temp tables definition in AOS and SQL.

I checked temp db file disk size, it’s okay. Enough space and max size unlimited.

I am looking for permanent solution to this issue as it is very annoying when it happens in production and we have to restart AOS during business hours.

Note: I already synchronized DB.

Thanks

Was this reply helpful? Yes No