TestStand Test Environment adapter dll error and Type Palette error

[aaronb]

I am new to TestStand and I am having a problem opening a TestStand 3.1 standalone UI application. The UI was built a couple of years ago and others use it within my company without problem. I however get the 3 .DLL adapter errors and the Type Palette errors shown below when I try to open it and I can't figure it out. I have tried everything from uninstalling and reloading TestStand 3.1 and uninstalling the UI application and reloading and it did not fix the problem. I verified that the errored .DLL's are present in the Bin directory and the Type Palette files are present in the Type Palette directory. I asked other more experienced TestStand developers within my company if they have ever seen this or knew what was wrong and they can't explain the errors either. Any suggestions?  

[dug9000]

Have you tried deleting the TestStand directory after you uninstall in order to get rid of any files left over (some config files and any custom files are left around after uninstalling)? Have you tried on another machine?

-Doug

[aaronb]

I have tried to delete the TestStand directory, the GUI application directory and also wiped out disconnected registry entries (via CCleaner) after uninstalling and none of this seemed to help. Several other people at my company are using TestStand 3.1 along with this GUI application with no problems on their machines. They have installed it several different times on several different machines and have never seen these errors. The custom TestStand GUI application has been used for about 4 years at my company with no problems.

[ColeTrain]

Hello aaronb,

Can you offer us a little more insight regarding this application or distribution?  Do you have anything else accessing the TestStand engine on your machine?  Is there anything different from your computer than theirs? OS, other installed software, anything of this sort that can offer us some guidance?

It sounds like the ActiveX library might not be registered properly or something is blocking access, but this is really just my wild speculation.  

[dug9000]

Have you tried running the TestStand Version switcher and re-registering TestStand? Do you get any errors when you do so?

-Doug

[aaronb]

Doug - I did try to run the version switcher and it completed sucessfully with no errors but when I try to launch the GUI application I still get the .dll errors. I only have TestStand v3.1 installed.

[aaronb]

Cole - There are probably many differences between my machine and that of my counterparts but they have told me that the only thing I should need to run this standalone TestStand GUI application is TestStand 3.1 and Microsoft .NET Framework which I do have. 

The standalone GUI application is a common front end application that we use for a large part of our production testing at my company. It allows us to have a GUI based front end to our TestStand sequences for running testing in a production environment so the operators can see the test running step by step on the screen. We have the GUI application installed on multiple different Production machines (probably over 10) and all are different machines with different software installed on each. the only real common aspect between them that we ensure is that they all have TestStand 3.1, the GUI application, and .NET Framework installed.  

[aaronb]

Cole - in addition to my last post all machines with this currently in use (including mine) are running WinXP SPv2. I do have LabView 2009 and also LabView 7.1.1 installed on my machine which a few of the other machines running this application do as well. I have all current updates installed from the Microsoft update site.

[aaronb]

I did some more searching around in the Forums and it seems someone had this same problem on an old post back in 2006. Neither of the individuals in the post seem like they have logged into the Forums since 2006 though so they probably wont be much help....

 http://forums.ni.com/ni/board/message?board.id=330&requireLogin=False&thread.id=9477

[dug9000]

Does the sequence editor work ok on that machine?

Also, If possible, please use microsoft's dependency walker on those dlls and let us know if it says that some dependencies cannot be resolved and if so which ones.

http://msdn.microsoft.com/en-us/library/ms235265.aspx

Thanks,

-Doug

Message Edited by dug9000 on 04-27-2010 11:35 AM