Regardin Nav2017 services.

Jacob1227 · 2018-03-26

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.

Note: I also have Nav 2009 in my system.

Slawek_Guzek · 2018-03-26

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.

Slawek_Guzek · 2018-03-26

Look into the Event Viewer for start. You will find more details about what happened there.

Jacob1227 · 2018-03-26

Thanks, Slawek.
I have stopped the nav2009 services and then try to start the Nav2017 services.Now its working properly.

Slawek_Guzek · 2018-03-26

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.

Jacob1227 · 2018-03-26

yaa, you are correct Slawek.
I have to set a different port for 2009 and 2017.

Jacob1227 · 2018-03-26

Now, I am trying to open 2017 RTC which shows below error:

"Microsoft Dynamics NAV server is Currently not ready to serve request.Try again later,or contact your system administrator."

Do the needful.

Slawek_Guzek · 2018-03-26

It usually happens when the NST is compiling objects after a restart. Just wait a few minutes more.

Jacob1227 · 2018-03-26

till now it's showing the same error. Guide me,,

Slawek_Guzek · 2018-03-26

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?

Jacob1227 · 2018-03-26

I have changed the NAV 2009 port number and also stop the services of 2009 still i can't able to open 2017.

Is anything i need to do in administration tools->Management Console,,?

Slawek_Guzek · 2018-03-26

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.

Jacob1227 · 2018-03-27

Thanks, Slawek.
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..

ErictP · 2018-03-27

Provisioning the Microsoft Dynamics NAV Server Account
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

Jacob1227 · 2018-03-27

Thanks, Slawek and ErictP.

I have uninstalled the nav2017 and install it again.Now, everything is working properly.

Howdy, Stranger!

Quick Links

Categories

Regardin Nav2017 services.

Best Answer

Answers