Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Problem on Compiling Tables
Ekin
Member Posts: 28
Hello Everyone,
I'm having an issue on compiling tables. Development Environment is unable to see NAV service.
Our architecture is :
Azure SQL Server : Machine A
Azure NAV Server : Machine B
Azure Server : Machine C
We are able to compile tables when we use development environment in Machine B where NAV Server and Services are installed. However, we are not able to compile tables (We can compile other object types). We are planning to use Machine C for development because of various reasons such as Disk Space, reduce number of signed users (Memory usage) etc.
We have opened Management Services port from Azure Portal, and set the outbound rule for the port in Machine B. We have also tried to change server name in SQL Table instead of localhost but we still not able to compile tables.
The only solution have come in our minds is to change Machine C to NAV Server, create a second service for every database and use that service for development and table compilation.
Do you have any other suggestion?
Regards,
Ekin
I'm having an issue on compiling tables. Development Environment is unable to see NAV service.
Our architecture is :
Azure SQL Server : Machine A
Azure NAV Server : Machine B
Azure Server : Machine C
We are able to compile tables when we use development environment in Machine B where NAV Server and Services are installed. However, we are not able to compile tables (We can compile other object types). We are planning to use Machine C for development because of various reasons such as Disk Space, reduce number of signed users (Memory usage) etc.
We have opened Management Services port from Azure Portal, and set the outbound rule for the port in Machine B. We have also tried to change server name in SQL Table instead of localhost but we still not able to compile tables.
The only solution have come in our minds is to change Machine C to NAV Server, create a second service for every database and use that service for development and table compilation.
Do you have any other suggestion?
Regards,
Ekin
0
Answers
Our Management Port service is not 7045, we are using 7645 for that specified database. And the port is open.
Check the Event Viewer too (Application log), since there may be more detailed messages or errors there.
And make sure that you're using finsql.exe from the folder "RoleTailored Client". By default, for Nav 2017 this is:
C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client
We once used a finsql.exe that can be found in the Service folder, and encountered problems when trying to save objects.