Microsoft Dynamics 365 | Integration, Dataverse...

Error importing solution with plugin package

(3) Share

Report

Posted on by AB-08012035-0

When trying to import a managed solution that contains a plugin package, I get the following error:

Solution "TestPackage" failed to import:
File not found for attribute package with file name kcs_PluginPackageTest.nupkg.
Searched following locations: '/pluginpackages/kcs_PluginPackageTest/package/kcs_PluginPackageTest.nupkg', 
'/pluginpackages/kcs_PluginPackageTest/package/kcs_PluginPackageTest.nupkg', 
'/pluginpackage_kcs_PluginPackageTest.nupkg', '/pluginpackage_kcs_PluginPackageTest.nupkg'

This error occurs when importing into a production environment. In non-production environments, I can import successfully and occurs with any solution that contains a plugin package.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (3)

Answers (0)

Sort by

CliveOld 52 on at

Like (0)

Report
Copy link

Link copied!

Getting the same error too. All types of environments for us, non prod too.

Will be raising a Microsoft support case & will report back how that goes.

Was this reply helpful? Yes No
ND-18062016-0 2 on at

Like (0)

Report
Copy link

Link copied!

Interesting, 6 months later and I am exploring leveraging the dataverse git integration. I am using a plugin package as well and when I attempt to pull my updates that include my plugin package from the main branch into my development environment I am getting a similar error. Has anyone received any updates on this error or insight?

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,421 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi,

Thanks for sharing the error details! The issue you're encountering—"File not found for attribute package with file name kcs_PluginPackageTest.nupkg"—typically occurs when importing a managed solution with a plugin package into a production environment.

Here are a few things to check:

Plugin Package Deployment Folder:

Ensure that the .nupkg file is correctly placed in the expected folder structure:

/pluginpackages/<PluginPackageName>/package/<PluginPackageName>.nupkg

The error message shows multiple paths being searched, so verify that the file exists in one of those exact locations.

Solution Packaging:

When exporting the managed solution, confirm that the plugin package was included properly.

Use the Solution Packager tool to inspect the structure and verify that the plugin package is bundled correctly.

Environment Restrictions:

Some production environments may have restrictions or missing configurations that prevent plugin package imports.

Check if the plugin registration service is enabled and accessible in the production environment.

File Access Permissions:

Ensure that the production environment has access to the file system or blob storage location where the .nupkg file is stored.

Try Reimporting as Unmanaged First:

As a workaround, try importing the solution as unmanaged first to verify the plugin package loads correctly, then convert to managed if needed.

If the issue persists, consider opening a support ticket with Microsoft and include the full solution package and environment details.

Hope this helps!
Please mark this response as helpful if it answered your question.

Best regards!

Was this reply helpful? Yes No