Message queuing service ошибка

Symptoms

When you install Microsoft Windows 2000 Service Pack 3 (SP3) or later on a computer that is running the Windows 2000 operating system, you may not be able to locate a private queue in the Computer Management window. If you try to create a new private queue, you may receive the following error message:

Cannot create ‘<Private Queue Name>‘.
Error: The Message Queuing service is not available

Note The <Private Queue Name> placeholder is a placeholder for the private queue name that you provide when you create a private queue.

Cause

When you install Windows 2000 Service Pack 3 or later on a computer that is running Windows 2000, code is added to authenticate the local Remote Procedure Call (RPC) between the message queuing runtime and the local message queuing service. This code supports the local system account that is also the default account. This code also supports domain accounts for domain controllers. You cannot run the Message Queuing service under the local user account. If you try to run the Message Queuing service under the local user account, you receive the error message that is mentioned in the «Symptoms» section.

Resolution

To resolve this problem, follow these steps:

1. Log on to your computer as an administrator.

2. Click Start, and then click
   Run.

   The Run dialog box appears.

3. In the Open box, type
   Services.msc, and then click OK.

   The Services window appears.

4. Locate Message Queuing. Right-click
   Message Queuing, and then click
   Properties.

   The Message Queuing Properties (Local Computer) dialog box appears.

5. On the Log On tab, click Local System account.

6. Click Apply, and then click
   OK.

7. Stop the Message Queuing service, and then start the Message Queuing service.

More Information

Steps to reproduce the problem

To reproduce the problem, follow these steps:

1. On a computer that is running Windows 2000 Service Pack 1, install Windows 2000 Service Pack 3 or later.

2. Restart the computer after you install the service pack.

3. Click Start, and then click
   Run.

   The Run dialog box appears.

4. In the Open box, type
   Services.msc, and then click
   OK.

   The Services window appears.

5. Locate Message Queuing. Right-click
   Message Queuing, and then click
   Properties.

   The Message Queuing Properties (Local Computer) dialog box appears.

6. On the Log On tab, click This account.

7. In the This account box, type
   <user name>. In the Passwordbox, type <password>. In the Confirm password box, type the same
   <password> again, and then click
   Apply.

   Note The <user name> placeholder is a placeholder for the user name that you put in the This accountbox. Make sure that this user account exists on your computer.

   The
   <password> placeholder is a placeholder for the password for the <user name>.

8. Click OK.

9. Close the Services window.

10. Log off the administrator account.

11. In the User name box, type
    <user name>. In the Passwordbox, type <password>, and then click
    OK to log on to the computer.

12. Right-click My Computer, and then click
    Manage.

    The Computer Management window appears.

13. Expand Services and Applications, and then expand Message Queuing.

14. Expand Private Queues. Try to browse through the messages, or try to create a private queue.

    You may receive the error message that is mentioned in the «Symptoms» section.

References

For additional information about frequently asked questions of known issues for Microsoft Message Queuing, visit the following Microsoft Web site:

http://www.microsoft.com/windowsserver2003/techinfo/overview/msmqfaq.mspxFor additional information about public and private queues, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/cc776346.aspx

have had MSMQ working for the past few months but I am suddenly getting this error message:

Message Queue service is not available.

This is when i test it locally when I test it in live i get the follwoing message:

 Unable to validate data.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Unable to validate data.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[HttpException (0x80004005): Unable to validate data.]
   System.Web.Configuration.MachineKeySection.EncryptOrDecryptData(Boolean fEncrypt, Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Boolean useValidationSymAlgo, Boolean useLegacyMode, IVType ivType, Boolean signData) +4961431
   System.Web.Security.MachineKey.Decode(String encodedData, MachineKeyProtection protectionOption) +194
   System.Web.Helpers.AntiForgeryDataSerializer.Deserialize(String serializedToken) +120

