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
RUNNING THE NAV2015 SERVICE TIER IN CONSOLE MODE
mbj
Member Posts: 63
When you have many customers on different versions/builds the console mode is very useful.
However it isn’t possible to invoke the service tier with PowerShell - when it’s started in console mode or?
Console mode:
http://www.hougaard.com/running-the-nav2015-service-tier-console-mode/#comment-49
However it isn’t possible to invoke the service tier with PowerShell - when it’s started in console mode or?
Console mode:
http://www.hougaard.com/running-the-nav2015-service-tier-console-mode/#comment-49
0
Comments
The only thing is, with parallell Versions - you msut rememeber to import into ps the module corresponding to the NAV Version you want to manage.
And one session (once a module is uploaded) can only manager one Version, exporting modules won't remove the uploaded Libraries.
So : open a ps session per Version you manage, impot correct module Version for that NAV Version and you should be able to manage NST regardless if it exists, if it is started and how it is started.
If not, contact support