Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New-PartnerAccessToken : Parameter set cannot be resolved using the specified named parameters.

See original GitHub issue

Steps to reproduce

   $AccessToken = New-PartnerAccessToken -Credential $Credentials -Resource $Resource -TenantId $TenantId -RefreshToken $SPNRefreshToken

Expected behavior

Should return AccessToken

Actual behavior

New-PartnerAccessToken : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:24
+ ... cessToken = New-PartnerAccessToken -Credential $Credentials -Resource ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-PartnerAccessToken], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,Microsoft.Store.PartnerCenter.PowerShell.Commands.NewPartnerAccessToken

PS C:\Users\testuser> Get-Module PartnerCenter

ModuleType Version    Name                                ExportedCommands                                                                           
---------- -------    ----                                ----------------                                                                           
Script     2.0.1909.1 PartnerCenter                       {Add-PartnerCustomerCartLineItem, Add-PartnerCustomerUserRoleMember, Connect-PartnerCent...

Issue Analytics

State:
Created 4 years ago
Comments:30 (8 by maintainers)

Top GitHub Comments

2reactions

cblackukcommented, Sep 14, 2019

Exactly… but instead in typical fashion, everything is broken and documentation does not reflect the actual state of affairs… Please fix it guys…

1reaction

ghostcommented, Sep 15, 2019

@chwilfing one of the things that Connect-PartnerCenter does is attempt to configure a country property based on the reseller profile. If the command is not able to get the profile it will leave that value blank, which I believe is the root cause for your issue with the Get-PartnerOffers command. I will look into that, but if this is an issue for you please open a new issue so we can track everything.