gacutil -u

  • Thread starter Thread starter alien2_51
  • Start date Start date
A

alien2_51

This component had been installed as a windows service using the Installer
class.. it was later uninstalled succesfully...

Any ideas....?

C:\mncprojects\vsprojects\VS2003\MNCBDOServiceLibrary\bin>gacutil -u
MNCBDOServiceLibrary

Microsoft (R) .NET Global Assembly Cache Utility. Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.


Assembly: MNCBDOServiceLibrary, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=48d69f43b9e7bec3, Custom=null
Unable to uninstall: assembly is required by one or more applications
Pending references:
SCHEME: <WINDOWS_INSTALLER> ID: <MSI> DESCRIPTION : <Windows
Installer>

Number of items uninstalled = 0
Number of failures = 0
 
I found the.....

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion]
"DisableCacheViewer"=dword:00000001

"Hack"

which allowed me to remove the folder that was causing me trouble...
Seems to work but theres got to be something more elegant... Any ideas
MS....?
 
Hi,

That's a really good question. I have the exact same
problem. After I added the DisableCacheViewer setting in
the registry, I was able to delete the assembly. But why
is this happening. This problem may also prevent the MSI
from removing the assembly from the GAC, when it should be
able to.

Any ideas would be appreciated.

Regards,
Sijmen.
-----Original Message-----
I found the.....

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion]
"DisableCacheViewer"=dword:00000001

"Hack"

which allowed me to remove the folder that was causing me trouble...
Seems to work but theres got to be something more elegant... Any ideas
MS....?



This component had been installed as a windows service using the Installer
class.. it was later uninstalled succesfully...

Any ideas....?

C:\mncprojects\vsprojects\VS2003 \MNCBDOServiceLibrary\bin>gacutil -u
MNCBDOServiceLibrary

Microsoft (R) .NET Global Assembly Cache Utility. Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.


Assembly: MNCBDOServiceLibrary, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=48d69f43b9e7bec3, Custom=null
Unable to uninstall: assembly is required by one or more applications
Pending references:
SCHEME: <WINDOWS_INSTALLER> ID: <MSI>
Click to expand...
DESCRIPTION :
<Windows
Installer>

Number of items uninstalled = 0
Number of failures = 0
Click to expand...


.
Click to expand...
 
Hi,

I believe there's an article in MSDN (was it a KB one?) explaining how to
deal with such situations. In a nutshell, the Windows Installer-generated
references are stored in a registry (there are different places for
per-machine and per-user references) and can be removed from there with
RegEdit should "legitimate" uninstall fail for some reason.

I have been in the same situation and only editing the appropriate registry
key enabled me to uninstall the assembly.

P.S. The key you are talking about is not the one I've used.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

alien2_51 said:
I found the.....

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion]
"DisableCacheViewer"=dword:00000001

"Hack"

which allowed me to remove the folder that was causing me trouble...
Seems to work but theres got to be something more elegant... Any ideas
MS....?



alien2_51 said:
This component had been installed as a windows service using the Installer
class.. it was later uninstalled succesfully...

Any ideas....?

C:\mncprojects\vsprojects\VS2003\MNCBDOServiceLibrary\bin>gacutil -u
MNCBDOServiceLibrary

Microsoft (R) .NET Global Assembly Cache Utility. Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.


Assembly: MNCBDOServiceLibrary, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=48d69f43b9e7bec3, Custom=null
Unable to uninstall: assembly is required by one or more applications
Pending references:
SCHEME: <WINDOWS_INSTALLER> ID: <MSI> DESCRIPTION : <Windows
Installer>

Number of items uninstalled = 0
Number of failures = 0
Click to expand...
Click to expand...
 
By any remote chance, did this machine have MSN Messenger 6 installed?

For some reason, Messenger 6 affects the ability to remove assemblies from
the GAC. It's possible to "fix" the problem by removing a particular
registry key, details of which I can dig out of my notes if it'd help.
 
Hi,

Yes, Messenger 6 is installed. I'm absolutely amazed that
messenger can have an impact on something as important as
the GAC.

I would greatly appreciate it, if you would let me know
how to fix the problem.

Regards,
Sijmen.
 
Hi,

I have confirmed that MsnMessenger 6.0 is somehow related
to the problem which prevents assemblies from being
uninstalled from the GAC. When I uninstalled MSN
Messenger 6, I was then able to uninstall the assembly
from the GAC using gacutil.exe.

Could someone please explain why this is the case, and how
I can overcome the problem, without haing to uninstall Msn
Messenger. Is this problem fixed in a later version of
messenger?

Regards,
Sijmen.
 
I have confirmed that MsnMessenger 6.0 is somehow related
to the problem which prevents assemblies from being
uninstalled from the GAC. When I uninstalled MSN
Messenger 6, I was then able to uninstall the assembly
from the GAC using gacutil.exe.
Click to expand...

I'd be happy if someone would simply explain to me how to delete MSN
Messenger. Whenever I try it says it's in use. I can't even stop it.

-- Rick
 
Back
Top