• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 567
  • Last Modified:

MSMQ send works great under XP, fails silently on Server 2003

I have created an application that uses MSMQ on XP.   It is time to being deploying and testing the app.   I have found that when I copy the files to  Windows 2003 Server that nothing ever "shows up" in the queue.  

This is a transactional, private queue reference via the string: @".\private$\myQueueName"

The entire code is surrounded by try-catch blocks, but no error is ever thrown.

I have set the permissions to be as permissive as possible to try to get something to show up in the queue.   (Everybody has full control.)

I am using transactions and the transaction's commit statement executes without any problems.

The queue is created from code, but I have also tried creating it by hand to see if it makes any difference.

I encountered a post on eggheadcafe referencing this exact problem: msmq works under xp, fails under 2003.  Unfortunately, no solution was ever posted.  (http://www.eggheadcafe.com/forumarchives/msmqprogramming/Jun2005/post23331195.asp
)
//get the messageQueue inst. var. ready for use
        MessageQueue messageQueue;
        if(MessageQueue.Exists(AppConst.QUEUE_PATH))
            messageQueue = new MessageQueue(AppConst.QUEUE_PATH);
        else
            messageQueue = MessageQueue.Create(AppConst.QUEUE_PATH, true);
                        
        MessageQueueTransaction mqTrans = new MessageQueueTransaction();
        
        
 
        mqTrans.Begin();
        try
        {
            messageQueue.Send(new Message(strXml,new XmlMessageFormatter()));
            mqTrans.Commit();
            if (AppConst.LOGGING_MODE_ENABLED)
            {
                TextWriter tw = File.AppendText(AppConst.QUEUE_TRANSACTION_LOG);
                tw.WriteLine();
                tw.Close();
            }
        }
        catch( Exception ex )
        {
            if (AppConst.DEBUGGING_MODE_ENABLED)
            {
                TextWriter tw = File.AppendText(AppConst.QUEUE_ERR_LOG_FILE);
                tw.WriteLine(ex.Message+ex.StackTrace+ex.StackTrace+ex.ToString());
                tw.Close();
            }
            mqTrans.Abort();
        }
        finally
        {
            messageQueue.Close();
            payloads.Clear();//Once you send to queue the Collection of payloads gets emptied
        }

Open in new window

0
trey_carroll
Asked:
trey_carroll
  • 2
1 Solution
 
trey_carrollAuthor Commented:
Just discovered that the server that this is running on is Windows 2003 Server SP1.   Could this be the entire problem?
0
 
trey_carrollAuthor Commented:
This error had to do with the fact that the virtual server that this app runs on ran out of memory and became corrupted.
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now