COM error with power tools/team members with Messenger and XP

Question

When loading the power tools with Windows messenger under XP get the following error:

 Creating an instance of the COM component with CLSID {B69003B3-C55E-4B48-836C-BC5946FC3B28} from the IClassFactory failed due to the following error: 8007000e.

This is related to windows messager.

For Vista the solution is to run the msnmsgr.exe as admin (select the Compatibility tab. Select 'Run this program as an Administrator".)
(ref: http://social.msdn.microsoft.com/Forums/en-US/tfspowertools/thread/e80f0333-9ef6-48a0-a409-1a693d5afcc6/)

Is there a solution for XP? (SP2, but other had the problems with SP3)
(I am local admin on the box).
I am upgraded to the latest version of messager to no avail.

Thanks

Answer 1

What version of Windows messenger are you using? if you search B69003B3-C55E-4B48-836C-BC5946FC3B28 in your registry, can you find this key? I just fond this CLSID on a machine with Windows messenger 8.5 and 9.0 beta installed. This CLSID is not found in a machine with messenger 8.1.

---

Please mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

Hi,

This is interesting, the behavior has changed.

You are right that registry does not exist (it did as I did search it originally to confirm it was a liver message issue or I pasted in the wrong value, I definitely had this error). I did update to 8.5 (8.5.1302.1018), and I was getting the same error.

Today I get message and it is "Team foundation error - live messager is not running".
The other different is that I am VPNed to the office but I doubt that would make a difference.
 
Maybe a windows update changed the behavior.

Bertrand

Answer 3

Hi Bertrand

I just searched this error message in the internet and find this blog. Please let me know whether it works for you or not.

---

Please mark the replies as answers if they help and unmark them if they provide no help.

Answer 4

Interesting.

I put the registry value to UpAndRunning value to 2 (I do not think I ma using a Beta version of messager) and now I got the same errot back

the Registry is {B69003B3-C55E-4b48-836C-BC5946FC3B28} and in the regisrty I fing it is linked to Messager.UIAutomation

Here is some info in the registry. Should I simply re-install messager (not my prefered course of action)?

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}
Class Name:        <NO CLASS>
Last Write Time:   11/13/2008 - 11:33 AM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:           

Value 1
  Name:            AppID
  Type:            REG_SZ
  Data:            {AB1D8565-40E9-4616-984D-98465687E82C}

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}\InProcServer32
Class Name:        <NO CLASS>
Last Write Time:   8/12/2004 - 12:11 AM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:            C:\Program Files\Messenger\msgsc.dll

Value 1
  Name:            ThreadingModel
  Type:            REG_SZ
  Data:            Apartment

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}\LocalServer32
Class Name:        <NO CLASS>
Last Write Time:   2/9/2006 - 8:43 PM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:            "C:\Program Files\Messenger\msmsgs.exe"

Value 1
  Name:            ThreadingModel
  Type:            REG_SZ
  Data:            Apartment

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}\ProgID
Class Name:        <NO CLASS>
Last Write Time:   8/12/2004 - 12:11 AM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:            Messenger.UIAutomation.1

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}\Programmable
Class Name:        <NO CLASS>
Last Write Time:   8/12/2004 - 12:11 AM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:           

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}\TypeLib
Class Name:        <NO CLASS>
Last Write Time:   2/9/2006 - 8:43 PM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:            {E02AD29E-80F5-46C6-B416-9B3EBDDF057E}

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}\Version
Class Name:        <NO CLASS>
Last Write Time:   8/12/2004 - 12:11 AM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:            1.0

Key Name:          HKEY_CLASSES_ROOT\CLSID\{B69003B3-C55E-4b48-836C-BC5946FC3B28}\VersionIndependentProgID
Class Name:        <NO CLASS>
Last Write Time:   8/12/2004 - 12:11 AM
Value 0
  Name:            <NO NAME>
  Type:            REG_SZ
  Data:            Messenger.UIAutomation

Answer 5

Reinstall will not help you. It did not help me either. I tried from installing MSN Messenger 7.0 to Live Messenger 9 beta 2 and Windows Messenger 5.1. Nothing helped :(

Answer 6

Solution for Windows Server 2003:
Goto C:\Program Files\Windows Live\Messenger, right-click on msnmsgr.exe -> Properties -> Compatibility -> Run this program in Compatibility mode -> Windows XP -> OK
The same for C:\Program Files\Messenger\Msmsgs.exe.
It Helped in my situation.

P.S.: I had Windows Messenger 5.1 installed before...
P.P.S: every team member has to have an live ID account with the same email as in the Acite Directory email of your company.

Answer 7

Hi robogob,

I've already registered a user account in windows live that matches the exchange email account to login to our TFS. It doesn't display the Tem Members Presence. It only states as Presence Unknown. How does Team Explorer -> Team Members connect to the Live site?

the user account is already online and other users from Windows Live can see i'm online.

Answer 8

  Hi,

sorry for my previous post. After restarting VS the problem occured again :(.
After 2 days of trying I found a solution (works for Win Server 2003 and Win XP).
Tested on Windows Server 2003 with WLM 8.5 and Windows XP with WLM 9 beta.

1. Windows Messenger 5.1  (not Live Messenger) has to be installed on the PC:
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8d9eb73-5f8c-4b9a-940f-9157a3b3d774&displaylang=en
2. A Live ID has to be created as in the TFS (AD account). And Microsoft Live Messenger has to be running.
3. Open VS 2008.
4. Error : "Creating an instance of the COM component with CLSID {B69003B3-C55E-4B48-836C-BC5946FC3B28} from IClassFactory failed due to the following error: 8007000e" -> OK
5. Refresh Team Explorer
6. New error: "Exception from HRESULT: 0x80040200" -> OK
7. Refresh Team Explorer
8. VS wants to send an error report to Microsoft -> Don't Send
9. New error: "The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))" -> OK
10. Open new instance of VS 2008
11. Repeat steps 4,5,6 on that new instance of VS 2008.
12. Close that instance of VS 2008 and return to the old one (opened first).
13. Refresh Team Explorer. If error occures refresh it again (1-5 times may be needed).
14. Everything is functioning.

P.S.: this procedure has to be done every time you open VS :(.

Ikhwan, as I understand not only you, but every team member needs to have and LiveID as in AD of your organization (see Team Explorer -> concrete Team Member -> properties window)

Answer 9

Is there any solution for this problem yet?

I have the same message with the october 2008 power tools (Creating an instance of the COM component with CLSID {B69003B3-C55E-4B48-836C-BC5946FC3B28} from the IClassFactory failed due to the following error: 8007000e.)

I just updated to beta of Windows Live Messenger Beta Version 2009 (Build 14.0.5027.908) and still have the same problem.

This is quite annoying.

Thanks

Answer 10

Hi,

I gave up and simply turned it off

Go to Team Explorer, right on team members, Personnal Settings - choose Change button (collaboration section) and select None.

Bertrand

Answer 11

Thanks Bertrand,

I did not realize I could turn the thing off!

I guess we will wait for the next power tools release for a fix.

Answer 12

I'm getting this now and it's May 2009...is there no fix in sight, or a registry hack or anything?

Answer 13

If you are not using live messenger, it better to turn it off in power tools.

Tools--> Options--> Team Foundation Server Power Tools

set
Status Search and wildcard search to false
Team Members to False
and one more about Synchronize contact information to false

this has resolved issue on my machine. I use live messenger but not always and i do not need team members and their status here in TFS.