How to configure Load Balancing for Session Recording with NetScaler

# Copyright (c) Citrix Systems, Inc. All rights reserved.

<#

.SYNOPSIS

This script is used to sync configurations between Session Recording Servers for load balancing deployment.

.DESCRIPTION

Will do below kinds of actions:

1. Export values from the registry key: HKEY_LOCAL_MACHINESOFTWARECitrixSmartAuditorServer to SrServerConfig.reg;

2. Import from SrServerConfig.reg and overwrite values in registry key: HKEY_LOCAL_MACHINESOFTWARECitrixSmartAuditorServer;

3. Add redirection mapping sr_lb_map.xml in %windir%System32msmqmapping;

3.1 sr_lb_map.xml will consist redirection rule for both http and https, and not port specific.

.PARAMETER Action

Export – to export the registry configurations of Session Recording Server to a registry file

Import – to import the registry configurations of Session Recording Server from a registry file

AddRedirection – to add HTTP/HTTPS redirection for MSMQ

.PARAMETER NetScalerHost

The host name or FQDN of NetScaler.

.OUTPUTS

Exported configuration file (SrServerConfig.reg) or backup configuration file (SrServerConfig.reg.bk)

.EXAMPLE

SrServerConfigurationSync.ps1 -Action Export

.EXAMPLE

SrServerConfigurationSync.ps1 -Action Import

.EXAMPLE

SrServerConfigurationSync.ps1 -Action AddRedirection -NetScalerHost netscaler.xd.local

.EXAMPLE

SrServerConfigurationSync.ps1 -Action Import,AddRedirection -NetScalerHost netscaler.xd.local

.EXAMPLE

SrServerConfigurationSync.ps1 -Action Import,Export,AddRedirection -NetScalerHost netscaler.xd.local

#>

######################

# Parameters section #

######################

Param(

[Parameter(Mandatory = $true)]

[ValidateSet(“Export”, “Import”, “AddRedirection”)]

[string[]] $Action,

[Parameter(Mandatory = $false)]

[string] $NetScalerHost

)

#############################

# Default variables section #

#############################

$SR_SERVER_REG_PATH = “HKEY_LOCAL_MACHINESOFTWARECitrixSmartAuditorServer”

$REG_FILE_PATH = “SrServerConfig.reg”

$REG_BACKUP_FILE_PATH = “SrServerConfig.reg.bk”

$TEMP_REDIRECT_XML = “sr_lb_map.xml”

$REDIRECT_XML_PATH = “$env:windirSystem32msmqmapping”

############# MAIN ###############

Try

{

If ($Action -Contains “export”) {

Write-Host “Exporting current Session Recording Server Configuration to registry file: $REG_FILE_PATH …” -ForegroundColor Green

& REG EXPORT $SR_SERVER_REG_PATH $REG_FILE_PATH /Y

Write-Host “Finish exporting.” -ForegroundColor Green

}

If ($Action -Contains “import”)

{

If (!(Test-Path $REG_FILE_PATH))

{

Write-Host “No $REG_FILE_PATH founded. Aborted.” -ForegroundColor Yellow

Exit 0

}

# Back up previous registry key

Write-Host “Backing up Session Recording Server Configuration to Registry file: $REG_BACKUP_FILE_PATH …” -ForegroundColor Green

& REG EXPORT $SR_SERVER_REG_PATH $REG_BACKUP_FILE_PATH /Y

Write-Host “Importing Session Recording Server Configuration from Registry file: $REG_FILE_PATH …” -ForegroundColor Green

& REG IMPORT $REG_FILE_PATH 2>$null

Write-Host “Finish importing.” -ForegroundColor Green

}

If ($Action -Contains “addredirection”)

{

# Check if netscaler host is given; If not, exit normally with warning.

If(([String]::IsNullOrEmpty($NetScalerHost)))

{

Write-Host “No NetScaler host name is specified. Finish adding redirection.” -ForegroundColor Yellow

Exit 0

}

If (!(Test-Path $TEMP_REDIRECT_XML))

{

New-Item $TEMP_REDIRECT_XML -Type file

}

$SysInfo = Get-WmiObject -Class Win32_ComputerSystem

$LocalFqdn = “$($SysInfo.Name).$($SysInfo.Domain)”

$RedirectXmlContent =

@”

<redirections xmlns=”msmq-queue-redirections.xml”>

<redirection>

<from>http://$NetScalerHost*/msmq/private$/CitrixSmAudData</from>

<to>http://$LocalFqdn/msmq/private$/CitrixSmAudData</to>

</redirection>

<redirection>

<from>https://$NetScalerHost*/msmq/private$/CitrixSmAudData</from>

<to>https://$LocalFqdn/msmq/private$/CitrixSmAudData</to>

</redirection>

</redirections>

“@

# Don’t take care of encoding

$RedirectXmlContent | Out-File -FilePath $TEMP_REDIRECT_XML

Write-Host “Copying $TEMP_REDIRECT_XML to $REDIRECT_XML_PATH …” -ForegroundColor Green

Copy-Item $TEMP_REDIRECT_XML -Destination $REDIRECT_XML_PATH

Write-Host “Restarting MSMQ service …” -ForegroundColor Green

Restart-Service msmq -Force

Write-Host “Finish adding HTTP/HTTPS Redirection for MSMQ.” -ForegroundColor Green

}

Exit 0

}

