Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Patch Manager > Failed to send partitioned task to Management Server

Failed to send partitioned task to Management Server

Table of contents
Created by Justin Rouviere, last modified by Justin Rouviere on Jan 23, 2017

Views: 2 Votes: 2 Revisions: 17

Overview

When attempting to push an update, the task fails. Looking in Task History, you see the tasks fail with this error:

"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)"

Environment

Patch Manager where multiple SAS are broken out into Management Groups with specific Routing Rules

Steps

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

 

If an Automation Server (AS) is in use in the environment, verify that the EminentWare Data Grid Server service is started:

  1. Launch the services.msc module from the Automation Server.
  2. Find the EminentWare Data Grid Server service.
  3. If it is not started, highlight it and click start.
  4. If you get any errors refer to the following for common scenarios to resolve the issue:
    1. Troubleshoot error 1064
    2. Troubleshoot error 1069
    3. Requirements for Patch Manager Service account

If you're using an AS and the service is started, verify that the Automation Server Routing Rules (ASRR) are correct:

  1. Automation Server fails to perform work even with correct rules
  2. Additional Automation Server scenarios

 

Verify that the Patch Manager servers are a part of the default pool:

  1. Expand Patch Manager System Configuration.
  2. Select Patch Manager Servers.
  3. In the middle pane, on the far right, confirm the status as True for In Default Pool.
  4. If any appear as False, select the Patch Manager Server Wizard to Edit an existing Patch Manager Server's configuration settings.
  5. Click next and select the server from the dropdown.
  6. Check the box in the wizard Include this Patch Manager server in the default round-robin pool.

 

If the error continues and you have multiple Management Groups and multiple Secondary Application Servers:

1. Verify the same error is received from Computer Management.

a. Expand Enterprise.

b. Click Managed Computers.

c. Highlight a test machine, right click and select Computer Explorer.

d. Click the System Information tab.

e. If you see the same error as reported, continue with the steps.

2. Confirm that the necessary servers are available in Application Servers.

a. Expand Patch Manager System Configuration.

b. Expand Patch Manager Servers.

c. Select Application Servers.

NOTE:  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.

3. This issue is caused by multiple SAS belonging to separate Management Groups unnecessarily.  Consolidate the SAS and PAS into one server and move the Automation Server Routing Rules to the consolidated Management Group.

a. Note the existing Automation Server Routing Rules.

i. Select one of the unnecessary Management Groups.

ii. Select the Automation Server Routing Rules tab from the center pane.

iii. Note the existing rule.

iv. Delete the rule (Patch Manager does not support a duplicate Automation Server Routing Rule).

b. Move the SAS from the unnecessary group to the primary Management Group.

i. Under Patch Manager System Configuration, expand Patch Manager Servers.

ii. Select Application Servers.

iii. Click on the Patch Manager Server Wizard under the Actions pane.

iv. Select Edit an existing Patch Manager Server's configuration settings and click Next.

v. Select the server from the Server Name dropdown that needs to be moved and click Next.

vi. For the Management Group dropdown select the primary Management Group that the SAS needs to move to.

vii. Click Yes for any errors.

viii. For the Server Role dropdown select Secondary Application Server without Management Role.

ix. Click Yes for any errors, click Next and click Finish.

c. Add the required Automation Server Routing Rules to the primary Management Group.

i. Under Patch Manager System Configuration select the desired primary Management Group.

ii. Select the Automation Server Routing Rules tab from the center pane.

iii. Under the Actions pane on the right side select the Add button for the appropriate rule type to re-create the rule.

Note:  You may get an error that the rule already exists.  Click OK for the error and Refresh this pane, the "new" rule should appear.

d. Repeat the above steps for as many groups as the customer has.

e. Confirm the error should be resolved by testing with Computer Management as tested above.

f. Re-run any failed tasks to confirm that they complete.

 

 

Last modified
15:55, 23 Jan 2017

Tags

Classifications

Public