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=126.96.36.199, Culture=neutral, PublicKeyToken=776eb620b83c3d30’. Could not enlist orchestration ‘MyAssembley, Version=188.8.131.52, 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.
This maybe happens because the DLL’s presents in the GAC are not correct, or they are missing.
Remove all the DLL’s and then deploy afterward or update them in GAC, normally solves this problem.
Remove all the DLL’s and then change the DLL version (for example 184.108.40.206) 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!!
Restart your machine!
5 thoughts on “BizTalk Deploy Error: Could not enlist orchestration ‘MyAssembley’. Object reference not set to an instance of an object. (Microsoft.BizTalk.SnapIn.Framework)””
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