Freitag, 25. Juli 2008 10:21
I have searched on my problems, but found no solution.
The problem being that old versions of dlls are used in my custom workflows, although I have iisresetted and restarted the CRM services. This happens sometimes, not always, and on an irregular basis.
I am not using any class variables as I read somewhere that one should write the execution in an stateless manner (the constructor not being evaluated every time a workflow is run).
The problem exists regardless of unregistering and re-registering the dll or just update the dll (I am using the SDK Plugin registration Tool to perform the registrations and updates).
Is there some way I can ensure that the old dlls are not being used?
Freitag, 25. Juli 2008 14:58ModeratorYou should restart the CRM Async Service, not IIS. Where are you registering the plugin - Database, Disk or GAC ? And how many CRM servers do you have ?
- Als Antwort markiert Andrii ButenkoMVP, Moderator Samstag, 11. Juni 2011 13:38
Freitag, 25. Juli 2008 15:06
I have (also) restarted the async service. First I registered the assembly on disk, then later in the database, and restarted the async service each time.
In the assembly I am using an external file, which I read using an absolute path on the server. This was not working when I moved the assembly to the database. That was solved using a UNC-path. And this is also how I know the workflows are using the older versions. When the workflows errors out it's due to the (old) path.
The CRM installation is on one server and about 15 users.