Messenger 5 upgrade

  • Thread starter Thread starter bissell
  • Start date Start date
B

bissell

Since upgrading to Messenger 5, when I click on "send contact an email, and
cut and paste a hyperlink into that email, windows installer opens up, then
says please wait while windows configures messenger 5.0, then another box
titled Windows Messenger 5.0 opens with this message "An error occured
during the installation of assembly component
{874793FC-5F43-496A-8FE7-18C4DB9B143D} HRESULT:-2147024864" Then when I
click OK, messenger closes down and disappears from the system tray.
Whats this all about.
 
I did a search and found in a previous post you wanted the error message
from eventvwr.msc
Hope this helps.

Detection of product '{1FOBD960-6525-4FEE-B577-2473F77FF1277}', feature
'MsgrFeat', component '{462CA1AD-90D6-4FC1-A424-F18BF7817AAA}' failed. The
resource'C\Program Files\Messenger\msgsc.dll' does not exist
 
Greetings Bissell,

This is definitely a new one -- you might try completely uninstalling Windows Messenger by
first making sure that Windows Messenger is shut down (right-click its icon in the
notification area/system tray, and choose Exit), then click Start, then Run, and type in the
following:
msiexec /x {4A432C6C-1E20-4266-95D1-5782349C6C62}
then click OK.

Then, assuming you still want Windows Messenger 5, after uninstallation, reinstall Windows
Messenger 5 from:
http://microsoft.com/downloads/details.aspx?FamilyID=77c3799f-6388-4193-8002-be55584c1ac1
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
 
I tried to uninstall but I get the message "This action is only valid for
products that are currently installed"
This is the message I then get in event viewer.

Product: Windows Mesenger 5.0 - Error 1985. An error occured during the
installation of assembly component
{874793FC-5F43-496A-8FE7-18C4DB9B143D}.HRESULT:-2147024864. assembly
interface: AssemblyCache tem, function: Commit, assembly name: Microsoft
Windows.Networking.RtcDll,type="win32", version= "5.2.2.1", publicKeyToken=
"6595b64144cf1df", processorArchitecture+"x86"
 
I have now just installed Adobe Acrobat and when I try to run it windows
installer tries to install Messenger then fails then tries again, and keeps
going over and over the same process.
How can I get rid of messenger 5.0 and reinstall 4.7?

Thanks


This email message has been swept by Norton Anti Virus for the presence of
computer viruses
 
Hello everyone,

Since some people had problems with the Windows Messenger v5.
installation, like I did, I figured that it could be helpfull to shar
my findings.
Settings\Temp\ (FileName changes on a per installation basis.)

Content :

Error 1935.
An error occured during the installation of assembly componen
{874793FC-5F43-496A-8FE7-18C4DB9B143D}. HRESULT: -2147024864. assembl
interface: IAssemblyCacheItem, function: Commit, assembly name
Microsoft.Windows.Networking.RtcDll,type="win32",version="5.2.2.1",publicKeyToken="6595b64144ccf1df",processorArchitecture="x86"
=== Logging stopped: 5/25/2004 5:06:30 ===


- Detection of product '{1F0BD960-6525-4FEE-B577-2473F77F1277}'
feature 'MsgrFeat', component '{462CA1AD-90D6-4FC1-A424-F18BF7817AAA}
failed. The resource 'C:\Program Files\Messenger\msgsc.dll' does no
exist.

- Detection of product '{1F0BD960-6525-4FEE-B577-2473F77F1277}'
feature 'MsgrFeat' failed during request for componen
'{54E79FD0-8DBE-442F-80ED-2DBA57C9BDB0}'


I did a search on my computer and found the msgsc.dll file in the MS
Messenger (v6.2) directory [C:\Program Files\MSN Messenger\msgsc.dll]
so I decided to give it a try.
I copied it in the "C:\Program Files\Messenger", clicked on th
shortcut for Windows Messenger, no more installation being invoked, no
errors !

I know, this might not be the best solution, but it keeps the thing
working, so I'm sort of happy with the outcome.

Also, there are some features in MSN Messenger that need Window
Messenger, so both of them must be on the system, at least in my case.

If anyone comes with the "real" solution, I'd be more than pleased t
read it.

Regards
-
DBoulange
 
Back
Top