Answered

Non-recoverable error when attempting to add licensing information to solution

(0) Share

Report

Posted on by cjbarnaby

Hi,

I am attempting to add licensing information to a solution by following this guide Appendix: Add licensing information to your solution - Power Apps | Microsoft Docs. When attempting to run the command pac solution add-license, I get the following error:

Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id:f2077346-abc3-45f9-bda9-b1d9602352e8

The tool's logfiles don't provide any further details.

Prior to running pac solution add-license, I had created an authentication profile for the solution's environment (using pac auth create) and cloned the solution to my machine (using pac solution clone) without any issue, and had created the necessary plan definition and plan mapping .csv files, with all the required details.

The following is the redacted content of the definitions.csv file:

Service ID,Display name,More info URL
b****d,M*******d,https://*********.com
b****d,C*******d,https://*********.com

The following is the redacted content of the mapping.csv file:

Service ID,Component name
b*****d,b******p
b*****d,b******t

I have attempted running the command using each of the following on my Windows 10 machine:

VS Code - Power Platform Tools extension - v 0.2.23
Powershell - Standalone Power Platform CLI - v 1.9.9+g8a4823f
Command Prompt - Standalone Power Platform CLI - v 1.9.9+g8a4823f

Thanks,
Chris

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (5)

Answers (1)

v-jefferni on at

Like (0)

Report
Copy link

Link copied!

Hi @cjbarnaby ,

Please consider raise a ticket on support page:

https://admin.powerplatform.microsoft.com/support

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
Copy link

Link copied!

Hi @cjbarnaby,

I am following this same method for licensing but facing the same issue.

Did you find any workaround on this?

Regards,
Ahmad

Was this reply helpful? Yes No
cjbarnaby 44 on at

Like (0)

Report
Copy link

Link copied!
Hi, @Anonymous ,

A workaround, yes (a solution, no) - following the user Helpful's steps (in the bullet point starting with the words "Take a look at what the command did") in this post, I added the licensing information to the unmanaged solution manually (performing the steps the CLI apparently does under the hood), which seems to have worked (though I've yet to actually submit the package to AppSource).

Like I said, it's a workaround, not a solution, but as far as I can tell, after you've added the licensing information to the unmanaged solution, the Solution Packager tool takes new XML and just adds a few licensing information nodes to the Other\Customizations.xml file. Since this licensing information is unlikely to change between releases, you could save the XML that gets added to the Other\Customizations.xml and then either:
Manually add this XML to the Other\Customizations.xml file in future releases of your solution; or
If you automate your deployments, implement a script in your ADO pipeline along the lines of the one JeffCarma proposed in the same thread
Hope that helps.

Was this reply helpful? Yes No
Verified answer

Community Power Pla... on at

Like (0)

Report
Copy link

Link copied!

Hi @cjbarnaby,

I found the solution to solve this issue. Below is the link

Non-recoverable error when attempting to add licensing information to Power Apps Solution - KAISPE LLC

Regards
Ahmad

Was this reply helpful? Yes No
cjbarnaby 44 on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous - you're right. I'm accepting your answer as the solution, but for future reference to others who come across this (in the event that the page you've linked to no longer exists), there appears to be an issue with the latest (at the time of writing) version of the PAC CLI (v 1.9.9); the pac solution add-license CLI tool, despite being present in v 1.9.9, doesn't work (for me). Reverting to an older version (eg v 1.7.4) works.

@v-jefferni - I don't have the necessary permissions to log a ticket with MS Support. Perhaps you could raise this with the relevant team internally. Thanks.

Was this reply helpful? Yes No