CRM Plugin Registration Tool

NEW POST: SDK to create Steps for existing plugin

srinivasraor — Tue, 30 Jun 2009 10:00:48 GMT

Hi,
I had used the sdk to register the plugin. Now the requirement is the i need to add the steps to the existing registered plugin using the c# code from another plugin. I had googled it but couldmt find a solution. any help would be appreciated.

thanks
srinivas

ajithg wrote:
Some of you are looking at samples for creating SDKMessageProcessingStep and attaching it to existing plugin

- SdkMessageProcessingStep should be the right choice

- Set the plugintypeid to the pluginType you refer to (Plugin Class)
- You also need to get the SdkMessageId, SdkMessageEntityId
- Set all the properties like Mode, Stage etc.

- Call CrmService.Create method

Look at the sample in the sourcecode of the plugin registartion tool CrmPluginStep.cs

NEW POST: 0x80044331 Error

CarstenGroth — Fri, 26 Jun 2009 07:57:47 GMT

I´m getting 'A validation error occurred. The length of the 'filteringattributes' attribute of the 'sdkmessageprocessingstep' entity exceeded the maximum allowed length of '100'. while registering a plug-in not for all attributes. Tried this with the audit plug-in.

Really annoying

COMMENTED ISSUE: Dependent Assembly Failure (System.IO.FileNotFoundException: Could not load file or assembly )

ajithg — Wed, 24 Jun 2009 20:28:41 GMT

While using this tool I discovered it has an issue where it cannot resolve dependent assemblies during the assembly load portion of assembly registration. See error below.

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly '[Assembly Name], Version=[Assembly Version], Culture=[Assembly Culture], PublicKeyToken=[Assembly Public Key Token]' or one of its dependencies. The system cannot find the file specified.
at System.Reflection.Assembly._GetExportedTypes()
at System.Reflection.Assembly.GetExportedTypes()
at PluginRegistrationTool.AssemblyReader.RetrievePluginsFromAssembly(String path) in C:\Projects\CRM 4.0 SDK\tools\PluginRegistration_2.2\PluginRegistration 2.2\AssemblyReader.cs:line 59
at PluginRegistrationTool.AssemblyReader.RetrievePluginsFromAssembly(String path)
at PluginRegistrationTool.RegistrationHelper.RetrievePluginsFromAssembly(String pathToAssembly) in C:\Projects\CRM 4.0 SDK\tools\PluginRegistration_2.2\PluginRegistration 2.2\RegistrationHelper.cs:line 49
at PluginRegistrationTool.PluginRegistrationForm.btnLoadAssembly_Click(Object sender, EventArgs e) in C:\Projects\CRM 4.0 SDK\tools\PluginRegistration_2.2\PluginRegistration 2.2\PluginRegistrationForm.cs:line 127

I believe this is because the the PluginRegistrationTool.AssemblyReader class is using System.Reflection.Assembly.Load(Byte[]) method to load the specified assembly. My plugin inherits from several layers of base classes, each in their own assembly, and it is these assemblies that it cannot resolve. This is because Assembly.Load provides no pathing context with which references can be resolved. Now I assume, though I did not test, that if my other dll's were in the Plugin Registration Tool's application directory or in the GAC that this would not be an issue. This is not ideal however since plugin debuging already has several extra steps, i.e. registration, without adding GACing or copying files around. I modified the PluginRegistrationTool.AssemblyReader.LoadAssembly(string path) method to use Assembly.LoadFrom(string path) instead of Assembly.Load(Bytes[]) which resolved the issue. Someone may want to consider making this change to the project unless there is some specific reason to use the byte array overload.

