error -17500 when using version selector and toolboxinstaller.exe file not found from the ts3.5 deployment

[Akiel]

Everytime i run the version selector to switch between ts4.2 and 3.5 it displays the above error and also gives advice how to fix it for a version of visual studio i dont have (I am using 2003). As well as this when i launch the deployment engine from TS3.5 i get the error message system.io.filenotfound with toolboxinstaller.exe. I know these are related so have tried to repair/reinstall them to no avail, Any help would be much appreciated    thanks

[Philip.k]

Hey Akiel

I have found a knowledge base that maybe related to your situation could you try this and let me know how you get on.

I shall try and reproduce the error in order to help.

Heres the Knowlagebase

Philip

[Manooch_H]

Hi Akiel,

My assumption is that TestStand 4.2 is currently the active version your machine and you receive this error when attempting to make TestStand 3.5 active. Is this correct? What version of Visual Studio does it give you instructions for? Could you post screenshots of all the errors/popups you receive when attempting to make TestStand 3.5 active?

Could you explain what you mean when you say you try to "launch the deployment engine from TestStand 3.5"? Are you talking about the TestStand Deployment Utility or are you talking about launching a TestStand 3.5 custom user interface? Could you also post a screenshot of this error?

I look forward to getting this information back from you so that we can resolve this problem as quickly as possible.

[Akiel]

It does change version but has the described errors while trying to select version. I have version 3.5 active due to removing 4.2, i have problems each time i open teststand but it does seem to function correctly (so far), by deployment i mean the teststand deployment utility 

The visual studio version is visual studio .net c++ , I have version visual studio c# .net 2003

Thanks for the replies, I tried the attached bat files which also produced the same error messages

[Manooch_H · Accepted solution]

Hi Akiel,

Is the message below similar to the message that you are receiving (note that this message relates to Visual Studio 2005, yours might relate to Visual Studio 2003):

This is a known problem with the TestStand Version Selector and has been reported to R&D (#171620). The TestStand Version Selector assumes that when Visual Studio is installed on the machine, that Visual C++ has also been installed. It attempts to write to Visual C++ specific files which do not exist if Visual C++ is not installed.

This error does not mean that something is necessarily wrong, it is more a message that the files could not be written to successfully. You should be able to continue to launch TestStand successfully without problems.

Regarding the Deployment Utility, I assume that the two issues are related however, it would be much easier to tell for certain that the error you are receiving will not cause problems if you post a screenshot of the error. Please do so.

Thanks!

[Akiel]

thats the message i am getting, thanks for the info I have attached the other messages (always occurs as a 2off) but i also have assumed they are related.    Thanks

[Manooch_H]

Akiel,

I want to be sure that I have a good understanding of the second issue. My assumption is that TestStand 3.5 is the current active version and you are able to open the Sequence Editor to use TestStand successfully. However, when you go to Tools»Deploy TestStand System, you receive the error displayed in the screenshot. Is this correct?

Do you receive both errors simultaneously upon first launch of the TestStand Deployment Utility?

[Akiel]

I get the one on the left then the one on the right, if I ignore them everything works fine, your assumption is correct, ts3.5 is the active version

Thanks

[Manooch_H]

Hi Akiel,

I have reproduced the Just-In-Time Debugging popups that you are receiving. The reason you are receiving these popups now is because TestStand 4.2 was uninstalled from your machine.

I know that you originally uninstalled TestStand 4.2 because you were worried about the 17500 error that you were receiving when making TestStand 3.5 active. Unless you have a particular reason not to, I recommend that you reinstall TestStand 4.2 then make TestStand 3.5 active again. You will still receive the 17500 error, but as discussed in earlier posts, this error is not harmful and can be ignored. Once you do this, you should no longer get the 2 Just-In-Time Debugging popups when you launch the Sequence Editor or the Deployment Utility.

Please let me know if this works out. Thanks!