Cannot add provider

Discussion in 'Parallels Remote Application Server' started by Steffen4, Feb 10, 2025.

  1. Steffen4

    Steffen4 Bit poster

    Messages:
    3
    Hi,
    we have a fresh Parallels RAS installation and want to add a hyper-v server as provider, but it always fails with wrong credentials.
    If I user the same credentials I can connect via RDP.
    Firewalls are off on both sites.

    [I 0B/00000041/T5160/P1120] 06-02-25 15:54:59 - Connected to Connection Broker 10.0.1.59:20003
    [E 0C/00001008/T5160/P1120/CC954BC52] 06-02-25 15:55:00 - VDIProvider::HyperV::Impl::CWmiCommonImpl::Connect(Connect to remote server (\\10.0.1.53\root\virtualization\v2) failed : Err : 0x80070005))
    [E 0B/0000000D/T5160/P1120/CC954BC52] 06-02-25 15:55:00 - Failed to establish connection with VDI Provider '(Microsoft Hyper-V, 10.0.1.53)': error [5]
    [I 0B/00000088/T5160/P1120/CC954BC52] 06-02-25 15:55:00 - Updated the preferred Connection Broker information: Agent IDs (2;3), Farm ID (47335AF3-6AEA-4CD0-9ECD-04CAE90539E7), Preferred Connection Broker List (HV-RAS:20002)
    [W 0B/00000033/T5160/P1120] 06-02-25 15:55:00 - Disabled Agent, Code 6, Reason Disabled: Invalid credentials
    [I 0B/00000036/T5160/P1120] 06-02-25 15:55:00 - Disconnected from Connection Broker (Priority: 0, Socket: 00003ca8)

    Does anybody have an idea, what I can do?
    I wanted to contact the support.. but theres only facebook/twitter possible ?!

    Thanks,

    Steffen
     
  2. StevenD19

    StevenD19 Bit poster

    Messages:
    1
    Hi Steffen,

    can you please reach out to [email protected] so we can get into contact and help you with this issue.

    tnx!

    Steven
     
  3. PraviG

    PraviG Bit poster

    Messages:
    2
    It looks like the issue is related to permission errors (0x80070005 indicates "Access Denied") when trying to connect to Hyper-V via WMI. Even though RDP works, you should check that the account you're using has the Hyper-V Administrator role on the Hyper-V server and sufficient WMI permissions. Try running wbemtest on the Parallels RAS server to manually connect to \\10.0.1.53\root\virtualization\v2 using those credentials--if it fails, it's definitely a permission issue. Also, make sure DCOM permissions are set correctly and that CIM service (WinRM) is running on the Hyper-V server. If you still have trouble, you might need to manually adjust group policies or registry settings to allow remote WMI access. As for support, you can try reaching out through the Parallels forums or email if social media isn't ideal.
     

Share This Page