In my daily job I need to regularly create Application Pools in IIS Manager for our innovative products (portal software which integrates with our Dynamics Add-on for example). If you just need to create one that’s an easy and quick job. However sometimes I need to create at least 8 application pools! Ofcourse this is possible by using PowerShell :) and once again I love it. It makes my work more efficient, repeatable and the quality is more in control and consistent. I not going to paste a lot of code here but will explain only the concept so you can easily build something useful for yourself.
- Open Powershell ISE
- Import the ‘WebAdministration’ module
- Use the New-WebAppPool Cmdlet to create an Application Pool
- Use the New-Website Cmdlet to create a website
Since the introduction of NAV 2016 the Windows Client is now also 64 bit just like the NAV Server. When you install the ‘Role Tailored Client’ from the NAV DVD you will now get 2 Windows Client executables:
- 32 bits version: C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe
Use this client if your NAV partner is using 32 bit COM or .NET Components or of course if your system OS and hardware is still 32 bits…
- 64 bits version: C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.x86.exe
If your OS is 64 bits then the 64 bits Windows Client will start by default. It’s obvious of course that the 64 bits client is the preferred client to use in order to utilize more memory (more than 4096 MB) for heavy reports for example.
Sometimes when installing a new NAV version for a customer I experience problems like a service tier which won’t start. Based on examination of the error in the Application Error log I will then use Telnet to check whether a port is opened or not.
- First install Telnet. By default this feature isn’t installed. You can accomplish this quick with Powershell:
Install-WindowsFeature -Name Telnet-Client -Verbose
- Now you can open a telnet session. First start a Command Prompt. Now type:
telnet ipadress port
- If you see this then the port is open from the current machine to the IP and port you specified:
If you see this then the port is closed:
In the example above I checked if port 1433 is open on the SQL Server. This way I can verify it isn’t a firewall issue.
The ‘Mainstream Support End Date’ for Microsoft Dynamics NAV 2009 R2 has ended on 1/13/2015. As you already may know you can find this info on Microsoft Lifecycle Policy. All supported Products are listed here alphabetically and you can check the Lifecycle information per product. Really useful and easy to find info. So Microsoft Dynamics NAV 2009 R2 will not officially support SQL Server 2016.
Now the question will be… is it possible to run NAV 2009 on A SQL Server 2016 machine? I’ve investigated this question. I’ve installed SQL Server 2016 on Windows Server 2012 R2 (from scratch). Then I restored a NAV 2009 database (Dutch Cronus Database) and installed NAV from the NAV DVD. Result: NAV 2009 R2 does work with SQL Server 2016 as expected. However, I haven’t done intensive testing to say or guarantee that every aspect will function without problems. But at first glance, it looks to work fine at least with the Classic Client. However keep in mind: as long as Microsoft won’t support SQL Server 2016 for ‘the old’ NAV 2009 R2 you should be careful. For those who are interested in the details. The setup and the versions I’ve used:
A dedicated SQL Server: SQL Server 2016 version: 13.0.1601.5
A dedicated NAV Server: NAV 2009 R2 version: 6.00.32942
Both servers are running on Windows Server 2012 R2 as the OS (Build 9600).