Sincerely,
Robb Vandaveer
Sr. Technical Consultant
Tribridge
Comments: I decided to use Assembly.Load for the following reason. Especially in plugin Registration tool, Developers will be loading the same assembly by updating the Code and not changing the version number. I wanted to upload the new file rather than return the old one that was laoded in cache of .NET From MSDN: http://msdn.microsoft.com/en-us/library/1009fa28.aspx The LoadFrom method has the following disadvantages. Consider using Load instead. If an assembly with the same identity is already loaded, LoadFrom returns the loaded assembly even if a different path was specified. If an assembly is loaded with LoadFrom, and later an assembly in the load context attempts to load same the assembly by display name, the load attempt fails. This can occur when an assembly is de-serialized. If an assembly is loaded with LoadFrom, and the probing path includes an assembly with the same identity but a different location, an InvalidCastException, MissingMethodException, or other unexpected behavior can occur. LoadFrom demands FileIOPermissionAccess..::.Read and FileIOPermissionAccess..::.PathDiscovery, or WebPermission, on the specified path. If a native image exists for assemblyFile, it is not used. The assembly cannot be loaded as domain neutral. In the .NET Framework version 1.0 and 1.1, policy is not applied.

NEW POST: Timeout Issue

Novi_Bjoerkvold — Mon, 22 Jun 2009 11:58:57 GMT

Hi Josef.

Have you tried setting PreferredDc in the MSCRM registry to overcome this problem? http://support.microsoft.com/default.aspx?scid=kb;EN-US;954811

Novi Bjørkvold

NEW POST: Plugin Development / Production Environment - invalid reference

ajithg — Fri, 12 Jun 2009 18:20:59 GMT

Use the Export Import funtinality of the tool to import the plugins... It shall be created with same Guid's on prod environment too. Just reset IIS and Async if it had any cache of these assemblies from before.

NEW POST: Error 0x80040216 using Plugin registration tool v2.2/2.0.

ajithg — Fri, 12 Jun 2009 18:18:54 GMT

Do you have privileges? Can you check the server traces?

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Fri, 12 Jun 2009 18:16:40 GMT

!! Jun 2009
Updated the PluginRegistration.exe so that it no longer complains about the Load Assembly error. (I had to rename this to Pluginregistration.exe) and Fixed V3 Callouts to show "Upgraded Callout"

!! Updates in Ver 2.2
* *Support for +Scripting+ for Import /Export operation in the tool*
PluginDeveloper tool shipped in the SDK has the console application support for scripting but i have got many requests to add support for scripting in the PlguinRegistration tool so that they could use it for deployment purposes.
PluginRegistration Tool assumes that you have secure trust established to the CRM server so it doesn't ask for the credentials. If you do want to run the tool across domains, then you can save the credentials of the CRM server in the Windows->Stored User Names repository and run the application.

Usage as follows:
/c:<connectionFileName> /cl:<connectionLabel> /org:<organizationName> /op:<operation> /f:<importExportFilename> /n:<ignoreGuids>
Parameter information:
<connectionFileName> name of the connections file, default: Connections.config
<connectionLabel>* name of the connection label in the connections config file, Example: newconnection
<organizationName> name of the working organization, Required in a multi-org deployment, defaults to the single org in a single org deployment
<operation>* name of the operation, valid entries: import, export
<operationFilename>* name of file you want to export or import, Example: import.xml
<ignoreGuids> boolean value (true or false), ignore guids if you are re-importing a group of plugins/workflows
* denotes requried attributes
All the assemblies need to be imported should be in the same folder as the executing exe and so the export.xml file
/? Show this help

* *Fixed the OutofMemoryException problem when trying to registering a step on an Imported Organization.*
* *Fixed the bug in Image registration wizard (Minimum value cannot be greater than maximum value)*
* *Fixed the bug when updating the Impersonation on Step from specified user to "Current User"*

Please provide you feedback using comments / Discussions /Issue Tracker.

Thanks
-Ajithg

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Fri, 12 Jun 2009 18:15:24 GMT

CREATED ISSUE: Dependent Assembly Failure (System.IO.FileNotFoundException: Could not load file or assembly )

rlvandaveer — Tue, 26 May 2009 15:00:35 GMT

NEW POST: Error 0x80040216 using Plugin registration tool v2.2/2.0.

bobfeller — Wed, 13 May 2009 19:58:25 GMT

Error 0x80040216 using Plugin registration tool v2.2/2.0.

