Today, after I deploy and configure a new version of an existing 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“, occurred when I went to enlist the new orchestration.
📝 One-Minute Brief
Encountering an “Object reference not set to an instance of an object” error when enlisting an orchestration in the BizTalk Administration Console can be a cryptic and frustrating experience. Often caused by mismatched or missing assemblies in the GAC, this error usually suggests that the console framework cannot properly resolve the artifact metadata. While manually cleaning the GAC or incrementing assembly versions are standard fixes, sometimes a simple environment restart is all that’s needed to clear the cached framework state.
Cause
This may happen because the DLLs present in the GAC are not correct, or they are missing.
Solution
Removing all the DLLs and then deploying afterward or updating them in the GAC normally solves this problem.
Solution 2
Remove all the DLLs and then change the DLL version (for example, 1.0.0.1), and deploy the solution, which 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 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 starting the application, and IT WORKED!!
Solution 3
Restart your machine!
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
Had the same problem but solved it when i restarted Visual Studio
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.
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.
Reboot is an answer. Yoy saved my day. Thx a lot.
Most probebly your are missing binding file