Test scheduling error

This problem seems to have resolved itself now. However, my tests still will not execute. As far as I can tell I have set everything up correctly. Please see attached.
Any help would be great, I am using a trial version on both local and remote if this matters.

Hello Darren,

Please read our KB article on Resolving Common Scheduling Issues.

You mentioned your execution server is a Virtual Machine. Please ensure it is not locked. Any test that requires moving the mouse or sending keystrokes requires an unlocked desktop. Telerik tests are not the only ones affected by this Windows limitation. You will find this is a general problem with any tool that performs UI testing.

Our tests against HTML based web applications frequently can work on a locked machine because most test steps don't use the mouse or keyboard. Instead they are able to inject Click or Select events against the element in question (e.g. a button or drop down select). Unfortunately Silverlight doesn't allow us to inject these events. We have to simulate system wide mouse moves and mouse clicks instead.

Some of our customers report success using a VNC product. With this they remotely connect to the test machine, leave the user logged on but disconnect the VNC connection. This leaves that Windows session open and unlocked, but humans still cannot access it without reconnecting the VNC connection (which usually means re-authenticating).

Greetings,
Anthony
the Telerik team

Thanks I have checked your link and the machine is not locked. I have also attempted to use the execution part on my own machine which is set up as the scheduling server and still the tests do not run, when I view the results I see the test but it doesnt show a path, please see attached. I have tried with Test studio both open and closed on both machines, with and without the project open.
Thank you

Hi Darren,

Can you provide me the exception details by clicking the white page icon in the upper right of your screen shot? Any additional log information you can provide will be helpful.

Regards,
Anthony
the Telerik team

Please find attached details from the log. It shows the results obtained from an attempted run from my scheduling server as the execution server.

Hello Darren,

‘The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.’

This exception message actually refers to the test execution folder of the client machine. This is configured when you register the Execution Server and is referred to as the "work folder" (see attached screenshot). I suspect this path for you is relatively long. Please change it to branch directly off the root of the C drive and try again.

'Could not find a part of the path 'N:\Projects\eSight\Testing Folder\AutomatedTests\TelerikTestStudio'

This message is more puzzling and I will have to run it by a colleague tomorrow. It is possible the uncommon drive letter is the culprit since this message went away when you moved the project to the C drive.

Regards,
Anthony
the Telerik team

I'm experiencing the same message.

My output folder is identical to the one you mentioned Anthony.
What was the resolution on this issue?

My set up is correct as well, I believe, I can run the test list manually and it works perfectly.
When I schedule the test list, the results are emailed to me, but display nothing in the body of the message. When I go the telerik calendar, I see the results as failed 0 out of 0 tests passed.

Hi Mark,

This appears to be a duplicate of your support ticket 452311. We'll concentrate our efforts and address the issue there.

Regards,
Anthony
the Telerik team

Hi Anthony

We seem to be facing the same problem while trying to set up S:\Automation\DBB as the execution server.  Since I am unable to see the resolution for ticket number 452311, I was hoping you could let us know if the issue was resolved.

Thanks,
Tripti

Hello Sujay,

It was resolved via an online meeting, but unfortunately the details were not logged.

What actions are you taking and what specific error messages do you receive? Any additional insight you can provide will be helpful in diagnosing your issue.

If you haven't done so already, please review this article.

Kind regards,
Anthony
the Telerik team