At a client, there was an issue with importing a solution package from Development environment to a UTA, Training and Production envionment. Same symptoms everywhere: The solution package file could not be imported.
Error message: Assembly do not exist.
The solution package included all modified object s and dependencies, except security roles, field security profiles and workflows.
Resolution was to add a separate solution for the plugins and import that solution first.
All SDK messages are kept in the main solution package.
Cause to the issue is not yet identified.
Either the file size of the solution package exceeds limit of object size in IIS configuration or the CRM Developer Toolkit, which was used for deployment of plugins from VS2012 to Development solution, could have made some bindings to the plugin assemblies that are not compatible to the solution package.
Error message: Assembly do not exist.
The solution package included all modified object s and dependencies, except security roles, field security profiles and workflows.
Resolution was to add a separate solution for the plugins and import that solution first.
All SDK messages are kept in the main solution package.
Cause to the issue is not yet identified.
Either the file size of the solution package exceeds limit of object size in IIS configuration or the CRM Developer Toolkit, which was used for deployment of plugins from VS2012 to Development solution, could have made some bindings to the plugin assemblies that are not compatible to the solution package.
No comments:
Post a Comment