Skip to Content
0
Former Member
Feb 06, 2012 at 07:28 PM

DI API error "Could not commit transaction: Error -1 detected during trans"

178 Views

I have a large collection of journal vouchers that I post in three different SAP companies. Each journal voucher contains between 2 and 5 entries. Once all calculation is done I go to commit all three transactions (it's required to be done this way). One of the DBs almost always fails when I try to do this during business hours (when users are logged in), the other two never create problems and I never have a problem if I do it in the middle of the night when only other DI API and DI Server applications are running. The error that I get is: "Could not commit transaction: Error -1 detected during transaction". The journal voucher that fails contains one entry with 1500+ lines it it (it's required to be done this way). Is there some way that I can prioritize my application above the users so that i can get this to work without forcing user out?

We are using SAP Business One 8.82, but this problem has existed since we were on 2007A.

we are using MSSQL 2005