NAS and Message Queue troubleshooting

 Problem Description

I cannot get the message queue communication to work between the Navision server and the TradePoint server properly.

 Solution

The following tips may help you in configuring your Message Queue communication.

Note that after making changes to the queues you might need to restart the NAS service or the MQ form.

Event log

Check the event log on your server running NAS for warnings. If the NAS did not start correctly you will probably have a notification about this in your event log. Problems might be related to the following:

• The Navision license file needs to be placed in the NAS.exe folder
• The NAS service needs to be running in a Windows account that has the SUPER role in Navision
• If you find a ScriptServer error in the NAS eventlog it is actually related to the fact that ScriptServer does not recieve a response from the NAS.

Message Queue Setup

Make sure that you have set up the queues correctly:

1. Open the "Communications" dialog from the "Manage Your ScriptServer" tool
2. Make sure you have selected Dynamics NAV and clicked update
3. Make sure that your queues point to your NAS server.
   • If you are using an IP-address you should use the TCP:xxx.xxx.xxx.xxx annotation
   • If you are using a server name you should use the OS:servername annotation
4. Open the "TradePoint Setup" dialog in your NAV client
5. Make sure the "to" queue points to the queue at the TradePoint server and the "from" queue points to the queue at the NAS server.

Make sure that permissions are properly set up on the message queues. On both servers, locate the queues as using the Computer Management from the Administrative Tools . Right click each of them and change the security to allow everyone full control.

If you are running NAS and TradePoint on separate servers you should have 1 message queues on each server, not both queues on the same server.

Server Clocks

Make sure there is not a to big time difference on the servers or else the message will be timed out before it has been sent. Ideally the clocks on the NAS server and the TradePoint server should be the same.

Open for Communication

Make sure the communication between the servers work by stopping the NAS or the MQ form depending on what you are running. Then try sending a test message from the Manage Your ScriptServer, Communications dialog. A message should now end up in the message queue on the NAS server. You can check this by starting the Computer Management from the Administrative Tools and check the Queue Messages node which resides under a message queue node.

Firewalls?

Firewalls may result in erratic message queue performance. To ensure that you have a clear communication route, do the following:

On your TradePoint server, start a command prompt and type telnet NAS_IP 1801 where NAS_IP shold be replaced by the IP address of your Nas Server. If you recieve and error then you need to reconfigure your firewall. Then do the same on the NAS server and try to connect to the IP address of your TradePoint server.

A fresh start

Try restarting the Message Queing service and purge the queues from messages.

Complex Network configurations

If your servers are in different domains or if you have a complex network setup, you might need to use TCP communication and specify the IP-addresses instead of just the server names in the queue address. You might also have to open up specific ports in your network, read more about this in the following article about Message Queue network configurations.