![]() |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
To create a private queue, you must provide the pathname for the queue, plus additional queue properties needed by your application.
The pathname for a private queue contains the name of the local computer where the messages sent to the queue will be stored, the "PRIVATE$" keyword, and the name of the queue.
When providing the name of local computer, you can use the NetBIOS machine name, full DNS machine name, or a period (".") to designate the computer.
When providing a name for the queue, you can use any character except "\", ";" and "$" as the last character of the name. (Message Queuing reserves names ending with "$". For example, the token "PRIVATE$" is used to specify a private queue.)
The name of the queue is case-insensitive (for example, "MyQueue" and "myQueue" are treated as the same name) and can be up to 124 Unicode characters.
![]() |
---|
Queue names greater than 64 Unicode characters can cause a slight reduction in performance, and they are not easily displayed in Active Directory. |
-
Declare the MSMQQueueInfovariable for the queue.
-
Create a new MSMQQueueInfoobject and assign it to the variable.
-
Specify the pathname of the queue.
In these examples, "." is used to indicate the local computer.
Note:
For Message Queuing servers and independent clients, the local machine is the local computer. However, for Message Queuing–dependent clients, the local machine is the client's Message Queuing server. -
(Optional) Add additional queue properties that might be needed.
The C++ COM code example also specifies the label of the queue.
-
Call MSMQQueueInfo.Createto create the queue.
For a code example using C++ COM, see C++ COM Code Example: Creating a Private Queue.
See Also
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.