Deadlock - Could Not Commit Transaction

Hi Experts,
While posting Journal Entries through B1if, we encountered an 'Deadlock Error' 'error, unable to commit the transaction. Although the process is executed through Queue, we faced the same multiple times. Solutions are highly appreciated.

HI,
While ur inserting through DI API.try to lock the table and insert.
ROM A WITH(NOLOCK)
regards,
Prasad

Similar Messages

Could not commit transaction

Hi,
I am creating an approval procedure for SO, checking balance, due inovices and payment terms. The approval should not be trigger when the SO is cash basic. The payment term cash basic has code -1. This is my query. I got the error Could not commit transaction.
What is wrong?
SELECT CASE WHEN T0.Balance+$[$29.0.NUMBER] > T0.CreditLine AND
$[ORDR.GroupNum] <> (-1 ))
OR
(SELECT COUNT(*) FROM [dbo].[OINV] T1 WHERE T1.DocDueDate<GetDate() AND T1.DocStatus='O' AND T1.CardCode = $[ORDR.CardCode]) > 0
AND
$[ORDR.GroupNum] <> (-1 )
THEN 'TRUE'
ELSE 'FALSE' END
FROM [dbo].[OCRD] T0
WHERE T0.CardCode = $[ORDR.CardCode]
Tks
Adriana

Hi Adriana,
By analyzing your logic, I simplified it. Please try this query:
SELECT Distinct 'TRUE' From dbo.OCRD T0, dbo.OINV T1
WHERE (T0.CardCode = $[$4.0.0]) AND ($[ORDR.GroupNum] !=N'-1') AND
((T1.DocDueDate<GetDate() AND T1.DocStatus='O' AND T1.CardCode = $[$4.0.0])
OR (T0.CreditLine - T0.Balance < $[$29.0.NUMBER]))
Thanks,
Gordon

Web Services,Delivery Document Adding Error Could not commit Transaction

Dear All,
I am working with SAP Business One Web Services, While adding Delivery Document it's giving error "Could not commit transaction" Please Give your Suggestion It's urget.
Thanks,
Madhu
9701155577

Hi,
Do you mean there is no journal entry created orthat the link is missing?
If this really is a delivery for stock/inventory items there should be a journal entry, else it sounds like an error in SAP.
Are there still changes in the stored procedure? Also have a look at the TansactionNotice. It is possible the roll back does not work correctly.
Again sounds like an error.
Doe sit happen all the time?
Only for certain items?
Are the stored procedures now clean?
What Version are you using?
Kind Regards,
Friederike

Error 'Could not commit transaction'

Dear Expert,
I am facing error ' Could not commit transaction' while entering Good Receipt PO . All GL account mapped.

Hi,
Please check for the Approval procedures and see if the user for which
you are getting error is defined the originator for the affected
documents.
You can check this by going through all the Approval template for that
particular document.
Then check the Terms tab of that template and if in Launch Approval
Procedure "When the following applies" is ticked then check the "Ratio"
column and "Value" column and make sure that some value is given there.
There should not be any undefined type.
If there is any Template which has undefined type selected then please
logged in as the Authoriser or Approver of that template and modify
that term.
Check all the approval template and go through the term tab and see the
value defined there.
Hope this will help.
Regards,
Gagan Thareja
SAP Business One Forums Team

Could not commit transaction Error 1 Detected During Transaction G/L Account

hi experts
when i was adding Sales Order i am getting an error as Could not commit transaction Error 1 Detected During Transaction G/L Account

Hi,
Plz find the following threads:
Transaction failure with error message \"Error -1 detected during transaction\" when update the G\\L Account D…
"Could not commit transaction: Error -1 detected during transaction"
Could not commit transaction: Error -1 detected during transaction 'Payment Methods for Payment Wizard' (OPYM)
Could not commit transaction when inserting new items

"Could not commit transaction: Error -1 detected during transaction"

hi guys,
im getting this error "Could not commit transaction: Error -1 detected during transaction" when trying to create standard document/s. i am now using B1 8.8, MS SQL 2008.
originally, my program was written for B1 2005, MS SQL 2005, and it WORKED.
we upgraded into B1 8.8, MS SQL 2008, and now my program is not working. it is now having the mentioned error upon committing transaction (vCompany.EndTransaction(wf_Commit)). tried removing transaction handling, and it WORKED. also, tried simplifying the program, instead of creating multiple documents, i modified it in just creating one document with transaction handling, and it WORKED.
initialliy, this issue seems to be related to MS SQL 2008.
please help, thanks.

Hi Emmanuel........
You get this error due to the Approval Procedure.
Please check if it is activated then please deactivate it from Administration> Approval> Approval Template.......
Then try.......
Regards,
Rahul

Failed to add data -1116 could not commit transaction

