Error 80004005 TestStand Will Not Load

Updated Jan 6, 2021

Reported In


  • TestStand

Issue Details

My TestStand crashed and now when I try to reopen it I get the following error, or I just installed a newer version of TestStand and when I try to open it, I get the same error and it won't open: 
Creating an instance of the COM component with CLSID {B2794EF6-C0B6-11D0-939-0020AF68E893} from the IClassFactory failed due to the following error: 80004005


This error occurs when TestStand cannot load your StationGlobals.ini file. It is most common in these two situations. Both will result in the same error message. 
  • If your TestStand began giving this error after a crash, this error will occur if your StationGlobals.ini file has become corrupted and could not be loaded when TestStand opens. 
To fix this, simply delete or rename the StationGlobals.ini file. This file is located in:
<Program Files>\National Instruments\TestStand x.x\Cfg
The next time you close TestStand, a new default copy of StationGlobals.ini will be created.
If this error still appears when restarting TestStand, verify that there are no TestStand related processes such as TSAutoMgr.exe running in the Details tab of your Windows Task Manager (Windows 10). If these processes are still present then terminate them and try restarting TestStand again.
Note: This will erase the Station Globals that you had set up on your computer and you will have to recreate them. Also, it's always good practice to save a backup of your files before deleting them.
  • If you recently installed a newer version of TestStand and when you open the new version you get this error box then you may have the wrong version of TestStand selected in the TestStand Version Selector.
To fix this, open Start»Program Files»National Instruments»TestStand X.X»TestStand Version Selector. Where TestStand X.X is your newest version of TestStand. When the Version Selector opens, verify that X.X is selected in the Installed TestStand versions list and click on the Make Active button.  Once you have done this, try to launch the TestStand Sequence Editor again.