Deployment issue - External assembly referenced by BTS orchestration

Question

Hi, I was trying to implement a POC where my orchestration references an external dll (another project inside my solution). I referenced dll in GAC from command line, I ran the MSI file on the machine, then tried to import the MSI, strated to get the following error

TITLE: Import Error
------------------------------
Failed to import "E:\tutorial\MyProcess\MyMessages\Setup\MyMessages.msi".
Location of the log file is provided in the Results page.

------------------------------
ADDITIONAL INFORMATION:

Change requests failed for some resources. (mscorlib)

For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2009&ProdVer=3.8.368.0&EvtSrc=Microsoft.BizTalk.ApplicationDeployment&EvtID=ChangeRequestsFailed&EvtChain=Microsoft.BizTalk.ApplicationDeployment+%2cEndTypeChangeRequestError%3bMicrosoft.BizTalk.Deployment+%2cAssemblyNotFound

------------------------------
BizTalkAssemblyResourceManager failed to complete end type change request. (Microsoft.BizTalk.ResourceManagers)
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=
Microsoft+BizTalk+Server+2009&ProdVer=3.8.368.0&EvtSrc=
Microsoft.BizTalk.ApplicationDeployment&EvtID=
EndTypeChangeRequestError&EvtChain=Microsoft.BizTalk.Deployment+%2c
AssemblyNotFound

------------------------------
Referenced assembly "MyMessages.BusinessLogic, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d7f63d8d08d8f3a2" could not be located on local machine's filesystem, so it's impossible to determine if its deployment is required prior to deployment of current assembly MyMessages.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d7f63d8d08d8f3a2. If referenced assembly is not BizTalk assembly, register it in GAC or add it as a resource to any application in the group using BizTalk Management Console or btstask.exe specifying type "System.BizTalk:Assembly", then try again. (mscorlib)

For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2009&ProdVer=3.8.368.0&EvtSrc=Microsoft.BizTalk.Deployment&EvtID=AssemblyNotFound


I turned to VS IDE, deployed the assembly, everything went OK, is ther any reason behind not accepting deployment fom MSI import?
2nd question, what is the best practice in this case.

Thanks

Answer 1

If you add the assembly as a dependency from the resource node of the BizTalk application and then export your MSI your MSI would install the dependent assemblies and the import will not fail.

The best practice is to add the dependent assemblies as a resource and export the MSI. Then import the MSI to another server.

---

Abdul Rafay - MVP & MCTS BizTalk Server
blog: http://abdulrafaysbiztalk.wordpress.com/
Please mark this as answer if it helps.

Answer 2

Thanks for your response. Sure, if yu add the assembly as resource deployment will not fail. But in my scenario, I have somebody who handed mean msi and I need it to run it first, then import it. This means that application is not created, importing the msi should create the application. It is here where failure is happening but not when I deployed from VS.I Application is working fine even without adding the assembly as resource in my BTS application.
Somy initial question was why this difference in behavior and app is running without the need to add the dll in resources.

Regards

Answer 3

Might be helpful: 

http://www.biztalkgurus.com/blogs/biztalk/archive/2006/11/28/Using-BtsTask-to-GAC-your-BizTalk-Assemblies-on-MSI-Import.aspx

http://msdn.microsoft.com/en-us/library/aa558703(BTS.20).aspx

---

Thanks. Mo

Answer 4

Ok thanks. I understood and know most of these methods. In both articles, I don't see how to do it when application is not created in BTS. The problem arised when I ran the MSI on BTS machine, then tried to import it without creati ng the application inadvance in BTS admin console. This is my point.

regards

Answer 5

Ok thanks. I understood and know most of these methods. In both articles, I don't see how to do it when application is not created in BTS. The problem arised when I ran the MSI on BTS machine, then tried to import it without creati ng the application inadvance in BTS admin console. This is my point.

regards

Are you absolutely sure it is the right DL you have in the GAC prior to running the MSI file?

---

eliasen, representing himself and not the company he works for.
Three times MVP and three times MCTS in BizTalk.
Blog: http://blog.eliasen.dk