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
- 305 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
NAV 2013 Issue
nverma
Member Posts: 396
I just started playing around with NAV 2013 and I am noticing something weird.
Lets say I open RTC and then in the development environment, I go and make some modification to a table. If I try to execute the table, nothing happens. I must close the RTC session and then if i try to execute the table, it opens up. Same thing happens with codeunits aswell.
Any idea how to fix this. Its getting rather annoying close the RTC session every time I want to run something. Am I missing something?
Lets say I open RTC and then in the development environment, I go and make some modification to a table. If I try to execute the table, nothing happens. I must close the RTC session and then if i try to execute the table, it opens up. Same thing happens with codeunits aswell.
Any idea how to fix this. Its getting rather annoying close the RTC session every time I want to run something. Am I missing something?
0
Comments
Never heard of it.
The change listener is a component that hooks to your SQL server to watch for object changes and informs the middle tier service about the change.
I am hesitant do believe the change listener causes your issue.
Did you properly install NAV 2013 (not just copy)? Does a dynamicsnav: URL launch the right client?
There was some trouble with incorrectly registered assemblies. Check out the following blog post:
Installing Microsoft Dynamics NAV 2013 R2 side-by-side with Microsoft Dynamics NAV 2013
I can't find a reference to it, but I read that with newer builds of NAV 2013 (R2) the dev environment tries to locate the right RTC in it's own directory. So, copying the files of the dev environment to the RTC install folder, and launching from there, might help.