I get the following error when trying to register an assembly. I was able to use this tool successfully for the past 6 months, then I just started getting this error on anything I try to do with the tool, ie Register, Disable step, etc.

Please help.

Unhandled Exception: System.Web.Services.Protocols.SoapException: Server was unable to process request.

Detail: <detail><error>

<code>0x80040216</code>

<description>An unexpected error occurred.</description>

<type>Platform</type>

</error></detail>

at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

at PluginRegistrationTool.CrmSdk.CrmService.Update(BusinessEntity entity) in C:\Users\bfeller.VIRTUAL\Documents\Visual Studio 2008\Projects\CrmSdk\pluginregistrationtool\Web References\CrmSdk\Reference.cs:line 345

at PluginRegistrationTool.RegistrationHelper.UpdateAssembly(CrmOrganization org, String pathToAssembly, CrmPluginAssembly assembly) in C:\Users\bfeller.VIRTUAL\Documents\Visual Studio 2008\Projects\CrmSdk\pluginregistrationtool\RegistrationHelper.cs:line 297

at PluginRegistrationTool.PluginRegistrationForm.btnRegister_Click(Object sender, EventArgs e) in C:\Users\bfeller.VIRTUAL\Documents\Visual Studio 2008\Projects\CrmSdk\pluginregistrationtool\pluginregistrationform.cs:line 290

NEW POST: Plugin Development / Production Environment - invalid reference

fvaalst — Tue, 28 Apr 2009 15:09:46 GMT

We are using the Plugin Registration Tool to register a custom made dll (plugin) in our development environment.
Then we have created several workflows in which we use this plugin.
The next step is to register the plugin in the production environment, also with this Registration tool.

So far so good, but when we export the workflows and import them into the production environment these imported workflows have an invalid reference to the registred plugin. Probably caused by the different plugintypeid...

Because these workflows are quite large, it's a lot of work to create them again in the production enviroment.

Anyone have any ideas how to solve this ?

Thanx in advance.

COMMENTED ISSUE: Unhandled Exception: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

ehanna — Sun, 12 Apr 2009 01:49:00 GMT

Very new to Plugins and I'm trying to register my first on the VPC to gain the experience before putting it on the actual deployment server.

I read the other issue of the 401 error, but it did not help and I think this is a different issue.

1- I wrote the plugin from the sdk so that looks good.
2- Downoaded this plug-in registration tool and I put it in the SDK bin directory.
3- I run it and fill in the basics for the VPC

- New Connection
- localhost
- 5555
- litwareinc.com
- Administrator

and hit connect I get prompted for the password I put the it and I get this error.

Is the registration tool suppose to be in any specific directory?

The error I get:

Unhandled Exception: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at PluginRegistrationTool.CrmSdk.Discovery.CrmDiscoveryService.Execute(Request Request)
at PluginRegistrationTool.CrmConnection.RetrieveOrganizations()
at PluginRegistrationTool.ConnectionsForm.OpenConnection(CrmConnection con)
Comments: Found the issue. For those who may run into the same issue. all you need to do is put in the connect name, the full name of the computer name as MOSS.litwareinc.com and the port 5555 hit connect and it works.

COMMENTED ISSUE: Error Updating Existing Assembly - OnDisk

ajithg — Wed, 08 Apr 2009 19:41:47 GMT

I installed v.2.2 of the Plug-In Registration Tool. I am able to connect to my Organization, load the previously registered assembly, messages etc. I have a new worklow that was added to the assembly so I need to register it. I click the assembly, click Update and then point to the .dll (same name, location etc). It loads the assembly and then I highlight the new item to register and click Update. I get the following error almost immediately:

