• State Not Answered
  • Replies 4 replies
  • Subscribers 20 subscribers
  • Views 540 views
  • Users 0 members are here
Options
Related

QMMAD 8.15 - RUM processing failed with "Operation was interrupted unexpectedly" and "Not all privileges or groups are assigned to the caller"

vladimir heifets_25324
4 months ago

Hello

I am processing workstations using QMM RUM console. Most workstations/servers of the source domain are processing fine; but I have 2 groups of workstations that are failing with the following errors:

1) "Operation was interruped unexpectedly". The last entry in that workstations' log file is "Requesting the agent to start processing". The processing is requested using remote agents, only file system and registry, shares and printers are being processed for now.  The error comes up after the workstation was pending during estimation phase, it never seem to actually start processing and then fails after a few minutes of "estimating". The "show progress" window does NOT show any counts for the work to be done.

2) "Not all privileges or groups are assigned to the caller" - the workstations fail after estimating the work, and "show progress" window does show the counts of files, registry entries etc to be processed, but no processing actually takes place. The user ID used for processing is a member of the local Administrators and Backup Operators groups on the workstations being processed.The last entry in that workstations' log file is "Requesting the agent to start processing". The processing is requested using remote agents, only file system and registry, shares and printers are being processed for now. 

I would appreciate any pointers on how to solve these issues; google search and the knowledgebase search at Quest do not come up with any useful suggestions.

Thank you

Vlad

  • 0 4 months ago

    Update on "operation was interrupted unexpectedly" - turns out, these were just really old machines running W2K8 and they blue screened during re-ACLing.  I RDP'd to the machines directly and re-ACLed them using the command-line vmover. 

    The second issue is still outstanding, and I would appreciate any pointers on how to resolve this. Both QMM RUM console and command-line vmover report the same error, and re-ACLing cannot proceed.

    Thanks

    Vlad

  • 0 4 months ago

    Item 2) is a generic Windows OS error that suggests that something is blocking the privileges of your agent service account.

    Is there some kind of endpoint protection running on these machines? 

    How are your RUM service account(s) being granted their local admin rights - is it by a group embedded in local admins or directly via restricted groups GPO or other method?

  • 0 4 months ago in reply to JohnnyQuest

    Thank you for the reply. The computers with the problem are all located in one OU, to which a custom GPO is linked. This GPO altered the defaults of User rights assignments. I made the changes to the GPO as recommended by https://support.quest.com/migration-manager-for-ad/kb/4349134/-error-1300-not-all-privileges-or-groups-referenced-are-assigned-to-the-caller 
    I also added the QMM user account into other user rights assignments, such as "Log on as a batch job", "Log on as a service", "Restore files and directories", "Take ownership of files or other objects".  
    The servers were restarted when possible for the GPO changes to take effect, or had GPUPDATE /force run on them when restart was not an option. 
    After the restart, I ran whoami /priv in a command window while logged on as the QMM service account configured in the GPO, and I see the privileges listed in "Disabled" state. QMM RUM reports "not all privileges assigned". It appears that the GPO modifications did not work, what can I do to make sure they apply?

  • 0 4 months ago in reply to JohnnyQuest

    Also to answer your questions: endpoint protection is not an issue since other machines with the same configuration are processed fine; this issue only affects half a dozen servers in one particular OU; computers in other OUs are processing just fine.  The RUM service account is in the local Administrators group, and I also added it to Backup Operators to troubleshoot - it didn't help.  The GPO linked to that OU is the problem; I need to know which specific user rights assignments need to be assigned to my RUM service user (in addition to the assignments already granted)