TestStand 4.2.1 fails with "Retrieving the COM class factory for component with CLSID {B2794EF6-C0B6-11D0-939C-0020AF68E8939} failed due to error: 800736B3."

[Bill Hamman]

I have an ATE running TestStand 4.2.1 that has been working well for months.  But recently its Windows XP Professional crashed.  
IT was able to repair the Windows installation, but now every time I try to run the TestStand sequence editor, I get the following
error:  "Retrieving the COM class factory for component with CLSID {B2794EF6-C0B6-11D0-939C-0020AF68E8939} failed due to
error:  800736B3."  

I have reinstalled TestStand 4.2.1, reinstalled VS2008, and performed repairs on all the installed .NET software but
the problem persists.  Note that LabWindows 8.5 seems to work normally - TestStand is the only thing that doesn't work, that I
know of.  

I cannot find any useful documentation on this error.  Does anyone know what this error refers to?  Does it point at a damaged
TestStand installation, a damaged .NET installation, or at some gruesome residual damage to Windows XP left over from the crash?

[dug9000]

Have you tried running the TestStand vesion switcher and re-switching to 4.2.1?

-Doug

[Bill Hamman]

Hi, Doug.

When I try to run the version switcher, it fails with error code C0150004.

Thanks!

Bill

[dug9000]

Haven't ever heard of that happening. Is there any description given along with that error code?

-Doug

[Bill Hamman]

Doug,

The Version Selector error text is "The application failed to initialize properly (0xC0150004).  Click OK to terminate."

Also, when Windows boots, the error "TSVerSelect failed to initialize (C0150004)" briefly appears, though nothing of this sort appears in the Windows event log.

I suspect my Windows installation is damaged beyond repair.

Thanks!

Bill

[dug9000]

The COM error is probably a direct result of the version switcher not being able to run. The version switcher not being able to run sounds like something is in a bad state on your machine. Have you tried repairing TestStand? Another thing you might try is installing the eval version of the latest version of TestStand (you can get it from ni.com) as that will upgrade your version switcher to the latest version which should hopefully fix the problem after you version switch back to 4.2.1. Though, since your machine was known to have problems, there might be other issues that will show up later so you might be better off rebuilding the machine from scratch (i.e. reinstalling the OS and all apps), but it's up to you.

Hope this helps,

-Doug

[Bill Hamman]

Doug,

That's been our analysis too - even if we luck out and fix it, who knows what other sharks lurk beneath the surface of its damaged Windows?  We've decided to abandon trying to fix it and we're rebuilding it entirely.

But thanks for your time!

Bill

[_S_G]

I had this same issue with TestStand 2013 on Windows 7.  I tried running the version switcher to set the version to TestStand 2013 and got the same error message.

I then ran the version switcher to set the version to 2012 and this was successful.  When I then switched back to 2013, this was also successful.

Thanks to the previous posters who pointed me in the right direction.