BizTalk Server 2006 R2 does not use recently processed "GAC" dll
I have a DLL that is GAC
' ced ( c:\windows\assembly
) which is used by my application Biztalk
, for some requirement I changed the function in this DLL and:
- I removed the old DLL that was in
GAC
(version 1.0.0.0) - I
GAC
'linked the newly built DLL inGAC
(version 1.0.0.0) - I also restarted the host instances
Biztalk
.
But still the output seems to come from an old DLL function. I don't get any problem, why am I still getting the old output.
Can anyone help me?
source to share
Some tips that might be helpful:
(1) If you have multiple BizTalk servers in your group, be sure to upgrade all servers! Depending on the configuration of your instance of your instance, your instance can run on any server that has an active host instance.
(2) Make sure you restart the correct biztalk host instance. This is often overlooked. Don't forget about BizTalk Sandboxed Host! Reprocess the specific IIS application pool as needed. If you are unsure run iisreset.exe
(3) To update a DLL in BizTalk, it is often necessary to update it in the BizTalk database as well. For some changes, it can just update the DLL in the GAC, but often I find that is not enough (especially with orchestration).
source to share
What you are describing here is correct. You should see the new DLL take over. A couple of things to check:
- Have you refactored the correct host instances?
- Have you reused the host instances across all servers?
- Did you confirm the creation date in the GAC'd DLL to make sure a new one was installed?
Another problem might be based on something you changed in the app. You can only use Gac / Restart under certain circumstances. See When You Can Just Restart and Restart on Jon Flander's blog for reference.
source to share
If you really want to verify that the correct assembly was GAC: ed, click Run and type "% systemroot% \ assembly \ gac" for .Net 1.1 or "% systemroot% \ assembly \ gac_msil" for> 2.0.
There you have physical files for each version number that you need to check (or overwrite).
This can help us support you if you let us know which part of BizTalk you are using assembly, pipeline, functoid, schema, etc.
source to share
Is this DLL used by the BizTalk process (BTSNTSvc.exe) or a stand-alone node instance?
If this DLL is used in a receive location where the receive handler (host) is isolated, such as a SOAP receive location, you need to restart the application pool from IIS, not the host instance.
source to share