Navision Application Server Stops running

DyNav4 · 2009-05-25

Hello,

i am working with an Web Service, that communicates with the Navision Application Server and finally Navision.

Most of the time it works, but sometimes the Application Server goes down.

Here is a snipped of the event log : After this entry, the NAS is down.

.... The following information is part of the event: nassql.exe; 5.0.26084.0; 47b39e02; msxml4.dll; 4.20.9870.0; 48e2ba47; 0; 0000fa38.

One reason could be, that the content of the xml stream contains an "<" or ">" sign, in that case the xml would appear corrupt, another error could be ....?? - that's my question to the community.

Environment:
Windows 2003 Server, latest SP's
SQL Server 2005, latest SP's
Navision 5 SP 1
4 GB Ram

Has anyone of you an idea?

Awaiting your reply

Regards

Peter

ara3n · 2009-05-26

I suggest to do executable upgrade and use 2009 web services. You don't need to use NAS in 2009.

Sog · 2009-05-26

I would let the NAS restart after first second and subsequent errors.
and ara3n, fyi executable upgrade is only possible for tier 1 countries. NAV 2009 has not been released in many tier 2 countries.

ara3n · 2009-05-26

Do you know the release date for G2? Are they going to just release 2009 Sp1. and skip 2009?

jlandeen · 2009-05-26

I've found that XML Ports, XML data and NAV don't always play nicely together when performing these kinds of tighlty integrated functions.

A few things to try:
1) wrap all calls to XML Ports with a codeunit (so you can use IF CODEUNIT.RUN check). If there are any calls that fail the check you can use GETLASTERROR Text to return any errors to the calling application via the regular communication protocol. Wrapping all the logic like this allows you to Trap for any errors that occur and handle them properly BEFORE they can propagate up and possibly kill the NAS.

2) When using XML Dom set the ASYNC Flag to FALSE (this is so that the XML DOM Doesn't start processing the XML Document before it is completely downloaded). This may prevent errors when processing larger XML documents.

Navision Application Server Stops running

Comments

Categories