Closed tfabraham closed 6 years ago
[tfabraham@2/28/2015] That error during deployment probably has nothing to do with application references. You get that when the other assembly -- DataServices.Common.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3b3f9f75a17ec580 -- is not found in the GAC or Mgmt database. Make sure you have that exact version deployed within DataServices.Common -- same public key and version.
[ssashok10@3/2/2015] Hello, We are deploying the common assemblies through BizTalk deployment scripts before we run the other assemblies which are referencing to it. The assembly database "DataServices.Common.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3b3f9f75a17ec580" is deployed into the management database and we have verified it as well. However, when we tried to see this assembly in GAC, its not deployed there. Here is the "ItemGroup" that we used to deployed it,
Now i have two questions,
Thank you in advacne.
[ssashok10@3/2/2015] We have checked the assembly version and its certainly deployed properly into the management database.
DataServices.Common.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3b3f9f75a17ec580
Is there anything that i am missing here? Thanks.
[ssashok10@3/2/2015] By the way, we found that the common orchetration "DataServices.Common.Orchestrations.DataServices" is in "Unenlisted" state. Will this cause the reference issue as its not enlisted sate? How can I start the orchestration after the master binding has been run? I tied with the below and its not working,
[tfabraham@3/2/2015] There are two GAC's -- one for .NET 2.x/3.x (\windows\assembly) and one for .NET 4.x (\windows\Microsoft.net\assembly). Have you checked both? Since you're using v6.0, I'm assuming you are on BizTalk 2013, and all of your assemblies should typically be in the 4.x GAC. Have you changed and rebuilt all projects to target .NET 4.x? The orchestration likely won't enlist if the DLL isn't in the GAC.
[ssashok10@3/2/2015] You are right about the GAC. I was looking at the wrong place. I am sorry about that. We are using BizTalk 2013 R2. I have checked the assembly folder "C:\Windows\Microsoft.NET\assembly\GAC_MSIL" and i see the assembly is there. I have checked all the BizTalk applications and its all pointing to .NET framework 4.5. Can you please let me know why the orchestration is in unenlisted state though the deployment framework deployed the common assembly successfully. Is that means that we can not reference any assembly if its not in enlisted state? Thanks in advance.
[ssashok10@3/2/2015]
By the way, we are using the property
[tfabraham@3/2/2015] When you deploy the application, the BizTalk application is created and the references to other BizTalk applications are added immediately. Did you look in BizTalk Admin at the properties of the app to see the references?
[UnknownUser@3/2/2015]
[ssashok10@3/2/2015] I have attached a sample project to re-produce this issue. I just created a BizTalk application which is pointing to "BizTalk Application 1". I have added the below item group to add a reference to "BizTalk EDI Application". When i deployed the solution, there is no errors and all deployed successfully. However, the reference to the application "BizTalk EDI Application" is not happened on "BizTalk Application 1". I refreshed the BizTalk admin console and verified the referenced applicaton there. Am i doing anything wrong or is it a bug on deployment framework 6.0? Please find the attached sample application that i created for your reference. Thanks.
[ssashok10@3/3/2015] Are you able to test the sample application that I attached in my previous message? Any early help will be appreciated as we are blocked now. Thanks.
[tfabraham@3/3/2015] Using your sample application on BizTalk 2013 R2: I deployed it Refreshed BizTalk Admin Opened the Properties of DEPFrameTestProject Switched to the References tab Found two references listed, one to BizTalk.System and another to BizTalk EDI Application
I am not seeing the issue.
[ssashok10@3/4/2015] We tried the same sample application to one of our test BizTalk machines here and it worked well without any changes too. This made us to un-install and re-install the deployment framework 6 on the machine where we had a problem and it worked well. So, its basically something went wrong during our installaiton of BizTalk deployment framework 6 on one particular machine. We are able to proceed further on our changes now. Thank you so much for all your help to resolve this issue.
[UnknownUser@3/4/2015]
[tfabraham@3/4/2015] Great, thanks for the update.
[UnknownUser@3/4/2015]
Issue closed by tfabraham with comment Reinstalled and works now
Reason closed Not BTDF
Hello, I am using Deployment Framework 6.0. I am using the below XML segment to reference a common application,
However, when i tried to do a local deployment, i am getting the below error,
Assembly "DataServices.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3b3f9f75a17ec580" references the following assemblies that must be deployed before deploying this assembly: Assembly "DataServices.Common.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3b3f9f75a17ec580"
Can anyone tell me why Deployment framework is not finding the referenced assembly though i am referencing it? Thanks in advance.
This work item was migrated from CodePlex
CodePlex work item ID: '10892' Vote count: '1'