I am having issues getting my orchestration to unelist in order to redeploy
it. When I choose unenlist I am getting an error stating that the host did
not respond in a timely manner. I've tried rebooting both my BizTalk and SQL
servers and have also run the messagebox cleanup utility but still no luck.
Has anyone had this issue or know of any other ideas on what to do to
troubleshoot a little more? Thanks.

[ Post a follow-up to this message ]

Hello Nicholas,

Yes, I ran into it yesterday and had to put the VPC out of its missery (Brok
en).
No errormessages or nothing besides the "timeout"...

I created the script below to manually delete references in the managment
box to the assembly, then i manually deleted the assembly from the gac.

After that i was able to deploy again. But I wasn't able to bind the last
port anyway(which was my initial problem)

!!!!! WARNING, Don't do this if it is not your "last resort"  and you are
ready to throw everything away !!!!!


-- Find the assembly id in bts_assembly
use BizTalkMgmtDb
Declare @AssemblyID int
Set @AssemblyID = 289

Delete from bt_DocumentSpec where assemblyid = @AssemblyID
Delete from bt_MapSpec where assemblyid = @AssemblyID
Delete from bts_Item where AssemblyId = @AssemblyID
Delete from bts_assembly where nID = @AssemblyID
Delete from bts_messagetype where nAssemblyID = @AssemblyID
Delete from bts_orchestration where nAssemblyID = @AssemblyID
Delete from bts_porttype where nAssemblyID = @AssemblyID




> I am having issues getting my orchestration to unelist in order to
> redeploy it. When I choose unenlist I am getting an error stating that
> the host did not respond in a timely manner. I've tried rebooting both
> my BizTalk and SQL servers and have also run the messagebox cleanup
> utility but still no luck. Has anyone had this issue or know of any
> other ideas on what to do to troubleshoot a little more? Thanks.
>

[ Post a follow-up to this message ]

By throw away do you mean simply having to redeploy the solution or that the
solution is totally gone?

Nicholas

"Michael Høtoft" wrote:

> Hello Nicholas,
>
> Yes, I ran into it yesterday and had to put the VPC out of its missery (Br
oken).
> No errormessages or nothing besides the "timeout"...
>
> I created the script below to manually delete references in the managment
> box to the assembly, then i manually deleted the assembly from the gac.
>
> After that i was able to deploy again. But I wasn't able to bind the last
> port anyway(which was my initial problem)
>
> !!!!! WARNING, Don't do this if it is not your "last resort"  and you are
> ready to throw everything away !!!!!
>
>
> -- Find the assembly id in bts_assembly
> use BizTalkMgmtDb
> Declare @AssemblyID int
> Set @AssemblyID = 289
>
> Delete from bt_DocumentSpec where assemblyid = @AssemblyID
> Delete from bt_MapSpec where assemblyid = @AssemblyID
> Delete from bts_Item where AssemblyId = @AssemblyID
> Delete from bts_assembly where nID = @AssemblyID
> Delete from bts_messagetype where nAssemblyID = @AssemblyID
> Delete from bts_orchestration where nAssemblyID = @AssemblyID
> Delete from bts_porttype where nAssemblyID = @AssemblyID
>
>
>
> 
>
>
>

[ Post a follow-up to this message ]

Hello Nicholas,

By throw away, i mean your development platform. The hours invested creating
your virtual pc etc. Your application is fine, the Biztalk Explorer just
"hangs" without any error. Effectively shutting down you develop, deploy,
test cyclus. Hopefully you'll have an backup.

The "solution" I provided is quick and dirty And I can not assure it wont
mess something else up in Biztalk. I my scenario it worked.

Regards
Micahael

[vbcol=seagreen]
> By throw away do you mean simply having to redeploy the solution or
> that the solution is totally gone?
>
> Nicholas
>
> "Michael Høtoft" wrote:
> 

[ Post a follow-up to this message ]