Following Lars script for 3-tier troubleshooting, I’ve created my own script which collects info from PC where Dynamics NAV clients are installed. This info could be used for further investigations and potential problems findings.
Whenever there is a problem with a NAV 3-tier setup, typically we check the same usual things to begin with (SPNs, Delegation, NAV Service account, etc).
Below is a link to a PowerShell script that collects some of this information for you. So rather than logging on to a customer’s NAV Server, then Domain Controller, then looking around in Services, ADSIEdit, Users and Computers, etc, just run the script and it collects most of the usual information in txt files.
I know, officially it’s Dynamics NAV, but honestly, is there anyone in the real world that doesn’t still call it Navision? Anyway, this post is not about naming, it’s about Power.
Yes, these days the new buzzword seems to be power. PowerView, PowerShell and PowerPivot to be more precise.
The purpose of this sample is to illustrate how to use PowerShell and other technologies for managing Dynamics NAV Services. It is on purpose developed to be just about useful as it is, but with lots of scope for further development.
The Microsoft All-In-One Code Site has a new NAV code sample. This time it demonstrates using PowerShell to
1.Get a list of NAV 2009 Services, either on the local machine or on a remote machine, and
2.Start and stop a service
Vertalen
