You check to see how many messages there are in the IncomingMessages directory on your MessageMaster server (\\MMServer\MessageMasterQueue$), and you find a lot. You notice by examining the file names, that some of the messages are days old, and that as time goes by, there are more and more messages piling up in the queue.
Messages in the queue (each represented by a .XML file), represent messages that have been sent to the server by your clients, but have not been delivered into the MessageMaster database yet. And messages that have not entered the database are not processed against subscriptions, or routed to you.
First, bring up the MessageMaster Console, and examine the Monitor Page. You need to determine the nature of the problem. (See references below to MessageMaster Console and Monitor Page documentation. It is an important tool, and you should become familiar with the information on that page.) Decide which situation you are facing from the list below, and then scroll down to the appropriate solution.
The first thing to do is restart the MessageMaster Delivery service, immediately followed by the MessageMaster Router service. These two services work together to deliver messages from the queue into the database, and to the agent subscriptions. After restarting, monitor again, and see if the situation has improved.
If not, check for a "Last Error" on the Monitor page. The Monitor page only shows the last error, but if you refresh the screen a few times, you get a good idea of what error, or errors, you are facing. If you are getting an error, you'll need to find the cause of the error and resolve it. Check "Router Errors", referenced below, for causes of specific Router Errors.
If it wasn't a particular error that was causing the problem, try restarting SQL Server, and if that doesn't work, restart the machine. MessageMaster relies heavily on a healthy SQL Server, and in turn, SQL Server relies heavily on a healthy system.
If there are no problems but your IncomingMessages queue is still growing, it means that your server is simply not keeping up to the volume of messages that are being generated in your environment. See "The IncomingMessages Queue is Growing", referenced below.
Also, check the registry settings for your MessageMaster server. Be sure you are not limiting the number of messages it is allowed to process each minute. See the MaxPerMinute entry in "Registry Entries for MessageMaster Server", referenced below.