Hello Experts
After installation of our add-on on client machine with SAP 8.8.1. we have received this error:
"Failed to add data -1116 could not commit transaction" after traing to add data to our table by using this code :
Dim oUserTable As SAPbobsCOM.UserTable
oUserTable = oCompany.UserTables.Item("UserTab")
'Set default, mandatory fields
oUserTable.Code = UniqueID
oUserTable.Name = UniqueID
'Set user field
oUserTable.UserFields.Fields.Item("U_UserField").Value = "UserValue"
oUserTable.Add()
What should I do?
Thanks

Hello
Also execute the following statement on server in a query analizer
select @@version
if the versions (client and server) are the same it is correct. If not, you can apply the sql native client (sqlncli.msi) from sql server patch
regards
János

Lock wait timeout: Could not commit JPA transaction

We are using MySQL v5.1.67 under Solaris (SmartOS) in a zone. We are using Java EE and Jetty as our servlet container (Hibernate, Ehcache). Sometimes we get: "Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Error while commiting the transaction" and then "Lock wait timeout exceeded; try restarting transaction". We have the database as one file instead of one file per table. The file is large about 20 GB. There are millions of rows in many tables. One table has 30 million rows. Some table has varchar(255)s. Some others have texts. It seems like cells in the database has been broken. Because if you try to update the same entry in the DB you get a "Lock wait timeout exceeded; try restarting transaction", just by issuing a MySQL query. The problem persists until you restart the DB server. Sometimes they start appearing again after a while. Now they seem to come more and more often. There are a lot of threads in the Java EE .war application. We send more and more JMS messages. There is also PHP-code accessing the database. How do we stop this problem from occuring?

I don't think it's threads deadlocking. I've seen this problem many times before and I've always been able to fix it by restarting the MySQL-server. Then it executes normally day after day. Then something special happens and then it fails every day until I restart mysql. I've also encountered the same problem using the test database I have on my local machine. Only one job executes, the one I'm testing. First it works every run. Something special happens usually triggered by errant code. I fix the error. The job continues to fail with the same message "Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Error while commiting the transaction". If try to do a simple UPDATE SQL query accessing exactly the row that's been corrupted, I get a lock wait timeout. But if I restart the database it starts working again. The update works and the Java job works both locally and on the server. But now a special job has experienced more severe problems of this nature. I restart mysql and the job works when triggered manually but not when triggered chronologically on schedule. Actually all failed first and then a few worked but most failed. It's the same job executing multiple times.

Error HRWPC_FC_EXEC - could not start transaction

Hi, am getting error when access MSS ePortal a particular transaction give me the error HRWPC_FC_EXEC - could not start transaction, and other transactions are working fine. Any one pls advise how to check and we miss anything?
thanks in advance.
Regds

Hello,
Please set parameter ~webgui_theme with value "sl" in the HRWPC_FC_EXEC service under GUI configuration. That you will find in the interactive options of service data. After saving this service please also run the transaction SITSPMON -> Templates and Mimes -> go to "Invalidate cache" and select System wide/Application server.
Hope it helps,
Christine

Item Could not commit action because it is currently in focus error.

Hi experts,
we developed addons for our client in 2007 B version.
Recently we upgraded our client server from SAP 2007B to 8.8.
The addons worked fine in 2007B.when we upgraded to 8.8 the error is occuring like
"Item-could not commit action because item is currently in focus [66000-23]"
when i disable a textbox(already it is focus) in my form the above error is occuring.
But this error was not happened with 2007B.
Please tell me is there any solution with out changing the code(i am unable to change the code).
Thanks in advance.
Edited by: vivek.Y on Jun 11, 2011 5:15 PM

Hi Jonathan,
Besides setting the focus and trying to disable the control, it was still throwing exception. So I tried a following:
Work around for this issue.
                                    Try
                                        oForm.Items.Item("ControlWithFocus").Enabled = False
                                    Catch ex As Exception
                                        Dim oItem As Item = oForm.Items.Item("AnyOtherItem")
                                        oItem.Click(BoCellClickType.ct_Regular)
                                        oForm.Items.Item("ControlWithFocus").Enabled = False
                                    End Try
This is a trick where you can set focus to another control and set enable to false.
Hope this helps.
Regards,
Kashif Ali
Edited by: Kashif Ali on Sep 21, 2011 11:43 AM

SRM Error : Could not start transaction.

The user want to approve the SC and is getting the error
"Cannot Start the Transaction"
"Return data for Work Item could not be read"
Please let me know how to fix this issue.

Hi,
Are there any dumps? What version of SRM are you using?
Regards,
Prasanna

Could not create JVM Virtual machine(While starting soa managed server)?

Hi,
While starting managed server I am getting following errors:
Could not commit 1048576KB heap memory at 0x0000000004790000.
Could not create JVM Virtual machine.
After above error SOA managed server is to be down.
Please help me that how can i resolve this issue.
Thanks
Dharm

