Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
"Unable to start a nested transaction.." MODIFY in a VIEW
uwe
Member Posts: 7
We are running a NAV 2009 and a NAV 2013 System.
The databases lie in separate SQL Servers, which know each other as linked servers.
In the NAV2009 database I have a table which I want to access from NAV2013, too.
Records are appended to the table inside NAV2009. Later, some mechanism in NAV2013 reads the records.
Therefor I created an SQL view in the NAV 2013 database and a NAV2013 table object that links to that view. The "LinkedObject" property is YES, the "LinkedInTransaction" property is NO.
So far, everything works fine. I can read the data from NAV2013 code. I can "Run" the table from the NAV 2013 Development Environment and see the data in NAV2013 Windows Client.
Now, there is a Boolean data field that marks a record as not yet read by the NAV2013 system. I want to set the Boolean field to "TRUE", as soon as my NAV2013 code has finished.
Unfortunately, my MODIFY command in NAV2013 C/AL code fails with an error message:
The following SQL error was unexpected:
Unable to start a nested transaction for OLE DB provider "SQLNCLI10" for linked server "XXXXXX". A nested transaction was required because the XACT_ABORT option was set to OFF.
When I klick one of the checkboxes in Windows Client, I get the same error message as soon as the system tries to MODIFY.
Only in SQL Server Management Studio, I can apply an SQL UPDATE to my view without any problems.
Anybody out there, who can help?
Uwe
PS:
These are the MIBUSO links that I visited before my post:
http://mibuso.com/forum/viewtopic.php?f=23&t=55571&hilit=xact_abort
http://mibuso.com/forum/viewtopic.php?f=23&t=37850&hilit=xact_abort
The databases lie in separate SQL Servers, which know each other as linked servers.
In the NAV2009 database I have a table which I want to access from NAV2013, too.
Records are appended to the table inside NAV2009. Later, some mechanism in NAV2013 reads the records.
Therefor I created an SQL view in the NAV 2013 database and a NAV2013 table object that links to that view. The "LinkedObject" property is YES, the "LinkedInTransaction" property is NO.
So far, everything works fine. I can read the data from NAV2013 code. I can "Run" the table from the NAV 2013 Development Environment and see the data in NAV2013 Windows Client.
Now, there is a Boolean data field that marks a record as not yet read by the NAV2013 system. I want to set the Boolean field to "TRUE", as soon as my NAV2013 code has finished.
Unfortunately, my MODIFY command in NAV2013 C/AL code fails with an error message:
The following SQL error was unexpected:
Unable to start a nested transaction for OLE DB provider "SQLNCLI10" for linked server "XXXXXX". A nested transaction was required because the XACT_ABORT option was set to OFF.
When I klick one of the checkboxes in Windows Client, I get the same error message as soon as the system tries to MODIFY.
Only in SQL Server Management Studio, I can apply an SQL UPDATE to my view without any problems.
Anybody out there, who can help?
Uwe
PS:
These are the MIBUSO links that I visited before my post:
http://mibuso.com/forum/viewtopic.php?f=23&t=55571&hilit=xact_abort
http://mibuso.com/forum/viewtopic.php?f=23&t=37850&hilit=xact_abort
0