BizTalk Deploy Error: Could not enlist orchestration ‘MyAssembley’. Object reference not set to an instance of an object. (Microsoft.BizTalk.SnapIn.Framework)"

Posted: May 11, 2011 in BizTalk
Tags: , ,

Today after I deploy and configure a new version of an existence solution, I tried to start the application and it gave me the following error:

TITLE: BizTalk Server 2006 Administration Console
——————————
Could not enlist orchestration ‘MyAssembley, Version=1.0.0.0, Culture=neutral, PublicKeyToken=776eb620b83c3d30’. Could not enlist orchestration ‘MyAssembley, Version=1.0.0.0, Culture=neutral, PublicKeyToken=776eb620b83c3d30’. Object reference not set to an instance of an object. (Microsoft.BizTalk.SnapIn.Framework)

This error, “Object reference not set to an instance of an object“, occurs when I went to enlist the new orchestration.

CAUSE

This maybe happens because the DLL’s presents in the GAC are not correct, or they are missing.

SOLUTION
Remove all the DLL’s and then deploy afterward or update them in GAC, normally solves this problem.

SOLUTION 2

Remove all the DLL’s and then change the DLL version (for example 1.0.0.1) and deploy the solution also, normally, solves this problem

But because today I was a little lazy and my lab machine had several windows updates to do, I decided to make a restart to my environment and install all updates and then deal with this error🙂.

Then came the best part, I decided to make one more shot, without changing anything, just application start J and IT WORKS!!

SOLUTION 3

Restart your machine!

Tags: BizTalk | Deploy | Errors and Warnings, Causes and Solutions

Comments
  1. Anonymous says:

    Had the same problem but solved it when i restarted Visual Studio

  2. Anonymous says:

    Yes today I too encountered this error but I followed your third option to quickly solve the problem !!! Some issues in biztalk make us go crazy but restarting the visual studio or machine will solve some of them. I guess today I deployed and undeployed assemblies several times because of which I could see some strange issues never encountered before.

  3. Venu Gopal Sarla says:

    Yes I followed ur third solution !! I deployed and undeployed biztalk assemblies several times because of which I could see some strange errors never seen before with admin console. Some times Biztalk even drives me crazy with these unknown but simple errors.

  4. Emzil says:

    Reboot is an answer. Yoy saved my day. Thx a lot.

  5. Anonymous says:

    Most probebly your are missing binding file

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s