ActiveX Automation Server Error -18351

[cdux]

I wrote a program using TestStand Version 4.5.1 and ran into this error code as soon as I initialize it.

Error loading type library/DLL.

Error Code: -18351; An error occurred reading an ActiveX Automation server type libarary Step 'Read Database Otion - Construct' of sequence 'Get Database Options' in 'SequentialModel.seq'

Bottom line, I'm not using or planning to use any form of database with my program. I just want it to run.

There was another document with ID 4IE7CCM6 that addressed this issue. Tried it, didn't help. I also went to the related links referring to the Knowledgebase document with ID 1HBAMMSR, didn't help either.

How do I fix this?

[dug9000]

Is this on an machine with a full install, or did you deploy things to another machine? Are you using a custom executable to run the sequence or are you using the sequence editor. If you are not using the sequence editor does the problem go away if you use the sequence editor?

-Doug

[cdux]

Yes it is on a full install, no deployment. I am using a sequence editor to run some executable via batch files though. It shouldn't affect or request database type of setup on RUN.

[dug9000]

I'm still not sure I understand what you are doing. What exactly do you mean by "using a sequence editor to run some executable via batch files"? Are you using the CallExecutable step type? Are you launching the sequence editor with the batch file, or is the sequence editor launching something else with the batch file? Is it the sequence editor giving you this error or the executable you are launching? Is the executable you are launching using TestStand or the TestStand engine in anyway?

-Doug

[cdux]

The executables aren't the problem. It is the fact that even when I write a simple LabView program in use TestStand's sequence editor, it still have this error display and won't run without this error interferring.

[dug9000]

Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
 

-Doug