• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 65 subscribers
  • Views 102 views
  • Users 0 members are here
Options
Related

Connect-QADService cmdlet exception

dae yoon
22 hours ago

When I run below cmdlet from server "A", system returns below exception. However, another engineer runs same cmdlet from server "B", it works fine from his end. I was told that probably ARS module is missing but I do not know what ARS module is missing from the server "A". I ran "Get-Module" and it returned me with ActiveRolesManagementShell version 7.4 so I was told that is installed. Do I need any other module?  I'd appreciate your advice!

Connect-QADService "server_name"  -proxy

following exception is returned:

+ CategoryInfo: NotSpecified: (:) [Connect-QADService],COMException

 

Parents
  • 0 6 hours ago

    Is the Active Roles Administration Service version 7.4?

    Your Active Roles Management Shell and Active Roles Administration Service versions need to match.

    Also, Active Roles 7.4 is currently End-of-Life. You should upgrade if that's really what you are using.

  • 0 4 hours ago in reply to Terrance.Crombie

    good morning, Terrance, I greatly appreciate shedding this information with me. I am new to AR. Do you know where AR Administration Service is running from?

    I have server "A", I installed AR management shell yesterday, not aware of v7.4 is in EOL. Do I need to install AR Administration Service on the server "A"? I am possibly speaking non-sense in here.

  • 0 3 hours ago in reply to dae yoon

    The Active Roles Management Shell (with the -proxy parameter) is just a client of the Active Roles Administration Service.

    The Active Roles Administration Service would be storing Virtual Attribute values, as well as running workflows, scripts, policies, and delegating access to Active Directory.

    If you do not have the Active Roles Administration Service installed on a server in your environment, then there is nothing storing Active Roles Virtual Attributes and no need for the Active Roles Management Shell.

    If you are not sure what the name of your Active Roles Administration Service host is, you should consult with your internal teams.

Reply
  • 0 3 hours ago in reply to dae yoon

    The Active Roles Management Shell (with the -proxy parameter) is just a client of the Active Roles Administration Service.

    The Active Roles Administration Service would be storing Virtual Attribute values, as well as running workflows, scripts, policies, and delegating access to Active Directory.

    If you do not have the Active Roles Administration Service installed on a server in your environment, then there is nothing storing Active Roles Virtual Attributes and no need for the Active Roles Management Shell.

    If you are not sure what the name of your Active Roles Administration Service host is, you should consult with your internal teams.

Children