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
LinkedObjecs in BC14
c.kestas
Member Posts: 15
We are in the process of upgrading NAV2009 to on-prem BC14 and we came across a problem with LinkedObject tables.
We have a number of such tables that we use to read data from other databases.
Although the table property LinkedInTtransation is set to No, when we run the table in BC we get an error that "....linked server <...> cannot begin a distributed transaction...". When we eventually managed to correctly set up distributed transactions between the two servers, the problem went away.
The question then is: Why does BC try to begin a distributed transaction even though LinkedInTtransation is set to No?
We can always properly configure distributed transactions but as you will agree this is not always the easiest of things to do.
Especially when it shouldn't be needed anyway.
NAV2009 was happily pulling the data from the linked server without the need to setup Distributed Transactions.
We have a number of such tables that we use to read data from other databases.
Although the table property LinkedInTtransation is set to No, when we run the table in BC we get an error that "....linked server <...> cannot begin a distributed transaction...". When we eventually managed to correctly set up distributed transactions between the two servers, the problem went away.
The question then is: Why does BC try to begin a distributed transaction even though LinkedInTtransation is set to No?
We can always properly configure distributed transactions but as you will agree this is not always the easiest of things to do.
Especially when it shouldn't be needed anyway.
NAV2009 was happily pulling the data from the linked server without the need to setup Distributed Transactions.
0