Catch

{

Write-Host “$_.Exception.Message” -ForegroundColor Red

Exit 1

}

Finally

{

# Nothing to do

}

Related:

Event ID 4863 — COM+ Service Availability

Event ID 4863 — COM+ Service Availability

Updated: February 22, 2008

Applies To: Windows Server 2008

The COM+ service supports COM+ components that are running in COM+ applications, and it enables them to function correctly. Examples include COM+ Queued Components and COM+ Transactions.

Event Details

Product: Windows Operating System
ID: 4863
Source: Microsoft-Windows-Complus
Version: 6.0
Symbolic Name: IDS_E_REMOTE_DTC_LIKELY_DOWN
Message: TransactionManager-&gt;GetWhereabouts failed. If Distributed Transaction Coordinator is configured to use remote host to coordinate transactions, it is likely that remote host cannot be contacted. You can configure Microsoft Distributed Transaction Coordinator (MS DTC) to use local coordinator by clicking MS DTC toolbar button in Component Services MMC snap-in. Since further execution is impossible at this time, server process has been terminated.%1%0

Resolve
Start the Microsoft Distributed Transaction Coordinator

The event message indicates that the problem might be resolved if you enable the Microsoft Distributed Transaction Coordinator (MS DTC). Determine whether the MS DTC is installed and properly configured. If it is not installed, you can use the Add Roles Wizard to add this role service to the Application Server role.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Determine whether the MS DTC is installed

To determine whether the MS DTC is installed:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the console tree of Component Services, click Services (Local).
  4. Scroll through the list of service names to find Distributed Transaction Coordinator.
  5. Confirm that the status of the service is Started. If the DTC is installed but not started, right-click Distributed Transaction Coordinator, and then click Start.

Check the MS DTC configuration

To check the MS DTC configuration:

  1. In the console tree of Component Services, click Component Services (Local).
  2. Expand Computers, expand My Computer, expand Distributed Transaction Coordinator, right-click Local DTC, and then click Properties.
  3. Click the tabs in the Properties dialog box to confirm that the configuration settings are correct.

Enable the MS DTC if it is not installed

To enable the MS DTC if it is not installed:

  1. Click Start, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. Under Roles Summary, click Application Server.
  3. Click Add role services.
  4. On the Select Role Services page, click Distributed Transaction Support. Some role services require the installation of supporting features or role services from other roles. If this is the case, a dialog box appears. Click Add Required Features.
  5. Click Next to proceed to the Confirm Installation Options page.
  6. Click Install. After the installation process starts, input by the operator is not necessary. When the installation process is finished, the status of the installation appears on the Installation Results page.

Verify

You can verify that the required components are installed and that the role services are enabled by using Server Manager.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify the status of installed components and role services:

  1. Click Start, and then click Server Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under Roles Summary, click Application Server.
  4. Under Role Services, confirm that the status of Message Queuing Activation and Distributed Transactions is Installed.

In addition, you can verify that the COM+ operating system component is installed and working properly.

To verify that COM+ is working properly:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the console tree, click Services (Local).
  4. Scroll through the list of service names to find the following services: COM+ Event System (optional), COM+ System Application, DCOM Server Process Launcher, Distributed Transaction Coordinator, Message Queuing, and Remote Procedure Call (RPC).
  5. Confirm that the status of each service is Started.

Related Management Information

COM+ Service Availability

Application Server

Related:

Event ID 4852 — COM+ Service Availability

Event ID 4852 — COM+ Service Availability

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

The COM+ service supports COM+ components that are running in COM+ applications, and it enables them to function correctly. Examples include COM+ Queued Components and COM+ Transactions.

Event Details

Product: Windows Operating System
ID: 4852
Source: Microsoft-Windows-Complus
Version: 6.1
Symbolic Name: ID_QC_MSMQ_GETPROC
Message: GetProcAddress for a Message Queuing API failed. Message Queuing may not be installed correctly.%1%0