[HttpAntiForgeryException (0x80004005): A required anti-forgery token was not supplied or was invalid.]
   System.Web.Helpers.AntiForgeryDataSerializer.Deserialize(String serializedToken) +754
   System.Web.Helpers.AntiForgeryWorker.Validate(HttpContextBase context, String salt) +199
   System.Web.Mvc.ControllerActionInvoker.InvokeAuthorizationFilters(ControllerContext controllerContext, IList`1 filters, ActionDescriptor actionDescriptor) +156
   System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName) +825488
   System.Web.Mvc.Controller.ExecuteCore() +159
   System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext) +335
   System.Web.Mvc.<>c__DisplayClassb.<BeginProcessRequest>b__5() +62
   System.Web.Mvc.Async.<>c__DisplayClass1.<MakeVoidDelegate>b__0() +20
   System.Web.Mvc.<>c__DisplayClasse.<EndProcessRequest>b__d() +54
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +469
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +375

Has anyone come across this problem where it has been working and then stops and any fixes for this?

Edit: I had a few issues setting up msmq see:
MSMQ creating errors: A workgroup installation computer does not support the operation / User’s internal Message Queuing certificate does not exist

My set up we have 6 servers which are load balanced and all have msmq set up, the domain is set up as a Network service and there are two other server which are involved — the doamin controller which receives the messages and serach server which receives the message — i don t kow if there is a problem on all or just one particular server. I have tried to narrow it down by using the Host file (C:WindowsSystem32driversetcHost )and pointing at each server at a time but they still seem to be sporadic in whther they work or not. We do use caching so I’m not sure if this may be affecting anything…

Thanks

When trying to open the Handheld Contact desktop application on the PC/server, you are unable to launch and the following error message appears:

«Unhandled exception occurred in Handheld contact!  Description of the error is: Message Queue service is not available.» 

The Microsoft Message Queuing (MSMQ) component is essentially a messaging protocol that allows applications running on separate servers/processes to communicate in a failsafe manner.  This is configured and maintained via Windows and Handheld Contact just utilizes this feature.  If the service is not installed, running, or experiencing problems then Handheld Contact will also not work by association. 

Below are some tips on resolving this error message:

• Reboot the PC/server where the Handheld Contact desktop application is installed.
• Open the Windows Services window to determine if ‘Message Queuing’ is running.
• Start/Stop the ‘Message Queuing’ service via above steps.
• Uninstall Microsoft Message Queuing from the PC/server:
  • Windows Vista/7
  • Windows 8
  • Windows 10
  • Windows Server 2003
  • Windows Server 2008
  • Windows Server 2012/2016

After uninstalling Message Queuing from the PC/server, a reboot is required.  When the computer restarts, follow the steps to re-install Microsoft Message Queuing.

If any additional error messages appear, please contact support with the exact error.

Note:  If the above suggestions do not work, additional assistance may be required by a Microsoft Windows technician as the root issue will be with the PC/operating system and not Handheld Contact.

On any 64 bit environment the user will need to turn on Microsoft Message Queuing in order for CAREWare to work properly. If it is not turned on, then users will encounter the following error:

Source: jProgBusiness - Message Queuing has not been installed on this computer.
   at System.Messaging.Interop.SafeNativeMethods.MQPathNameToFormatName(String pathName, StringBuilder formatName, Int32& count)
   at System.Messaging.MessageQueue.ResolveFormatNameFromQueuePath(String queuePath, Boolean throwException)
   at System.Messaging.MessageQueue.Exists(String path)
   at jProgBusiness.jBusiness.jURNEncryption.GetEURN(String urn)
   at jProgBusiness.jBusiness.jURNEncryption.EncryptURN(String URN)
   at jProgBusiness.jBusiness.jBusinessClient.ClientAdd(String GUIDToken, jClientAdd NewClientAdd, jBusinessShared BusinessShared, Boolean 
ignoreURN, String importHL7ProviderPK, Boolean skipClientPresearch)
   at jProgBusiness.jBusiness.jBusinessClient.ClientAdd(String GUIDToken, jClientAdd NewClientAdd, Boolean skipClientPresearch, String 
domainToImportTo)
   at jProgBusiness.jBusiness.jBusinessRemote.CLN_Client_Add(String SessionToken, jClientAdd NewClientAdd, Boolean skipClientPresearch, 
String domainToImportToPK)
An error occured while adding a new client to the central database. You will not be able to add a client to the central database at this time.

To install Message Queuing on Windows Server 2012 or 2016

• Open Server Manager.
• Click Add Roles and Features.
• Click Installation Type.
• Click Role-based or feature-based installation.
• Click Next.
• Click Features.
• Expand Message Queuing.
• Click Message Queuing Server.
• Click Directory Service Integration.
• Click HTTP Support.
• Click Next.
• Click Install.

To install Message Queuing on Windows Server 2008 or Windows Server 2008 R2

1. In Server Manager, click Features.
2. In the right-hand pane under Features Summary, click Add Features.
3. In the resulting window, expand Message Queuing.
4. Expand Message Queuing Services.
5. Click Directory Services Integration (for computers joined to a Domain), then click HTTP Support.
6. Click Next, then click Install.

To install Message Queuing Windows 7 or Windows Vista

1. Open Control Panel.
2. Click Programs and then, under Programs and Features, click Turn Windows Features on and off.
3. Expand Microsoft Message Queue (MSMQ) Server, expand Microsoft Message Queue (MSMQ) Server Core, and then select the check boxes for the following Message Queuing features to install:

   * MSMQ Active Directory Domain Services Integration (for computers joined to a Domain).

   * MSMQ HTTP Support.

4. Click OK.
5. If you are prompted to restart the computer, click OK to complete the installation

Message Queuing can also be enabled using Powershell by following these steps:

1. Type Powershell in the search field.
2. Right click Powershell.
3. Click Run as Administrator.

To list the Message Queuing Features:

1. Paste this command: Get-WindowsOptionalFeature –Online | ? FeatureName -match «msmq» | select FeatureName
2. Press Enter.

To enable Message Queuing Feature:

1. Paste this command: Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-Container -All
2. Press Enter.
3. Paste this command: Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-Server -All
4. Press Enter.
5. Paste this command: Enable-WindowsOptionalFeature -Online -FeatureName «MSMQ-HTTP» -All
6. Press Enter.
7. Paste this command: Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-ADIntegration -All
8. Press Enter.

* A restart of the business tier service must be completed after completing any of the above steps in order for CAREWare to recognize the new changes made to the PC/Server. ¶

Back to Installation

Back to Frequently Asked Questions