Occasionally - perhaps once a month on average for a period of maybe 30 minutes to an hour, NAV (2013 R2) won't accept new connections though anyone already in NAV can carry on working without problem - unless they try to export data to Excel as that, I believe (usually?) needs to create a new connection.
I have seen a couple of unexpected Warning events in Event log on the application server but am not sure they're related. It has always (so far) resolved itself within an hour. During that time, it is possible to connect without problem to our UAT database (different port number).
It happened again this morning and I have now set up a second Service using an alternate port to try to use next time but the main connection started working again just before I could test the new service.
It does not seem related (at least not directly) to the number of users vs our licenses.
My NAV partner suggested checking Net.Tcp Port Sharing Service but I don't have multiple services using the same ports so although it's set to Automatic it is never actually running. If I try to start it, it simply stops again with a message indicating that is because it's not needed.
When it happens it affects all users so is not related to firewall on client machines - and the fact that anyone already in NAV can continue without problem seems to suggest firewall cannot be a factor.
It's not a show-stopper as we (so far) can be confident it will resolve itself every time but I'd still, obviously, like to get to the bottom of it. Any ideas anyone?
*This post is locked for comments
Hello Paul,
Did you find the solution for this problem? I have the same problem too and i cannot find anything right now.
Any suggestions would help.
For people trying to open a new instance of NAV there's a wait of a minute or so and then they get the message:
The program could not create a connection to the server. Do you want to try again?
If I try to switch from our UAT database with Select Server it will try for a minute or so and then error with:
A server was not found at "net.tcp.//ourappserver:10046/ournavservice/Service". Either the URL is incorrect or the server is currently not available.
I haven't checked Job Queues so that's a thought, thank you, Suresh. We do have one job which runs every 15 minutes to integrate with a third-party application but should never take more than a few minutes. When the problem happens again I'll check to see if that's running.
Paul,
What kind of error message do you get at that time ? Are there any job queues or any other processes scheduled to run weekly, or monthly ?
Sohail Ahmed
2
mmv
2
Amol Salvi
2