BizTalk Server Orchestration - Deployment Bug (2004) - Adding Orchestration to Project

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > October 2004 > Deployment Bug (2004) - Adding Orchestration to Project





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Deployment Bug (2004) - Adding Orchestration to Project
PaulR

2004-10-06, 5:49 pm

Whenever I add a new orchestration to a deployed project, it ends up giving
me the following error in the application log (attached below, HAT gives
nothing). If I undeploy and delete all the ports, it usually fixes it, but
sometimes I have to do it a few times. Is there a reliable way to fix this?
Also, deployment in general is very buggy and kind of seems like its half
finished. Are there plans to improve the deployment from within Visual
Studio?


Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10001
Date: 10/6/2004
Time: 12:53:54 PM
User: N/A
Computer: PRITTER
Description:
Failed while creating a WebMDBizTalkInterfaces.WMD_LoadGroups service.


Exception type: ServiceCreationException
Source:
Target Site:
Help Link:
Additional error information:

Could not load type WebMDBizTalkInterfaces.WMD_LoadGroups from assembly
WebMDBizTalkInterfaces, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=991313e21f1fe479.

Exception type: TypeLoadException
Source: mscorlib
Target Site: System.Type GetType(System.String, Boolean)
Help Link:
Additional error information:



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

phil

2004-10-25, 5:48 pm

I had this same error on an orchestration I added to a project. So, I can
tell you how I resolved it.

1. In HAT - Queries menu - Suspended Orchestrations
right click on each orchestration to Terminate service
2. Back in VS - Unenlisted Orchestrations
3. Set pipeline to something other than the one in my project on my receive
locations.
4. Selected my project from Assemblies and Undeployed
5. Selected Solution and did a Build then Deploy
6. Refreshed BizTalk Configuration Databases in BT Explorer
7. Reselected my pipeline in my project for both receive locations
8. Bind - Enlist - Started my Orchestrations
9. Tested my two interfaces successfully - each document w/ multiple records.

I've only been working with BizTalk 2004 for a week and had help building
the first interface. I'm also new to VS.NET and the deployment parts of this
was a pain all day.

Phil


"PaulR" wrote:

> Whenever I add a new orchestration to a deployed project, it ends up giving
> me the following error in the application log (attached below, HAT gives
> nothing). If I undeploy and delete all the ports, it usually fixes it, but
> sometimes I have to do it a few times. Is there a reliable way to fix this?
> Also, deployment in general is very buggy and kind of seems like its half
> finished. Are there plans to improve the deployment from within Visual
> Studio?
>
>
> Event Type: Error
> Event Source: XLANG/s
> Event Category: None
> Event ID: 10001
> Date: 10/6/2004
> Time: 12:53:54 PM
> User: N/A
> Computer: PRITTER
> Description:
> Failed while creating a WebMDBizTalkInterfaces.WMD_LoadGroups service.
>
>
> Exception type: ServiceCreationException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
> Could not load type WebMDBizTalkInterfaces.WMD_LoadGroups from assembly
> WebMDBizTalkInterfaces, Version=1.0.0.0, Culture=neutral,
> PublicKeyToken=991313e21f1fe479.
>
> Exception type: TypeLoadException
> Source: mscorlib
> Target Site: System.Type GetType(System.String, Boolean)
> Help Link:
> Additional error information:
>
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com