Hi Dharm,
This is typically printed when we are short on memory.
What is OS version and JDK being using here ? 32bit or 64bit ?
Current Xms and Xmx values ?
Thanks,
Sharmela

Could not commint action because item is currently in focus

Hi,
I have 2 scenarios new and existing in exiting i will show grid and in new edit box.
I f user is in edit box and select existing radio button then i am getting bellow error.
"could not commit action because item is currently in focus". kindly help me how to disable item when there is a focus.

Hello,
You can use the click sub to set the focus.
So put a EditText into you screen, and when you would like to disable your item, move the cursor to the EditText
oform.items.item("DUMMYEDITTEXT").Click ()
'Now you can disable to the item you wanted.
Best Regards,
János

Could we get a deadlock error on COMMIT (END TRANSACTION) in BDB-SQL

According to the DB_TXN->commit documentation at:
http://download.oracle.com/docs/cd/E17076_02/html/api_reference/C/txncommit.html
"After DB_TXN->commit() has been called, regardless of its return, the DB_TXN handle may not be accessed again.
If DB_TXN->commit() encounters an error, the transaction and all child transactions of the transaction are aborted."
Since BDB-SQL uses the BDB engine, should the code handle such errors in BDB-SQL?
Another point to keep in mind is that, post BDB-SQL version 5.1 upon receiving a potential deadlock error all the previous operations(child transactions) in the same transaction are still valid and can be committed.
It would be great if someone can throw some light on this.
Edited by: user10942853 on Jul 28, 2011 9:31 AM

user10942853 wrote:
LaurenFoutz wrote:
I do not think commit can experience a deadlock error since it does not obtain any new locks, and it could not have been in a blocked state if you are able to call commit. Either way, after calling commit on a transaction in SQL the transaction is done, even if an error is returned. At that point if an error is returned the transaction (and all the work its children have done) is either aborted under the covers, or the database has been corrupted, and all future calls to it will return a corruption error that will require restarting the database to restore it (and the restoration will roll back any work done by the transaction since it did not complete cleanly).
Hope that answers your question.
Lauren FoutzLauren, thanks for the reply. From your reply, though there is little possibility that we can get an error on commit looks like we should be prepared to handle such errors in BDB-SQL. We have had instances where we experienced an error on commit while using native BDB (without SQL API) and wanted to confirm the same.You are correct. Error when committing are rare in both the SQL and native API, but they can happen and you should deal with them when they do.
Lauren Foutz

Could not turn on auto-commit in an active global transaction

Why and when does toplink throw this exception
09/09/28 17:50:58 Caused by: java.sql.SQLException: could not turn on auto-commit in an active global transaction
09/09/28 17:50:58 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
09/09/28 17:50:58 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
09/09/28 17:50:58 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
09/09/28 17:50:58 at oracle.jdbc.driver.PhysicalConnection.disallowGlobalTxnMode(PhysicalConnection.java:4045)
09/09/28 17:50:58 at oracle.jdbc.driver.PhysicalConnection.setAutoCommit(PhysicalConnection.java:1343)
09/09/28 17:50:58 at oracle.jdbc.OracleConnectionWrapper.setAutoCommit(OracleConnectionWrapper.java:107)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionImpl.setAutoCommit(ManagedConnectionImpl.java:572)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionImpl.initForUse(ManagedConnectionImpl.java:167)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionImpl.<init>(ManagedConnectionImpl.java:106)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:171)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(ApplicationConnectionManager.java:1398)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnectionFromFactory(ConnectionPoolImpl.java:327)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl.access$800(ConnectionPoolImpl.java:98)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl$NonePoolingScheme.getManagedConnection(ConnectionPoolImpl.java:1211)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:785)
09/09/28 17:50:58 at oracle.oc4j.sql.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:45)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.getConnectionFromPool(ApplicationConnectionManager.java:1596)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.acquireConnectionContext(ApplicationConnectionManager.java:1541)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.allocateConnection(ApplicationConnectionManager.java:1486)
09/09/28 17:50:58 at oracle.j2ee.connector.OracleConnectionManager.unprivileged_allocateConnection(OracleConnectionManager.java:238)
09/09/28 17:50:58 at oracle.j2ee.connector.OracleConnectionManager.allocateConnection(OracleConnectionManager.java:192)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:272)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:200)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:142)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:127)
09/09/28 17:50:58 at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:145)
Thanks,
ND

Hello,
As you can tell from the stack trace, TopLink is not throwing the exception, the connection is when TopLink is attempting to get a connection from the datasource. getConnection should not be throwing this exception, so it is likely a datasource configuration issue or a problem in the driver you are using. How is the datasource configured, what is the version of Oc4J and the driver you are using, and can you try using a different driver version?
Best Regards,
Chris

Deadlock - Could Not Commit Transaction

Similar Messages

Maybe you are looking for