Our backflush task all of a sudden started to have issues. IT seems to get stuck on a few jobs. Just by opening them in Job Closing resolves each job. (which also bewilders us). Looking at the exception that is being generated we see this inner exception:
The partner transaction manager has disabled its support for remote/network transactions.
Does anyone have any insights as to what this might be or mean?
At the time we see this error each time on the app server event viewer.
Query failed to run
The underlying provider failed on EnlistTransaction.
(ctx, company_ex, personID_ex) => ctx.Person.Where(row => ((row.Company == company_ex) AndAlso (row.PersonID == personID_ex))).FirstOrDefault()
Joe,
I noticed this error which is similar to one we are getting when we attempt to email A/P remittances. We submit the job and it fails.
Did you ever find a solution to this? My guess is maybe some type of DB data corruption.
And I’m wondering if the error message has any real meaning and that the error is still hidden.
Thanks!
Rob
We found the cause, not necessarily a solution. It turned out one of our users created a global alert and just having that global alert caused seemingly random jobs to get stuck when running backflush.
We worked with Epicor to figure it out but never came to a solution. We send our entire DB to them a few times but they said they could not get the issue to occur. That is as far as they would assist us.
Eventually, it was determined that the global alert was no longer needed. It was removed and everything went back to normal.
Sorry but still no clear answer.