If I use the BizTalk deployment wizard to remove an assembly from the
database, I get a message that the file cannot be removed because it is used
by another process. However, I have shut down the orchestration, un-enlisted
it and also stopped at send ports etc. Sometimes the deployment wizard
allows me to delete the assembly.

How do I determine the locking process? If I use the "Task Manager" I do not
see any process that is of help in determining the issue.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp

[ Post a follow-up to this message ]

Hi,

This statement "Sometimes the deployment wizard allows me to delete the
assembly" makes me think that there is some human error while removing
assembly. There is a tool (Sorry, I forgot what it is) which lists all the
dependencies for an orchestration. Use it to make sure nothing has been left
out.

You can kill BTSNTSvc.exe and then try undeploying the assembly. But this is
not the proper way to do that.

Thanks



"SriSamp" <ssampath@sct.co.in> wrote in message
news:%23DXhmuRCFHA.2984@TK2MSFTNGP11.phx.gbl...
> If I use the BizTalk deployment wizard to remove an assembly from the
> database, I get a message that the file cannot be removed because it is
used
> by another process. However, I have shut down the orchestration,
un-enlisted
> it and also stopped at send ports etc. Sometimes the deployment wizard
> allows me to delete the assembly.
>
> How do I determine the locking process? If I use the "Task Manager" I do
not
> see any process that is of help in determining the issue.
> --
> HTH,
> SriSamp
> Please reply to the whole group only!
> http://www32.brinkster.com/srisamp
>
>

[ Post a follow-up to this message ]

Hi,

You may be receiving this message if you have more than one
assembly depolyed as part of you BizTalk application. For example if
you have one assembly for Orchastations and another for your Message
Schemas you need to undeploy the Orchastrations assembly first as it
will reference the message types in the Message Schemas assembly.

HTH,
Finbar
http://www.irishdev.com/blogs/fmcgurren

Sasidhar Parvatham wrote:
> Hi,
>
> This statement "Sometimes the deployment wizard allows me to delete
the
> assembly" makes me think that there is some human error while
removing
> assembly. There is a tool (Sorry, I forgot what it is) which lists
all the
> dependencies for an orchestration. Use it to make sure nothing has
been left
> out.
>
> You can kill BTSNTSvc.exe and then try undeploying the assembly. But
this is[vbcol=seagreen]
> not the proper way to do that.
>
> Thanks
>
>
>
> "SriSamp" <ssampath@sct.co.in> wrote in message
> news:%23DXhmuRCFHA.2984@TK2MSFTNGP11.phx.gbl... 
the[vbcol=seagreen] 
it is[vbcol=seagreen]
> used 
> un-enlisted 
wizard[vbcol=seagreen] 
I do[vbcol=seagreen]
> not 

[ Post a follow-up to this message ]

Thanks for both the replies.

There is only a single assembly, since all message schemas etc are present
in one DLL.
I check in HAT to see if any instances etc are running and none are (which
is why I'm wondering as to what is that process). I will try searching for
the tool, but in case you do remember, do let me know.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp

"Sasidhar Parvatham" <sasidhar.parvatham@gmail.com> wrote in message
news:%23JHlllUCFHA.3928@TK2MSFTNGP15.phx.gbl...
> Hi,
>
> This statement "Sometimes the deployment wizard allows me to delete the
> assembly" makes me think that there is some human error while removing
> assembly. There is a tool (Sorry, I forgot what it is) which lists all the
> dependencies for an orchestration. Use it to make sure nothing has been
left
> out.
>
> You can kill BTSNTSvc.exe and then try undeploying the assembly. But this
is
> not the proper way to do that.
>
> Thanks
>
>
>
> "SriSamp" <ssampath@sct.co.in> wrote in message
> news:%23DXhmuRCFHA.2984@TK2MSFTNGP11.phx.gbl... 
> used 
> un-enlisted 
> not 
>
>

[ Post a follow-up to this message ]