• State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 19 subscribers
  • Views 3868 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

2nd RUM console getting error 0x80090005 Bad Data

eric_bergstrom
over 4 years ago

Hello all-
I've set up a 2nd RUM console so front-line support can move straggler workstations without our intervention. Items to note:
* 2nd console attaches to the ADLDS database and enumerates the collections
• 2nd console has its own local ADLDS instance but set up as a replica of the ADLDS instance on the first console
• Both consoles use the same domain service account
• Server Windows Firewall is disabled on both consoles
* QMMAD version is 8.14

As soon as I try to push an agent, process or move from the 2nd console, the status remains in "In progress" and nothing happens. Both systems are on the same subnet with no firewalls between them. Looking at the RUMController.log I see the agent push session and the error
5/20/2019 10:35:08 AM 7372 Successfully connected to console.
5/20/2019 10:45:50 AM 4236 Analyzing task with ID: 4D739DAB1437784CB1D5C4BD10A233C4.
5/20/2019 10:45:52 AM 4236 Task will be started immediately.
5/20/2019 10:45:52 AM 4236 Task type is Discovery.
5/20/2019 10:45:52 AM 4236 Task contains 2 computer(s).
5/20/2019 10:45:52 AM 4236 Modifying object <GUID=4D739DAB1437784CB1D5C4BD10A233C4>
5/20/2019 10:45:52 AM 4236 aelita-Amm-Status
5/20/2019 10:45:52 AM 4236 update 3
5/20/2019 10:45:52 AM 4236 modification successful
5/20/2019 10:45:52 AM 3864 Modifying object <GUID=BF74B001E84D1B47ADFDF425E6126ED5>
5/20/2019 10:45:52 AM 3864 aelita-Amm-CurrentTask
5/20/2019 10:45:52 AM 3376 Modifying object <GUID=97EA020F58F1E04F9B9CE786C64A1C38>
5/20/2019 10:45:52 AM 3376 aelita-Amm-CurrentTask
5/20/2019 10:45:52 AM 3864 update <GUID=4D739DAB1437784CB1D5C4BD10A233C4>
5/20/2019 10:45:52 AM 3376 update <GUID=4D739DAB1437784CB1D5C4BD10A233C4>
5/20/2019 10:45:52 AM 3864 aelita-Amm-Error
5/20/2019 10:45:52 AM 3864 erase attribute
5/20/2019 10:45:52 AM 3376 aelita-Amm-Error
5/20/2019 10:45:52 AM 3376 erase attribute
5/20/2019 10:45:52 AM 3864 aelita-Amm-LastOperation
5/20/2019 10:45:52 AM 3376 aelita-Amm-LastOperation
5/20/2019 10:45:52 AM 3864 update 2
5/20/2019 10:45:52 AM 3864 aelita-Amm-LastOperationTime
5/20/2019 10:45:52 AM 3376 update 2
5/20/2019 10:45:52 AM 3864 update 20190520144552.0Z
5/20/2019 10:45:52 AM 3376 aelita-Amm-LastOperationTime
5/20/2019 10:45:52 AM 3864 aelita-Amm-Status
5/20/2019 10:45:52 AM 3376 update 20190520144552.0Z
5/20/2019 10:45:52 AM 3376 aelita-Amm-Status
5/20/2019 10:45:52 AM 3864 update 2
5/20/2019 10:45:52 AM 3376 update 2
5/20/2019 10:45:52 AM 3864 modification successful
5/20/2019 10:45:52 AM 3376 modification successful
5/20/2019 10:45:52 AM 3864 Error 0x80090005. Bad Data.
5/20/2019 10:45:52 AM 3376 Error 0x80090005. Bad Data.

I could not find this on the Quest resources referring to this error but it may be a generic Windows error.
Any insight as to what is causing this is greatly appreciated.
Regards,
Eric

:

  • 0 over 4 years ago

    Update: I checked local permissions to the 2nd console and our service account was not a local admin to the box. I've added and will try again when I get another system to process.

  • 0 over 4 years ago

    Upon applying local admin privs to my service account still gives me the error but the output is slightly different. This was issuing a move to a single computer.

    5/20/2019 12:24:02 PM 4236 Analyzing task with ID: DA9C291294BA57459535530BBB9CCA55.
    5/20/2019 12:24:02 PM 4236 Task will be started immediately.
    5/20/2019 12:24:02 PM 4236 Task type is Move.
    5/20/2019 12:24:02 PM 4236 Task contains 1 computer(s).
    5/20/2019 12:24:02 PM 4236 Modifying object <GUID=DA9C291294BA57459535530BBB9CCA55>
    5/20/2019 12:24:02 PM 4236 aelita-Amm-Status
    5/20/2019 12:24:02 PM 4236 update 3
    5/20/2019 12:24:02 PM 4236 modification successful
    5/20/2019 12:24:02 PM 3908 Modifying object <GUID=04AC31DE97CB444EA9199675B74363C4>
    5/20/2019 12:24:02 PM 3908 aelita-Amm-CurrentTask
    5/20/2019 12:24:02 PM 3908 update <GUID=DA9C291294BA57459535530BBB9CCA55>
    5/20/2019 12:24:02 PM 3908 aelita-Amm-Error
    5/20/2019 12:24:02 PM 3908 erase attribute
    5/20/2019 12:24:02 PM 3908 aelita-Amm-LastOperation
    5/20/2019 12:24:02 PM 3908 update 4
    5/20/2019 12:24:02 PM 3908 aelita-Amm-LastOperationTime
    5/20/2019 12:24:02 PM 3908 update 20190520162402.0Z
    5/20/2019 12:24:02 PM 3908 aelita-Amm-Status
    5/20/2019 12:24:02 PM 3908 update 2
    5/20/2019 12:24:02 PM 3908 modification successful
    5/20/2019 12:24:02 PM 3908 Error 0x80090005. Bad Data.

  • 0 over 4 years ago in reply to eric_bergstrom

    Hi Eric,

    Do you get the error message from the 1st RUM Console, processing the same PC?  Under Project in the RUM Console are the Project Credentials ok?

  • 0 over 4 years ago in reply to eric_bergstrom

    Hello Enrico-

    First console processes without any issues. Customer will not give me the service account creds but I can only assume that my creds on the 2nd console are ok as I would have issues even connecting and replicating ADLDS?

    Eric

  • 0 over 4 years ago in reply to eric_bergstrom

    Resolve this be delegating the 2nd console service account Full Administrator to the project from the first console.  

  • 0 over 4 years ago in reply to eric_bergstrom

    Up and running now. Solution was to export the project from my working console and run the MSI that was created on my 2nd console. Then, change the focus of the project on the 2nd console to point to itself - not the first console. Stop and restart the RUM Controller service. We're thinking the import of the project reset some of the ADLDS permissions.