Skip to content

Connect-AzAccount fails with error: [Assembly with same name is already loaded] after successfully authenticated with Connect-PartnerCenter #27048

Open
@jaccobezemer

Description

@jaccobezemer

Description

The execution of the cmdlet Connect_PartnerCenter is successful.
Then the execution of the cmdlet Connect-AzAccount fails with the module could not be loaded due to the following error: [Assembly with same name is already loaded]

Or the execution of the cmdlet Connect-AzAccount is successful.
And then the execution of the cmdlet Connect_PartnerCenter fails with the module could not be loaded due to the following error: [Assembly with same name is already loaded]

Script or Debug output

Environment data

Name                           Value
----                           -----
PSVersion                      7.4.6
PSEdition                      Core
GitCommitId                    7.4.6
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Module versions

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     4.0.2                 Az.Accounts                         {Add-AzEnvironment, Clear-AzConfig, Clear-AzConte…
Script     3.0.10                PartnerCenter                       {Add-PartnerCustomerCartLineItem, Add-PartnerCusto

Error output

Resolve-AzError: The 'Resolve-AzError' command was found in the module 'Az.Accounts', but the module could not be loaded due to the following error: [Assembly with same name is already loaded]
For more information, run 'Import-Module Az.Accounts'.

Metadata

Metadata

Assignees

No one assigned

    Labels

    customer-reportedneeds-triageThis is a new issue that needs to be triaged to the appropriate team.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions