Plamen

This problem is usually caused by a mismatched versions of Test Studio/Run-Time and Scheduling/Execution server. Please make sure the Run-Time version installed on your execution machine is the same as the Test Studio version on your local machine.

For example, if you have Test Studio version 2012.1.411 installed on your local machine, you must have the exact same version 2012.1.411 of Test Studio Run-Time on the remote execution machine.

Hi Plamen -
I upgraded both my main ts installation as well as the remote execution box yesterday and am receiving that error. See attached version numbers. Here is some detail about what I have done with the remote execution instillation.

1. I first did a straight upgrade with the installer. That failed to work.
2. I uninstalled the software and then reinstalled it.

Plamen

Are you able to execute the same test list locally? If you create a brand new project are you able to execute it on the remote machine? Can you send us the problematic test project for diagnosis? Just place the root project folder into a .zip file and attach it to the ticket. We don't need to be able to run the tests. We only want to look at the files and try to determine why it's not compiling.

Plamen

Thank you for the provided test files. Unfortunately, I wasn't able to reproduce the problem you are experiencing. If I understand correctly, you are not able to execute any tests on your execution machine, and this leads me to believe that the problem is probably related to a corrupted installation. This could happen if the Scheduling service is running during an upgrade or uninstall.

I apologize for the delay in my response. The copying process should be relatively quick and painless; just follow these steps:

Check out the project from source control.

Move the applicable project files from the old disk location to the new project location. This includes the test files (.tstest, .resx, .cs) and folders, but NOT the project-specific files (like Pages.g.cs & Settings.aiis).

Delete the old project location on disk.

Cut the new project folder and paste it to the old location. It should now reside in the exact path as the old project.

Source control now sees the "new" project in the old location, and simply regards it as updated and needing to be checked in.

I agree it's ideal to repair the existing project instead, however since we don't know what's exactly wrong with it, we don't know what to repair. The process above is the quickest work-around we came up with to get your remote execution working again.

John -
I switch back an forth between Test Studio and the VS Plugin. I think what was ultimately causing this issue was having both set up to connect to TFS. What I found was that when I redid the biding to TFS via Test Studio when I all ready had a binding in place for the project in VS I started getting this issue. I was able to find a simpler work around by simply deleting the .aiis file in the solution root and having TS recreate it when I opened the project location. That ended up working just as well as the steps I got from the Telerik folks. I have been able to keep the issue from recurring by simply not re adding the binding back via TS. I manage the project in TFS through VS and the VS power tools which allows me to manage it via the file system.

John

Daniel,
Thanks for the info. Just to verify the process that you use (I'm still having trouble...):

When I check out the project via VS then open it in TS, I get several prompts warning me that the files are write-only. Do you click through them all and continue working? Or do you connect TS to the already-checked-out-via-VS project using Connect/Open? If I click through all the warnings, VS throws errors when I check the project back in...

I have seen that as well. What I try to do now is keep files (settings etc) checked out in TFS through VS then I don't get those warnings. Checking them out will remove the read only flag. I don't do any work on the tests themselves in Test Stuidio but just use it to schedule tests and manage results.

Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.