Unhandled Exception: System.Web.Services.Protocols.SoapException: Server was unable to process request.
Detail: <detail><error>
<code>0x80040216</code>
<description>An unexpected error occurred.</description>
<type>Platform</type>
</error></detail>
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at PluginRegistrationTool.CrmSdk.CrmService.Update(BusinessEntity entity) in E:\PluginRegistration_2.2\PluginRegistration 2.2\Web References\CrmSdk\Reference.cs:line 345
at PluginRegistrationTool.RegistrationHelper.UpdateAssembly(CrmOrganization org, String pathToAssembly, CrmPluginAssembly assembly) in E:\PluginRegistration_2.2\PluginRegistration 2.2\RegistrationHelper.cs:line 297
at PluginRegistrationTool.PluginRegistrationForm.btnRegister_Click(Object sender, EventArgs e) in E:\PluginRegistration_2.2\PluginRegistration 2.2\PluginRegistrationForm.cs:line 291

This is an On-Disk deployment not database. Also, this installation is on Update Rollup 2.

Thanks,

Jeremy
Comments: Can you check the Trace files on the server when this happens. We seem to get the error from the CRM server

CLOSED ISSUE: AssociateEntities plugin message

ajithg — Wed, 08 Apr 2009 19:39:33 GMT

Hi Ajithg, can AssociateEntities plugin message be supported?
Comments: Not in CRM 4

COMMENTED ISSUE: AssociateEntities plugin message

ajithg — Wed, 08 Apr 2009 19:39:26 GMT

Hi Ajithg, can AssociateEntities plugin message be supported?
Comments: Sorry. This is not supported in CRM 4.

NEW POST: Console window remains open behind GUI

ajithg — Wed, 08 Apr 2009 19:37:50 GMT

If you dont use the Console parts, then just build the project as Windows Application.

NEW POST: Error Regstering SharePoint Plugin

ajithg — Wed, 08 Apr 2009 19:37:04 GMT

It should list the Type also when you expand the tree. Unless the assembly is not signed i dont see any issues here

NEW POST: A bug for this tool

ajithg — Wed, 08 Apr 2009 19:34:58 GMT

Try accessing the server from the machine and see if the crentials are correct. (Get the wsdl from IE)

NEW POST: Could not load file or assembly. The system cannot find the file specified.

ajithg — Wed, 08 Apr 2009 19:31:13 GMT

I had fixed this issue now. All you had to do was rename the .exe to PluginRegistration.exe instead of PluginRegistration_2.2.exe. If you had built the project you would not have this issue.

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Wed, 08 Apr 2009 19:29:59 GMT

!! April 2009
Updated the PluginRegistration.exe so that it no longer complains about the Load Assembly error. (I had to rename this to Pluginregistration.exe)

!! Updates in Ver 2.2
* *Support for +Scripting+ for Import /Export operation in the tool*
PluginDeveloper tool shipped in the SDK has the console application support for scripting but i have got many requests to add support for scripting in the PlguinRegistration tool so that they could use it for deployment purposes.
PluginRegistration Tool assumes that you have secure trust established to the CRM server so it doesn't ask for the credentials. If you do want to run the tool across domains, then you can save the credentials of the CRM server in the Windows->Stored User Names repository and run the application.

Usage as follows:
/c:<connectionFileName> /cl:<connectionLabel> /org:<organizationName> /op:<operation> /f:<importExportFilename> /n:<ignoreGuids>
Parameter information:
<connectionFileName> name of the connections file, default: Connections.config
<connectionLabel>* name of the connection label in the connections config file, Example: newconnection
<organizationName> name of the working organization, Required in a multi-org deployment, defaults to the single org in a single org deployment
<operation>* name of the operation, valid entries: import, export
<operationFilename>* name of file you want to export or import, Example: import.xml
<ignoreGuids> boolean value (true or false), ignore guids if you are re-importing a group of plugins/workflows
* denotes requried attributes
All the assemblies need to be imported should be in the same folder as the executing exe and so the export.xml file
/? Show this help

* *Fixed the OutofMemoryException problem when trying to registering a step on an Imported Organization.*
* *Fixed the bug in Image registration wizard (Minimum value cannot be greater than maximum value)*
* *Fixed the bug when updating the Impersonation on Step from specified user to "Current User"*

Please provide you feedback using comments / Discussions /Issue Tracker.

Thanks
-Ajithg