Skip to main content

MSMQ Processing Fails

This occurred when upgrading the Scribe integration product, along with changing the connection settings to a test environment. In this process, MSMQ messages were critical in processing the publisher bridges that create and pass XML messages to a hosted service.

The queue for the message service was unable to process them due to the update, and ended up filling the queue, in several private message queues. The total amount of messages was over 1 GB. You can clear the messages from the MSMQ MMC, but if the process is failing due to resources, which this was, it will create dead-letter messages which have to be addressed.

  1. Backup the .mq files
    1. Note Before you run MQbkup.exe, select a folder to which you will back up the Message Queuing files. This folder must be located on a disk that has at least 2.5 GB of available space.
    2. Open a Command Prompt window.
    3. Change the directory to %WinDir%\System32.
    4. Run the following command:
    5. MQbkup.exe -b Drive:\Folder to Put Backup Files
    6. Note the location of the folder to which you backed up the Message Queuing files, in case you may need to restore them.
  2. Open the Computer Management MMC, click on the Dead-Letter messages, and purge the folder.
  3. Restart the MSMQ service.

Comments

Popular posts from this blog

SQl Upgrade Error - Access to the Path C:\Program Files\Microsoft SQL Server\110\License Terms\SQLServer2012_License_SQLBI_1033.rtf is denied

SQL Upgrade Error - Access to License Denied Ahh a wonderful time to experience an error, when you are upgrading SQL, during a limited window for downtime.  Sop much for the weekend plans eh? No worries, this one is easy.  In my case I received the following when downgrading an edition for a reporting Server that houses several instances.  After the first one processed, I received this error: If I browse to that path, we notice the file is set to read only. Easy enough, lets un-check read only and try again.  Success!  I had to do this for each instance install.  So if you have multiple instances be prepared to set the file to read/write each time.

SCSM Data Warehouse Cube / Dimensions do not process - Event 33573 / 35574

Recently I received an alert from our SQL server "OLE DB error: OLE DB or ODBC Error: Operation Cancelled HY008.   Around that same time, I found a few errors in our Operations Manager log on our SCSM 2012 R2 DataWarehouse Management Server.  Specifically Events 33573 and 33574. Event 33573 Warning Message : An Exception was encountered while trying during cube processing.  Message=  Processing warning encountered - Location: , Source: Microsoft SQL Server 2012 Analysis Services Code: 1092550657, Description: Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'WorkItemDim', Column: 'WorkItemDimKey', Value: '18553'. The attribute is 'WorkItemDimKey'..     Well, that appears that a overnight job did not run for our SCSM data warehouse.  However, when I looked at the Data Warehouse Jobs in the SCSM Console, all of the status were either set to Not Started, or success. Going back to the logs on the SCSM

PowerShell - Add telnet client to Windows Server 2012 R2

I was trying to check port specific communication on  a server, so I decided to power up good old telnet.  Much to my surprise it was not installed on the Server. PowerShell to fix that issue! Add-WindowsFeature telnet-client  All set.  No Reboot needed. -AJ