• State Not Answered
  • Replies 4 replies
  • Subscribers 20 subscribers
  • Views 562 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
5 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

Parents
  • 0 5 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

Reply
  • 0 5 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

Children
No Data