The XXX server is no longer responding

arthNAVarthNAV Member Posts: 4
edited 2012-02-29 in Navision Attain
Hi,

we get this error from our Navision 3.60 clients:

"The XXX server is no longer responding. This is probably because of one the following reasons:

* The Server has been shut down, either manually or as an result of an error.
* Network failure has occured.
* A hardware failure has occurred on the server computer or on your computer.

Try to open the database again from the menu bar by clicking File, Database, Open. Contact your system manager if you need assistance"


We connect from our workstations to terminal servers via Citrix. On these TS, Navision 3.60 client is installed.
We are not experiencing disconnections between workstations and Navision clients, instead it seems that this issue is between the terminal and the application servers...

Could someone confirm our thought? If so, which is the solution?
Every suggestion is welcome...

Thanks

Comments

  • kinekine Member Posts: 12,562
    Check the event log on the DB server for more info.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • arthNAVarthNAV Member Posts: 4
    kine wrote:
    Check the event log on the DB server for more info.

    Hi kine,

    We already checked in both application server (where MSSQLSERVER instace is running) and terminal servers, but there are no evidence of entries about these disconnections/errors.

    This error only shows to the user that is using Navision Client via Citrix Program Neighborhood in that moment.

    Another thing to be said, is that even if the user close both Navision and Citrix, and attempts to connect again, often the problem persists!

    Thanks.
  • kinekine Member Posts: 12,562
    Than try to measure the network for problems, use wire shark or something else to look at the communication...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • ResenderResender Member Posts: 119
    Was their a solution found for this cause we got a simelar setup, and it would be handy to know what caused it. Rather then having to reinvent 'the wheel' when it were to occur.
Sign In or Register to comment.