I have tried to open Nav 2017 report but it's not opening then i have tried to run the services of the same but i am not able to open the services.I have attached the error.
I am guessing that if you looked into the Event Viewer you could probably read that the service cannot be started because the port 7046 is already used by another application.
If that's the case then you need to enable NetTcpPortSharing service and add dependencies to both 2017 and 2009 NST services, so both depend on the NetTcpPortSharing service, and then restart them.
Or you need to reconfigure 2009 or 2017 and move it from standard set of ports 7045+ to something different.
I am guessing that if you looked into the Event Viewer you could probably read that the service cannot be started because the port 7046 is already used by another application.
If that's the case then you need to enable NetTcpPortSharing service and add dependencies to both 2017 and 2009 NST services, so both depend on the NetTcpPortSharing service, and then restart them.
Or you need to reconfigure 2009 or 2017 and move it from standard set of ports 7045+ to something different.
Which service ports have you changed? NAV 2017 or 2009? If NAV 2017 - have you updated port numbes in your access url? (The url you entering to connect the RTC client to the NST service?
No, i don't think that you need to do anyting in the console. If you only changed what you've described here it should have no impact on the NAV 2017 NST whatsoever.
I would try to stop or force-stop the 2017 service (by killing the process if necessary), and try to restart it.
Answers
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
I have stopped the nav2009 services and then try to start the Nav2017 services.Now its working properly.
If that's the case then you need to enable NetTcpPortSharing service and add dependencies to both 2017 and 2009 NST services, so both depend on the NetTcpPortSharing service, and then restart them.
Or you need to reconfigure 2009 or 2017 and move it from standard set of ports 7045+ to something different.
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
I have to set a different port for 2009 and 2017.
"Microsoft Dynamics NAV server is Currently not ready to serve request.Try again later,or contact your system administrator."
Do the needful.
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
Is anything i need to do in administration tools->Management Console,,?
I would try to stop or force-stop the 2017 service (by killing the process if necessary), and try to restart it.
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
I have checked with the event viewer which shows some warning:
"The service account has insufficient privileges to remove service principal names from Active Directory".
Guide me..
Check the rights of the service-account.
I think you must look at the part with Enabling the account to register an SPN on itself
I have uninstalled the nav2017 and install it again.Now, everything is working properly.