Resolve
Install Message Queuing

The event message indicates that the problem might be resolved by installing support for Message Queuing (also known as MSMQ). You can use the Add Roles Wizard to add this role service to the Application Server role.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To add Message Queuing to the Application Server role:

  1. Click Start, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. Under Roles Summary, click Application Server.
  3. Click Add role services.
  4. On the Select Role Services page, click Message Queuing Activation, and then click Add Required Features in the dialog box that appears.
  5. Click Next to proceed to the Confirm Installation Options page.
  6. Click Install. After the installation process starts, input by the operator is not necessary. When the installation process is finished, the status of the installation appears on the Installation Results page.

Verify

You can verify that the required components are installed and that the role services are enabled by using Server Manager.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify the status of installed components and role services:

  1. Click Start, and then click Server Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under Roles Summary, click Application Server.
  4. Under Role Services, confirm that the status of Message Queuing Activation and Distributed Transactions is Installed.

In addition, you can verify that the COM+ operating system component is installed and working properly.

To verify that COM+ is working properly:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the console tree, click Services (Local).
  4. Scroll through the list of service names to find the following services: COM+ Event System (optional), COM+ System Application, DCOM Server Process Launcher, Distributed Transaction Coordinator, Message Queuing, and Remote Procedure Call (RPC).
  5. Confirm that the status of each service is Started.

Related Management Information

COM+ Service Availability

Application Server

Related:

Event ID 4851 — COM+ Service Availability

Event ID 4851 — COM+ Service Availability

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

The COM+ service supports COM+ components that are running in COM+ applications, and it enables them to function correctly. Examples include COM+ Queued Components and COM+ Transactions.

Event Details

Product: Windows Operating System
ID: 4851
Source: Microsoft-Windows-Complus
Version: 6.1
Symbolic Name: ID_QC_MSMQ_UNAVAILABLE
Message: Queued Components requires Message Queuing. Message Queuing is not installed.%1%0

Resolve
Install Message Queuing

The event message indicates that the problem might be resolved by installing support for Message Queuing (also known as MSMQ). You can use the Add Roles Wizard to add this role service to the Application Server role.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To add Message Queuing to the Application Server role:

  1. Click Start, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. Under Roles Summary, click Application Server.
  3. Click Add role services.
  4. On the Select Role Services page, click Message Queuing Activation, and then click Add Required Features in the dialog box that appears.
  5. Click Next to proceed to the Confirm Installation Options page.
  6. Click Install. After the installation process starts, input by the operator is not necessary. When the installation process is finished, the status of the installation appears on the Installation Results page.

Verify

You can verify that the required components are installed and that the role services are enabled by using Server Manager.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify the status of installed components and role services:

  1. Click Start, and then click Server Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under Roles Summary, click Application Server.
  4. Under Role Services, confirm that the status of Message Queuing Activation and Distributed Transactions is Installed.

In addition, you can verify that the COM+ operating system component is installed and working properly.

To verify that COM+ is working properly:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the console tree, click Services (Local).
  4. Scroll through the list of service names to find the following services: COM+ Event System (optional), COM+ System Application, DCOM Server Process Launcher, Distributed Transaction Coordinator, Message Queuing, and Remote Procedure Call (RPC).
  5. Confirm that the status of each service is Started.

Related Management Information

COM+ Service Availability

Application Server

Related:

Event ID 4111 — Microsoft Distributed Transaction Coordinator Service Stoppage

Event ID 4111 — Microsoft Distributed Transaction Coordinator Service Stoppage

Updated: February 22, 2008

Applies To: Windows Server 2008

The Microsoft Distributed Transaction Coordinator service (MSDTC) coordinates transactions, regardless of failures that may occur during the process, so that the work is committed as a single transaction even if the work spans multiple resource managers on multiple computers.

MSDTC is a Windows service. By default, the service is configured as a manual service rather than as an automatic service. However, most applications demand-start the service as needed. If necessary, the administrator can start or stop the service with the Services administrative tool.

Event Details

Product: Windows Operating System
ID: 4111
Source: Microsoft-Windows-MSDTC
Version: 6.0
Symbolic Name: IDS_DTC_SHUTDOWN
Message: The MS DTC service is stopping.%0

Resolve

This is a normal condition. No further action is required.

Related Management Information

Microsoft Distributed Transaction Coordinator Service Stoppage

Application Server

Related:

Event ID 2255 — Message Queuing Operation

Event ID 2255 — Message Queuing Operation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Message Queuing operation provides message authentication, message encryption, dead-letter queues, security settings, and other basic features. If Message Queuing has problems with any of these features, proper Message Queuing operation may suffer.

