Tag: Inter-process communication

Poison Count is %1 for the message with RecordID %2. The message has reached or exceeded the configured poison threshold of %3. After the Microsoft Exchange Transport service restarted, the message was moved to the poison message queue.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 10001
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: MessageEnqueuedToPoisonQueue
Message: Poison Count is %1 for the message with RecordID %2. The message has reached or exceeded the configured poison threshold of %3. After the Microsoft Exchange Transport service restarted, the message was moved to the poison message queue.
   
Explanation

This Warning event indicates that the transport process detected a message that could harm a Microsoft® Exchange environment. That message was moved to the poison message queue.

The poison message queue is a persistent queue that isolates messages that are detected as potentially fatal to a computer that is running Exchange Server 2007. This queue is typically empty. If no such messages exist in the poison message queue, the queue does not appear in the queue viewing interfaces. For information about how to manage queues, see Managing the Queue Database.
   
User Action

No user action is required. However, we recommend that you contact Microsoft Product Support to report the potentially harmful message that Exchange detected. For more information about how to contact support, visit the Microsoft Help and Support Web site.

Note   Do not delete the poison message from the poison queue. Microsoft Product Support Services may have to examine the message.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Unable to start a DCOM Server: %3. The error:”%%%2″Happened while starting this command:%1

PCIS Support Team Leave a comment
Details
Product: Windows Operating System
Event ID: 10000
Source: DCOM
Version: 5.2
Symbolic Name: EVENT_RPCSS_CREATEPROCESS_FAILURE
Message: Unable to start a DCOM Server: %3.
The error:”%%%2″Happened while starting this command:%1
   
Explanation

The Component Object Model (COM) infrastructure could not activate the requested server. Possible causes include:

  • There is not enough memory available
  • An error occurred with another file that the COM infrastructure depends on.
       
    User Action

    Review the Windows error code displayed in the message. If the error indicates that the system is out of memory, save your work, close other programs, and then try to start the service again. Alternatively, increase the amount of RAM installed on the computer.

    If the message displays a system, server, or configuration error, contact your service support vendor.

    To determine the service vendor

    1. Click Start, and then click My Computer.
    2. Using the executable file name displayed in the message after ‘command:,’ navigate to the program.
    3. Right-click the program name, and then click Properties.
      The Properties dialog box for the program is displayed.
    4. To determine who the vendor is for this service, refer to the Version tab.You can also find the path to the executable file in this tool.

    Related:

    The %1 permission settings do not grant %2 %3 permission for the COM Server application with CLSID %4 to the user %5%6 SID (%7). This security permission can be modified using the Component Services administrative tool. %1 = machine-default, application-specific; %2 = local, remote; %3 = launch, activation; %4 = ; %5 = /; %6 = .

    PCIS Support Team Leave a comment
    Details
    Product: Windows Operating System
    Event ID: 10016
    Source: DCOM
    Version: 5.2
    Symbolic Name: EVENT_COM_ACCESS_DENIED_IN_SERVER_ACTIVATION_OR_LAUNCH_PERMISSION
    Message:

    The %1 permission settings do not grant %2 %3 permission for the COM Server application with CLSID %4 to the user %5\%6 SID (%7). This security permission can be modified using the Component Services administrative tool.

    %1 = machine-default, application-specific; %2 = local, remote; %3 = launch, activation; %4 = ; %5 = /; %6 = .
       
    Explanation

    A program, the Clsid displayed in the message, tried to start the DCOM server by using the DCOM infrastructure. Based on the security ID (SID), this user does not have the necessary permissions to start the DCOM server.
       
    User Action

    Verify that the user has the appropriate permissions to start the DCOM server.

    To assign permissions

    1. Using Regedit, navigate to the following registry value
      HKCR\Clsid\clsid value\localserver32
      The clsid value is the information displayed in the message.
    2. In the right pane, double-click Default.
      The Edit String dialog box is displayed. Leave this dialog box open.
    3. Click Start, and then click Control Panel.
    4. Double-click Administrative Tools, and then double-click Component Services.
    5. In the Component Services snap-in, expand Computers, expand My Computer, and double-click DCOM Config.
    6. In the right pane, locate the program by using its friendly name.
    7. Right-click the program name, and then select Properties.
    8. On the Security tab, in the Launch and Activation Permissions group box, select Customize, and then click Edit.

    Add the user to the permissions list, and give the user the appropriate permissions.

    Related:

    DCOM got error “%%%1” from the computer %2 when attempting to activate the server:%3

    PCIS Support Team Leave a comment
    Details
    Product: Windows Operating System
    Event ID: 10006
    Source: DCOM
    Version: 5.0
    Component: System Event Log
    Symbolic Name: EVENT_RPCSS_REMOTE_SIDE_ERROR
    Message: DCOM got error “%%%1” from the computer %2 when attempting to activate the server:%3
       
    Explanation

    A program on this computer could not access a program on the remote computer.
       
    User Action

    Do one or all of the following:

    • Review the Windows error code displayed in the message.
    • Review the remote computer’s Event Viewer for any related events indicating that a program could not be started or that an access denied error occurred.
    • If this event log indicates an out-of-memory error, tell the user to save his work, close other programs, and then try to access the server again. Or, add more system RAM.
    • If the event log indicates an access-denied error, change the DCOM permissions.

    To change permissions

    1. Using Regedit, navigate to the following registry valueHKCR\Clsid\clsid value\localserver32The clsid value is the information displayed in the message.
    2. In the right pane, double-click Default.The Edit String dialog box is displayed. Leave this dialog box open.
    3. Click Start, and then click Control Panel.
    4. Double-click Administrative Tools and then double-click Component Services.
    5. In the Component Services snap-in, navigate to Computers\My Computer\DCOM Config.
    6. In the right pane, locate the program by using its friendly name.
    7. Right- click the program name and then select Properties.
    8. On the Security tab, select Customize, and then click Edit.
    9. Add the user to the permissions list.

    If these steps don’t solve the problem, contact your technical support provider.

    Related:

    Running WebSocket applications on IBM i

    IBM Leave a comment
    WebSocket represents the next evolutionary step in web communication after Comet
    and Ajax. Both Java™ and Node.js provide support for server side WebSocket.
    mod_proxy_wstunnel is a new module of Apache 2.4 that provides support for the tunneling
    of web socket connections to a back-end WebSocket server. These features can be bundled
    together to run WebSocket solutions on IBM i. This article illustrates how to create
    different WebSocket server-side implementations and associate them with the Apache HTTP
    Server to run WebSocket applications on IBM i.

    Related:

    AJAX techniques within a Tivoli Access Manager WebSEAL Environment

    IBM Leave a comment
    This article describes the challenges found when introducing Asynchronous JavaScript and XML (AJAX) programming techniques into an IBM Tivoli Access Manager (TAM) WebSEAL environment. It provides a brief review of WebSEAL technology and a brief introduction
    to AJAX methods. The considerations are outlined for AJAX developers when working with WebSEAL. The potential solutions to issues
    that can arise are supplied, along with listing best practices that will assists AJAX developers to succeed in a WebSEAL environment.

    Related:

    • No Related Posts