Cannot start a nested transaction
See original GitHub issueUpgrading to 2.13.1 and see the following errors,
vendor.js:formatted:30800 Uncaught Error: Cannot start a nested transaction
at Object.debugAssert [as assert] (vendor.js:formatted:30800)
at Environment.begin (vendor.js:formatted:29098)
at Environment.begin (vendor.js:formatted:41133)
at InteractiveRenderer._renderRoots (vendor.js:formatted:43915)
at eval (eval at begin (vendor.js:formatted:29098), <anonymous>:1:7)
at Environment.begin (vendor.js:formatted:29098)
at Environment.begin (vendor.js:formatted:41133)
at InteractiveRenderer._renderRoots (vendor.js:formatted:43915)
at InteractiveRenderer._renderRootsTransaction (vendor.js:formatted:43982)
at InteractiveRenderer._revalidate (vendor.js:formatted:44025)
I suppose this is related to the back tracking issues but the error message makes it hard to work back towards the cause. Any ideas on how we would go about debugging this?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:7
- Comments:18 (10 by maintainers)
Top Results From Across the Web
Unable to start a nested transaction for OLE DB provider ...
Unable to start a nested transaction for OLE DB provider "SQLNCLI11" for linked server "RI". A nested transaction was required because the XACT_ABORT...
Read more >Msg 7395: Unable to start a nested transaction
The common solution to this error is to set XACT_ABORT to ON, just like the error recommends. This tells SQL Server that, if...
Read more >SQL SERVER - FIX: Msg 7395, Level 16, State 2 - SQL Authority
SQL SERVER – FIX: Msg 7395, Level 16, State 2 – Unable to start a nested transaction for OLE DB provider ... While...
Read more >"Cannot start more transactions on this session." - Server Fault
A nested transaction was required because the XACT_ABORT option was set to OFF. This local database was moved from 2000 (where queries worked) ......
Read more >Remedy - Unable to update view form via a linked server
Unable to start a nested transaction for OLE DB provider "OraOLEDB. ... "{Server Name}" was unable to begin a distributed transaction."
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
2.13.3 was released this morning with a fix for this assertion.
On Wed, May 31, 2017 at 12:43 PM Alexander Kapelyukhovskiy < notifications@github.com> wrote:
– Jordan Hawker www.JordanHawker.com Senior JavaScript Engineer, Twitch
@RobIsHere / @AlexanderKapelyukhovskiy ah i forgot about bower, but the 2.13.3 version of ember in bower should also resolve the issue.