Event Details

Product: Windows Operating System
ID: 2255
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_WARN_DEADLETTER_QUEUE_ENCRYPTED
Message: The message could not be moved to deadletter queue %1. Deadletter queues should not require privacy of messages. The message will be moved to the system transactional dead letter queue.

This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2255 registry value to desired time in seconds.

Resolve
Change encryption levels

To allow messages to enter a dead-letter queue, set the privacy level of the specified dead-letter queue to None or Optional, or ensure that the messages that are being sent to the queue are encrypted.

For more information about changing the privacy level of queues, see Change the Privacy Level for Queues (http://go.microsoft.com/fwlink/?LinkId=104733).

For more information about sending encrypted messages, see Message Queuing-Encrypted Messages (http://go.microsoft.com/fwlink/?LinkId=104734).

Verify

Verify that the MSMQ Service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the MSMQ Service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Locate the Message Queuing service, and confirm that the value in the Status column is Started.

Related Management Information

Message Queuing Operation

Message Queuing

Related:

Event ID 2256 — Message Queuing Operation

Event ID 2256 — Message Queuing Operation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Message Queuing operation provides message authentication, message encryption, dead-letter queues, security settings, and other basic features. If Message Queuing has problems with any of these features, proper Message Queuing operation may suffer.

Event Details

Product: Windows Operating System
ID: 2256
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_WARN_DEADLETTER_QUEUE_NOT_TRANSACTIONAL
Message: The message could not be moved to deadletter queue %1. The deadletter queue needs to be transactional. The message will be moved to the system transactional dead letter queue.

This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2256 registry value to desired time in seconds.

Resolve
Make the per-app dead-letter queue transactional or the messages being sent to it nontransactional

The dead-letter queue that is specified in the event is nontransactional, but there are transactional messages trying to go there.

To allow messages to go to the dead-letter queue, recreate the dead-letter queue as a transactional queue, or if you have control over the messages that are being sent to the queue, ensure that the messages are nontransactional.

To recreate the dead-letter queue as a transactional queue, create a new transactional queue with all the same properties as the original dead-letter queue, but make the new queue transactional.

For more information about creating queues, see Create Queues (http://go.microsoft.com/fwlink/?LinkId=104735).

Verify

Verify that the MSMQ Service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the MSMQ Service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Locate the Message Queuing service, and confirm that the value in the Status column is Started.

Related Management Information

Message Queuing Operation

Message Queuing

Related:

Event ID 2253 — Message Queuing Operation

Event ID 2253 — Message Queuing Operation

Updated: January 31, 2008

Applies To: Windows Server 2008

Message Queuing operation provides message authentication, message encryption, dead-letter queues, security settings, and other basic features. If Message Queuing has problems with any of these features, proper Message Queuing operation may suffer.

Event Details

Product: Windows Operating System
ID: 2253
Source: MSMQ
Version: 6.0
Symbolic Name: EVENT_WARN_ILLEGAL_DEADLETTER_QUEUE
Message: The message could not be moved to deadletter queue %3. The message was moved to the system transactional dead letter queue.

This event is logged at most once per %4 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2253 registry value to desired time in seconds. Error %1: %2

Resolve
Confirm that a dead-letter queue exists and confirm permissions

A dead-letter queue must exist. It also needs appropriate permissions.

To resolve this issue:

  • Confirm that the dead-letter queue that is specified in the event exists.
  • Determine the user account under which Message Queuing is running.
  • Confirm that the user account has permissions on the specified queue.

Confirm that the dead-letter queue exists

To confirm that the dead-letter queue exists:

  • On the computer that is specified in the queue format name, locate the dead-letter queue that is specified in the event. For more information about queue format names, see Queue Names (http://go.microsoft.com/fwlink/?LinkID=104739).

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Determine the user account under which Message Queuing is running

To determine the user account under which Message Queuing is running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. In the details pane, locate Message Queuing.
  3. Check the Log On As column to see what user the service runs under.

    Note: When Message Queuing is running in workgroup mode, the default user is Local System. When Message Queuing is running in domain mode, the default user is Network Service.

Confirm that the user account has permissions on the specified queue

You must have administrator privileges to confirm Message Queuing user permissions. If you want to modify permissions, you will also must have the Set Permissions permission on the specified queue.

To confirm that the user account has permissions on the specified queue:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, and then expand Message Queuing.
  3. Navigate to the dead-letter queue that is specified in the event.
  4. Right-click the queue, and then click Properties.
  5. On the Security tab, in Group or user names, find the user under which Message Queuing is running. If the user is in this list, go to step 11.
  6. If the user is not already in the list, click Add.
  7. In Enter the object names to select, enter the user under which Message Queuing is running.
  8. Click Check Names to make sure that you are adding the correct permissions.
  9. If the correct user is found, click OK.
  10. In the queue’s security properties, under Permissions, select the Allow check box next to the Send Message permission.
  11. Click OK.

Verify

Verify that the MSMQ Service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the MSMQ Service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Locate the Message Queuing service, and confirm that the value in the Status column is Started.

Related Management Information

Message Queuing Operation

Message Queuing

Related:

Event ID 2251 — Message Queuing System Resources

Event ID 2251 — Message Queuing System Resources

Updated: January 31, 2008

Applies To: Windows Server 2008

Disk, memory, and system resources are assigned to Message Queuing. If these resources become limited, Message Queuing may not function as expected.

Event Details

Product: Windows Operating System
ID: 2251
Source: MSMQ
Version: 6.0
Symbolic Name: EVENT_WARN_LOW_COMMIT
Message: Message Queuing will not be able to accept messages temporarily because system commit is high.

No manual intervention is required at this stage. Once memory utilization has normalized, Message Queuing will automatically resume accepting messages.

Resolve
Monitor low system resources

Common system resources are almost fully consumed. Message Queuing will not operate properly until system resources are freed up. For more information about managing Message Queuing system resources, see Resource Management in MSMQ Applications (http://go.microsoft.com/fwlink/?LinkId=107361).

We recommend that you monitor the number of messages on your computer and processs these messages. If this issue is persistent, you may have to rearchitect your solution.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To monitor Message Queuing with Performance Monitor:

  1. Open a command prompt. To open a command prompt, click Start. In the search box, type cmd, and then press ENTER.
  2. At the command prompt, type Perfmon, and then press ENTER.
  3. In the console tree, under Monitoring Tools, click Performance Monitor.
  4. Click the green plus sign to add a monitor.
  5. On the Add counters tab, in the Counters section, click MSMQ Service.
  6. Select the appropriate counters that you need.

Verify

Verify that there is sufficient available memory and disk space.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that there is enough available memory:

  1. Open Task Manager. To open Task Manager, right-click an empty space on the taskbar, and then click Task Manager.
  2. Click the Performance tab.
  3. Verify the CPU Usage is not 100%.

To verify that there is enough available disk space:

  1. Open Windows Explorer.
  2. Right-click the drive where Message Queuing is located, and then click Properties.
  3. Verify that there is available Free space.

Related Management Information

Message Queuing System Resources

Message Queuing

Related:

Event ID 2250 — Message Queuing System Resources

Event ID 2250 — Message Queuing System Resources

Updated: January 31, 2008

Applies To: Windows Server 2008

Disk, memory, and system resources are assigned to Message Queuing. If these resources become limited, Message Queuing may not function as expected.

Event Details

Product: Windows Operating System
ID: 2250
Source: MSMQ
Version: 6.0
Symbolic Name: EVENT_WARN_LOW_PAGED_POOL
Message: Message Queuing will not be able to accept messages temporarily because system paged pool is low.

No manual intervention is requried at this stage. Once memory utilization has normalized, Message Queuing will automatically resume accepting messages.

Resolve
Monitor low system resources

Common system resources are almost fully consumed. Message Queuing will not operate properly until system resources are freed up. For more information about managing Message Queuing system resources, see Resource Management in MSMQ Applications (http://go.microsoft.com/fwlink/?LinkId=107361).

We recommend that you monitor the number of messages on your computer and processs these messages. If this issue is persistent, you may have to rearchitect your solution.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To monitor Message Queuing with Performance Monitor:

  1. Open a command prompt. To open a command prompt, click Start. In the search box, type cmd, and then press ENTER.
  2. At the command prompt, type Perfmon, and then press ENTER.
  3. In the console tree, under Monitoring Tools, click Performance Monitor.
  4. Click the green plus sign to add a monitor.
  5. On the Add counters tab, in the Counters section, click MSMQ Service.
  6. Select the appropriate counters that you need.

Verify

Verify that there is sufficient available memory and disk space.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that there is enough available memory:

  1. Open Task Manager. To open Task Manager, right-click an empty space on the taskbar, and then click Task Manager.
  2. Click the Performance tab.
  3. Verify the CPU Usage is not 100%.

To verify that there is enough available disk space:

  1. Open Windows Explorer.
  2. Right-click the drive where Message Queuing is located, and then click Properties.
  3. Verify that there is available Free space.

Related Management Information

Message Queuing System Resources

Message Queuing

Related: