Load Test on remote virtual doesn't return detailed data

[Kathleen]

I am doing load testing and just recently tired switching running the test from my local machine to running it from a virtual machine. Everything seems to run OK on the virtual machine, yet when I attempt to open the results of the Load Test, all I can see is the general results of the Goals set for the test on the Goals tab. There is no information on the dashboard tab and if I try to look at the Page Specific Metrics tab,Telerik hangs and the information on the page never loads. I am Using Test Studio Version 2013.2.1210.0. Is there a step that I missing in order to be able to view data from the test performed from a Virtual Machine?

Thanks,

Kathleen 

[Cody]

Hello Kathleen,

I am sorry you are having this problem. We need to create a log on the remote machine and look for any errors reported in the log. Then we'll have an idea what's going wrong.

Regards,
Cody
Telerik

 

[Kathleen]

Cody,

I have set up logging on our remote scheduler. I am attaching the log file produced for a single day running four different Load Tests.

Thanks,

Kathleen

[Kathleen]

I am trying to attach a zip file, but it is not showing up.

Kathleen

[Cody]

Hello Kathleen,

Thank you for the log. Everything appears normal from 06/04 09:52:44 all the way to the end of the log at 06/04 13:39:01. It only shows actions of the Execution server though. There's nothing in this log from the storage service which is where Test Studio fetches the log from. I think I'd like to look at this problem on your machine via GoToMeeting. Let me know your timezone and your availability and I'll setup the meeting.

Regards,
Cody
Telerik

 

[Kathleen]

I have the log from the Storage Service attached to this message

Thanks,

[Cody]

Hi Kathleen,

Here's our problem:

System.Data.SqlClient.SqlException: Could not allocate space for object 'dbo.DataPoints'.'IX_Datapoints_EntityId' in database 'TestStudioStorage062014' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

One of two things has happened:
1) You've literally run out of disk space where SQL Server has put the DB files
2) You've reached the 4GB size limit that SQL Express puts on databases

Are you using full SQL (which doesn't have the 4GB size limitation) or have you run out of disk space?

Regards,
Cody
Telerik