Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Failed to send a partitioned task to the Management Server

Failed to send a partitioned task to the Management Server

Updated November 19, 2018

Overview

When you publish an update, the task fails and generates the following error in Task History:

"Failed to send partitioned task to Management Server <PAS>. Reason: rpcsessionmanagerproxy::instance()->execute() failed with Exception. Message:  Object reference not set to an instance of an object.. Call Stack:    at EminentWare.Core.Server.Jobs.ManagementServerJobOrchestrator.ManufactureJobs()
   at EminentWare.DataGridServer.Executive.ManagementServerJobManager.SubmitTask(RequestContext rc)
   at EminentWare.DataGridServer.Executive.DataGridServerCommunicationsInterfaceImplementation.DispatchToManagementServer(OperationDispatchInfo odi, OperationResults operationresults)
   at EminentWare.DataGridServer.Executive.DataGridServerCommunicationsInterfaceImplementation.EminentWare.DataGridServer.Channel.IDataGridServerCommunications.DispatchCall(OperationDispatchInfo odi, OperationResults operationresults)
   at EminentWare.Core.Server.RPC.rpcsessionmanagerproxy.execute(OperationDispatchInfo odi)"

 

This error also occurs when you pull WSUS/AS server details using the Server Publishing Wizard.  

clipboard_e9d3d60dd251fb845500b2f7a44b34c16.png

Environment

  • All Patch Manager versions
  • Primary Application Server (PAS) and (SAS) servers with or without routing rules

Cause

This error can have multiple causes. It is primarily caused by a communication issue with the management server (PAS, SAS, or Automation Server).

Steps

Check the PAS and SAS servers

Verify that port 4092 on the SAS and PAS is open for two-way communications between both servers. If the PAS cannot communicate with the SAS, you may see the error above. 

Troubleshoot the Automation Server

If your environment does not include an Automation Server, go to the next section.
If your environment includes an Automation Server, perform the following steps:

  1. Log in to the Automation Server.
  2. Open Services (services.msc).
  3. Locate the EminentWare Data Grid Server Service
  4. Start the Eminentware Data Grid Server Service (if not started). 
  5. Troubleshoot any errors. See the following resources for troubleshooting. 
  6. If the EminentWare Data Grid Service is started, verify that the Automation Server Routing Rules (ASRR) are correct. See the following articles for details:
  7. Verify that the error is resolved.
    If the error is not resolved, go to the next section.

Check the Patch Manager servers

Verify that the servers are part of the default pool.

  1. Log in to Patch Manager.
  2. In the navigation pane, expand Patch Manager System Configuration and select Patch Manager Servers.
  3. In the center pane, verify that each server displays as True in the Default Pool column.
    default-pool.png
    If a server in the Default Pool column displays False:
    1. Select the server in the center pane.
    2. In the Action menu, click Patch Manager Server Wizard.
    3. Select Edit an existing Patch Manager Server's configuration settings, and click Next.
    4. In the Server name drop-down menu, select the targeted server, and then click Next.
    5. Select Include this Patch Manager server in the default round-robin pool, and click Next.
    6. Complete the wizard.
  4. Verify that the error is resolved. 
    If the error is not resolved, go to the next section.

Configure the management groups and secondary application servers

This issue can be caused by multiple secondary application servers belonging to separate management groups. If the error continues and you have multiple management groups and multiple secondary application servers, perform the following steps.

  1. Verify that Computer Management receives the same error.
    1. In the Patch Manager navigation pane, expand Enterprise and select Managed Computers.
    2. Right-click a test machine and select Computer Explorer.
    3. Click the System Information tab.
    4. Verify that the error displays in the tab window.
      If the error is not displayed, you are finished.
      If the error displays, go to the next step.
  2. Verify that the necessary servers are available in Application Servers.
  3. In the navigation pane, expand Patch Manager System Configuration > Patch Manager Servers and select Application Servers.

    In some cases, the server will be listed as an automation server under Application Servers or Patch Manager Servers directly.  If it is no longer an automation server, you may need to delete the server from this view for the task to complete.

  4. Verify that the error displays in the tab window.
    If the error is not displayed, you are finished.
    If the error displays, go to the next section.

Consolidate the SAS and PAS into one server

If the error message continues, it may be caused by multiple SAS belonging to separate management groups. Consolidate the SAS and PAS into one server and move the automation server routing rules to the consolidated management group.

  1. Record the existing automation server routing rules.
    1. In the navigation pane, expand Patch Manager System Configuration > Management Groups and select Managed Enterprise.
    2. Select one of the unnecessary management groups.
    3. In the center pane, select the Automation Server Routing Rules tab.
    4. Record the existing rule.
    5. Delete the rule.

      Patch Manager does not support a duplicate Automation Server Routing Rule.

  2. Move the SAS from the unnecessary group to the primary Management Group.
    1. In the navigation pane under Patch Manager System Configuration, expand Patch Manager Servers and select Application Servers.
    2. In the Actions pane, click Patch Manager Server Wizard. 
    3. Select Edit an existing Patch Manager Server's configuration settings, and click Next.
    4. Click the Server Name drop-down menu, select the server that needs to be moved, and then click Next.
    5. Click the Management Group drop-down menu, select the primary management group that will host the SAS, and then click Next.

      Patch Manager may display an error stating that the rule already exists. Click OK to close the error and then refresh your screen. The new rule should display in the console.

Verify that the error is resolved

  1. Repeat the steps in the previous sections for any remaining groups.
  2. Confirm that the error is resolved by checking Computer Management.
    See Configure the management groups and secondary application servers in a previous section for details.
  3. Re-run any failed tasks to confirm they complete as required. 

 

 

 

Last modified

Tags

Classifications

Public