cancel
Showing results for 
Search instead for 
Did you mean: 
My Areas

Sign in or create account

to get a personalized navigation.

andretvard
CONTRIBUTOR ***

Error messages "The transaction has been silently rolled back before a database update operation"

by andretvard

Hi

 

We are getting the error messages "The transaction has been silently rolled back before a database update operation" when trying to create PurchaseReceipts via API once a day in the morning. 

Sometimes it works without problems but today it's the second time this week when all our requests failed.

 

Could you please advise on how to avoid it?

 

Thank you

8 REPLIES 8
Yildirim
VISMA

by Yildirim (Updated ‎27-08-2020 11:34 by Yildirim VISMA )

Hello Andre, 

Have you tried troubleshooting this issue based on instruction shared at API incidents - Troubleshooting and reporting


Could you please share information in detail about your API Transaction/s ?

Such as,

  1. Used API Endpoint URL / Method
  2. Returned Http Status Code
  3. Returned Response Body (Error Message)
  4. If this is a POST/PUT request then Used RAW JSON script has to be attached

Please also inform us about transaction steps (what are you aiming to achieve with the transaction/s sent etc)

Thank you.
andretvard
CONTRIBUTOR ***

by andretvard

Hi

 

Today we didn't get any errors but yesterday we had 8 occurrences. We don't think it is data related problem since sometimes similar requests work flawlessly and sometimes nothing can get through.

Here is the information about the requests and responses:

 

1. URL: POST /controller/api/v1/PurchaseReceipt/

 

2. Status Code: we didn't record it but it was a not successful code

 

3. Response Body:

{"message":"VismaId: 207f9f82-3225-43bb-bd32-8982eff00fd3. Error creating purchase receipt. Error: The transaction has been silently rolled back before a database update operation."}

 

4. JSON (not exactly this code but identical structure with different values):

JSON: {
    "Lines": [{
            "Operation": "insert",
            "LineType": {
                "Value": "GoodsForDropShip"
            },
            "InventoryId": {
                "Value": "547636"
            },
            "ReceiptQty": {
                "Value": 1.0
            },
            "UnitCost": {
                "Value": 2500.0
            },
            "PoOrderType": {
                "Value": "DropShip"
            },
            "PoOrderNbr": {
                "Value": "000107"
            },
            "PoOrderLineNbr": {
                "Value": 1
            }
        }
    ],
    "ReceiptType": {
        "Value": "PoReceipt"
    },
    "Hold": {
        "Value": false
    },
    "Date": {
        "Value": "2020-08-13T00:00:00"
    },
    "SupplierId": {
        "Value": "50005"
    },
    "LocationId": {
        "Value": "C0013949"
    },
    "SupplierRef": {
        "Value": "76268670"
    }
}

 

Yildirim
VISMA

by Yildirim

Hi Andre,
Thank you for the details. We'll check this out and get back to you. 

andretvard
CONTRIBUTOR ***

by andretvard

Hi

 

We had 5 more occurencies again this Saturday.

One of the requests:

 

URL: /purchasereceipt/
StatuseCode: 500 InternalServerError
Response Body:

{"message":"VismaId: e25b7e95-83df-485c-a524-0aad32581790. Error creating purchase receipt. Error: The transaction has been silently rolled back before a database update operation."}

JSON:

{
	"Lines": [{
			"Operation": "insert",
			"LineType": {
				"Value": "GoodsForDropShip"
			},
			"InventoryId": {
				"Value": "32225"
			},
			"ReceiptQty": {
				"Value": 2.0
			},
			"UnitCost": {
				"Value": 56.96
			},
			"PoOrderType": {
				"Value": "DropShip"
			},
			"PoOrderNbr": {
				"Value": "002982"
			},
			"PoOrderLineNbr": {
				"Value": 1
			}
		}, {
			"Operation": "insert",
			"LineType": {
				"Value": "GoodsForDropShip"
			},
			"InventoryId": {
				"Value": "548153"
			},
			"ReceiptQty": {
				"Value": 10.0
			},
			"UnitCost": {
				"Value": 71.73
			},
			"PoOrderType": {
				"Value": "DropShip"
			},
			"PoOrderNbr": {
				"Value": "002982"
			},
			"PoOrderLineNbr": {
				"Value": 3
			}
		}
	],
	"ReceiptType": {
		"Value": "PoReceipt"
	},
	"Hold": {
		"Value": false
	},
	"Date": {
		"Value": "2020-08-28T00:00:00"
	},
	"SupplierId": {
		"Value": "50005"
	},
	"LocationId": {
		"Value": "C0014245"
	},
	"SupplierRef": {
		"Value": "76388826"
	}
}
Yildirim
VISMA

by Yildirim (Updated ‎31-08-2020 10:34 by Yildirim VISMA )

Hello,

we highly doubt that this is related to PurchaseOrders linked in the POST operation, we're still investigating this.

1) Is it working without errors when you retry the operation with the same payload (Identical PO / PO Line references)
2) Do you happen to have any ipp-request-id belong one of these transactions failed with this error ? 

andretvard
CONTRIBUTOR ***

by andretvard (Updated ‎31-08-2020 15:23 by andretvard )

Hi.

 

1. We have tried to implement the retry logic on this type of errors and it seems that it works without errors on the second attempt. We didn't had so many confirmed cases like this yet but we have seen some.

 

2. Here is one ipp-request-id of the request that failed: 982270da-854d-4a9e-ae9a-d7107bf7d6a8

We have now seen this behavior in both Prod and Test companies.

 

andretvard
CONTRIBUTOR ***

by andretvard

Hi

 

After we talked last week I added some delays to the integration and it seemed to have a positive effect, the errors disappeared.

However, today we have experienced them again on some requests that failed even when retried three times with a 5 second delay.

We got also many other errors like "The column name '[FeaturesSet].[B2CServiceAutoInvoice]' is invalid.\r\nThe column name '[FeaturesSet].[JournalVoucher]' is invalid.\r\nThe column name '[FeaturesSet].[SeveraIntegration]' is invalid.\r\nThe column name '[FeaturesSet].[VatAdjustment]' is invalid.\r\n" but we reported them in another ticket.

Maybe these issues are related as they look like coming directly from the database.

Accepted solution
Yildirim
VISMA

by Yildirim

Hi Andre, 
The team is currently investigating the issues.
Please subscribe to the  The column name '[FeaturesSet].[SeveraIntegration]' is invalid.