Hello, I can't start a Biztalk application. After starting a messagebox with error occurs:

Could not enlist orchestration 'XXXX'. Could not enlist orchestration 'XXXX'. Object reference not set to an instance of an object. (Microsoft.BizTalk.SnapIn.Framework)

After that I go to the Application Windows log and see 3 Errors.

First and second one:

Unable to communicate with MessageBox BizTalkMsgBoxDb on SQL Instance BIZTALK1. Error Code: 0x8004d00e. Possible reasons include:
 1) The MessageBox is unavailable.
 2) The network link from this machine to the MessageBox is down.
 3) The DTC Configuration on either this local machine or the machine hosting this MessageBox is incorrect.

Third:

xlang/s engine event log entry: NullReferenceException exception occurred while the XLANG/s runtime enlisted a service.
Error message:Object reference not set to an instance of an object.
Call stack:   at Microsoft.BizTalk.XLANGs.BTXEngine.OrchestrationMetadata..ctor(String assemblyName, String orchTypeName, Delegate satAssemblyCacheCallback)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXServiceStaticState.PersistState(String mgmtDBServer, String mgmtDBName, String MsgBoxGroupName, String ApplicationName, String serviceAssembly, String serviceTypeName, Guid[] PortIDs, Guid[] LrpIDs, Delegate satAssemblyCacheCallback, ITransaction transaction)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXService.GoLive(String configDBServer, String configDBName, String msgBoxGroupName, String applicationName, String servicePath, String serviceTypeName, Guid[] portIDs, Guid[] lrpIDs, Delegate satAssemblyCacheCallback, ITransaction transaction)
       
       
Exception type: BTXEnlistmentException
Additional error information:

        Object reference not set to an instance of an object.
       
Exception type: NullReferenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void .ctor(System.String, System.String, System.Delegate)
The following is a stack trace that identifies the location where the exception occured

   at Microsoft.BizTalk.XLANGs.BTXEngine.OrchestrationMetadata..ctor(String assemblyName, String orchTypeName, Delegate satAssemblyCacheCallback)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXServiceStaticState.PersistState(String mgmtDBServer, String mgmtDBName, String MsgBoxGroupName, String ApplicationName, String serviceAssembly, String serviceTypeName, Guid[] PortIDs, Guid[] LrpIDs, Delegate satAssemblyCacheCallback, ITransaction transaction)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXService.GoLive(String configDBServer, String configDBName, String msgBoxGroupName, String applicationName, String servicePath, String serviceTypeName, Guid[] portIDs, Guid[] lrpIDs, Delegate satAssemblyCacheCallback, ITransaction transaction)

==================

I've rebuilt and redeployed solution a lot of times. Restarted host instances, but it fails again and again. What is the most interesting that another applications start and finish successfully. But not this one.

The orchestration that can't be enlisted has 2 ports: the first one requests MS CRM via it's adapter (send-receive port), the second  one is a receive-send port which is published as webservice (I want webservise to return results back to user after biztalk finish data manipulations).

I even republished an orchestraion as webservice and used autogenerated receive location in Receive Port, but it didn't helped... The same error once again.

Please, advise me, where I'm wrong? Thanx in advance.

 

• Edited by KirillMedvedev Thursday, June 17, 2010 10:01 AM

Hi,

This is bad. I have encountered this once or twice before. Seems like this problem pops up in different scenarios with different circumstances.

I'm not sure what I did to solve this but I think I manually recreated the ports and the bindings. So If you want to try:

1) remove everything

2) Deploy the orchestration, schemas, etc.

3) Manually create the ports

4) Configure the BizTalk application.

Thank you.
Following your advise, I performed these actions (step-by-step):

1) Recreated send-receive public port in orchestration (that is published with orchestration)
2) Recreated messages and reassigned them to the port
3) Removed orchestrations, ports etc from the application in Administration Console
4) Removed the assemblies from GAC (gacutil.exe /u ApplicationName)
5) Removed application from Applications group
6) Removed a webservise from Default site in IIS Manager
7) Rebuild an application in Visual Studio, deployed it
8) Restarted a host instance in Administration Console, cleared Application Windows Log
9) Launched a  Biztalk Webserver Publishing Wizard, recreated webservice (with anonymus access, and created BizTalk receive locations for this application from Publishing Wizard)
10) Configured CRM port form Administratino Console
11) Restarted a host instance once again
12) Started an application, and... the same errors :(

Hi,

I agree with Randal that it does look bad although I have not encountered this problem before. You might have to check you DTC configuration using DTCPing or DTCTest (based upon your first two errors) and try to perform steps again and/or Randal's steps.

HTH

Regards,

Steef-Jan Wiggers
MCTS BizTalk Server
http://soa-thoughts.blogspot.com/
If this answers your question please mark it accordingly

Thank you.

DTCPING wrote me:

RPC server is ready
Does not make sense to test RPC on the same machine

I've also restarted a "Distributed Transaction Coordinator" service, it didn't help.

I made a lot of attempts to rebuild-redeploy-reconfigure-start, but this error occures every time. Maybe a problem is in receive-send port? Here is my orchestration

Or, maybee, this problem is caused by beta version of Biztalk Server 2010? Any suggessions?

Hi,

Are you doing a call orchestration in one of the orchestrations? Also is the problem limited to one of the orchestrations in the Biztalk application. You can try this by not starting the BizTalk application as a whole but enlisting and starting the individual artefacts like ports and orchestrations.

 

 

 

Hi,

Are you doing a call orchestration in one of the orchestrations?

No, I have the only one orchestration in the application. I'm going to recreate the whole application from scratch now. Maybee that will resolve this issue...

Huraah!! The problem is resolved! I've removed previous project from Administration console, cleaned GAC, created a new BiztalkApplication from scratch, moved xsd schemas and maps from old project, rebuilt, deployed, published orchestration, and... Started! And right now it don't cause any issue, like in previous case!

Thanx!

• Marked as answer by KirillMedvedev Thursday, June 17, 2010 12:22 PM

Also first you must install MSI before importing it to BizTalk, it may be helpful to solve this issue.

Thanks,

RusHay T