| Author |
Unable to undeploy an assembly and orchestration
|
|
| fheinema 2005-10-28, 5:03 pm |
| I have an assembly that will not undeploy. It contains one orchestration
which is unenlisted. I keep getting two errors that some items in this
assembly are bing used by items in another assembly. This specific assembly
references one other assembly that contains schemas only. I have checked all
other setups in BizTalk Explorer and do not see any other assembly accessing
this one. I have redeployed the assembly with a different version number and
that has made it worse. Now when I try to deploy the assembly again with the
same version number I get two asseblies with the same version number but the
one that I cannot undeploy has a (1) after it. Is there any way to go into
the database or gac and force this assembly out? I have tried everything I
can think of including undeploying everything (except the schema assembly as
it will no longer let me undeploy that since it is referenced by this
corrupted one) and nothing has worked.
--
Fred Heinemann
| |
| fheinema 2005-10-28, 5:03 pm |
| I just found out that the assembly we are working with now is a complete
rebuild of the original. The original solution file and assembly file for
this project was deleted but the original assembly was not undeployed before
the project was deleted. I was confused because they both were using the
same name. So the question is how can you undeploy an assembly when the
solution, project and .snk file were all deleted?
--
Fred Heinemann
"fheinema" wrote:
> I have an assembly that will not undeploy. It contains one orchestration
> which is unenlisted. I keep getting two errors that some items in this
> assembly are bing used by items in another assembly. This specific assembly
> references one other assembly that contains schemas only. I have checked all
> other setups in BizTalk Explorer and do not see any other assembly accessing
> this one. I have redeployed the assembly with a different version number and
> that has made it worse. Now when I try to deploy the assembly again with the
> same version number I get two asseblies with the same version number but the
> one that I cannot undeploy has a (1) after it. Is there any way to go into
> the database or gac and force this assembly out? I have tried everything I
> can think of including undeploying everything (except the schema assembly as
> it will no longer let me undeploy that since it is referenced by this
> corrupted one) and nothing has worked.
> --
> Fred Heinemann
| |
| Tomas Restrepo \(MVP\) 2005-10-29, 5:50 pm |
|
Fred,
>I just found out that the assembly we are working with now is a complete
> rebuild of the original. The original solution file and assembly file for
> this project was deleted but the original assembly was not undeployed
> before
> the project was deleted. I was confused because they both were using the
> same name. So the question is how can you undeploy an assembly when the
> solution, project and .snk file were all deleted?
The BizTalk Deployment wizard should be able to do that, I think.
At worst, you might need the actual DLL, which you probably should be able
to get from the GAC...
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| fheinema 2005-10-31, 5:55 pm |
| I have tried the deployment wizard and it has also failed out. I am not sure
how to get the dll out of the GAC. Can you tell me where it would be
located? If I do get that won't it still fail because of the dependencies it
is claiming exist?
--
Fred Heinemann
"Tomas Restrepo (MVP)" wrote:
>
> Fred,
>
>
> The BizTalk Deployment wizard should be able to do that, I think.
>
> At worst, you might need the actual DLL, which you probably should be able
> to get from the GAC...
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Tomas Restrepo \(MVP\) 2005-10-31, 5:55 pm |
| >I have tried the deployment wizard and it has also failed out. I am not
>sure
> how to get the dll out of the GAC. Can you tell me where it would be
> located? If I do get that won't it still fail because of the dependencies
> it
> is claiming exist?
You need to run regsvr32.exe /u on shfusion.dll (it's in your framework
setup dir). That way, Explorer will allow you to see the real structure
under %windir%\assembly, and a simple search will do.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| fheinema 2005-10-31, 5:55 pm |
| Thank you for your help so far. I was able to run the regsvr32 utility. It
does make the GAC directory viewable in explorer for about 10 seconds. I am
able to get to the directory using the DOS prompt even if I cannot view it in
explorer. I tried running the deployment wizard to undeploy the assembly and
got the same two errors. I also tried going to the GAC directory that
contains the .dll and attempted to run the gacutil -uf program. It gives me
a message that the .dll does not exist in the global assembly and cannot
remove it. I must be missing a step somewhere. Any ideas?
--
Fred Heinemann
"Tomas Restrepo (MVP)" wrote:
>
> You need to run regsvr32.exe /u on shfusion.dll (it's in your framework
> setup dir). That way, Explorer will allow you to see the real structure
> under %windir%\assembly, and a simple search will do.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Tomas Restrepo \(MVP\) 2005-10-31, 5:55 pm |
| Fred,
> Thank you for your help so far. I was able to run the regsvr32 utility.
> It
> does make the GAC directory viewable in explorer for about 10 seconds. I
> am
> able to get to the directory using the DOS prompt even if I cannot view it
> in
> explorer. I tried running the deployment wizard to undeploy the assembly
> and
> got the same two errors. I also tried going to the GAC directory that
> contains the .dll and attempted to run the gacutil -uf program. It gives
> me
> a message that the .dll does not exist in the global assembly and cannot
> remove it. I must be missing a step somewhere. Any ideas?
Removing it from the gac is no problem (heck, you can do that from
explorer), the problem is really removing it from the BizTalk configuration
database. If worse comes to pass, you might just need to edit the tables in
the BizTalkMgmtDB directly 
What I meant was to unregister the fusion GAC viewer so that you could look
for the physical Assembly DLL and then use the BizTalk deployment wizard to
try to remove it.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| fheinema 2005-10-31, 5:55 pm |
| Thanks for all the help. It turns out there was an easy fix. I used BizTalk
Deployment Wizard like you said, but I did not flag it to remove the assembly
from the GAC. This removed it from the database. I can now manually remove
it from the GAC. This might have been what you meant all along. Thank you
for all your advice.
--
Fred Heinemann
"Tomas Restrepo (MVP)" wrote:
> Fred,
>
>
> Removing it from the gac is no problem (heck, you can do that from
> explorer), the problem is really removing it from the BizTalk configuration
> database. If worse comes to pass, you might just need to edit the tables in
> the BizTalkMgmtDB directly
>
> What I meant was to unregister the fusion GAC viewer so that you could look
> for the physical Assembly DLL and then use the BizTalk deployment wizard to
> try to remove it.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
|
|
|
|