Yup, just gave it a shot. I have turned off tracing, I have gotten rid of bpms. This is really annoying.
You checked the sequential thing above?
Yes sir. Checked that. It looks the same as any other part rev. I am dumbfounded on why this part is different than the rest
From what I am reading it sounds like it is an SQL server issue. I suppose the transaction is considered a “doomed transaction”. Does not sound too promising =/
Well everyone… 6 hours later, I figured out what the issue was. Pretty frustrated at how stupid it was. One of the operation comments had #'s in it. Apparently Epicor does NOT like #'s in comments. So Stinking stupid. Anyways, thank you all for your help, hope this helps someone down the road if they get the same error!
1 Like