Home » Visual StudioRSS

VS2010 Ultimate Edition: Failed to serialize WebTestResultDetails error.

Only in VS2010, intermittently I get the following error as the last step when running a long web test:

"Failed to serialize WebTestResultDetails. ... The Web test result details will be lost if the Web test result viewer window is closed."

When I tried to programatically serialize the results file the inner error was: "End of Stream encountered before parsing was completed."

A google search returned 0 results which was surprising (or frightening).

Anyone has encoutered this or knows the reason and how to fix it?

 

10 Answers Found

 

Answer 1

Hello,

Could you please offer the detailed error  message so the community members could help you better and quicker? Have you added custom additional code for the web  test, like plug-in for serialization? If you create a simple web test, does this issue still exist?

You could also try the following steps to see if they help:

a)     Try to run devenv /ResetSettings (in command prompt) to eliminate the related potential settings problem.

b)     Try disabling Add-ins (e.g. “Tools” | “Add-in Manager”) or run “devenv.exe /SafeMode”.This can eliminate the possibility that third party Add-ins or packages are causing problems. (For more detailed VS command line switches information, see: http://msdn2.microsoft.com/en-us/library/xee0c8y7.aspx )

c)     Try creating a new project. Sometimes corrupted project settings can cause problems. These are project specific.

d)     Try to reboot the operating system to safe mode. This can help to isolate whether any other applications are interfering with Visual Studio. Note that some features (like IIS) are not available under safe mode. Please check whether this can be applied or not. In addition to safe mode, we can also try “clean boot”: How to configure Windows XP to start in a "clean boot" state http://support.microsoft.com/kb/310353 .

e)      Try to create a new user account. This can help isolate user profile corruption related causes.


Edwer Fang [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Send us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.
 

Answer 2

Edwer,

Thanks for your prompt reply. To follow up on this, the exact error  I am getting is:

System.Exception: An error occurred writing web  test result  file 'D:\SourceCode\XXX.IIS.XXXXX\Main\XXX.IIS.XXXXX.PerformanceTest\XXX.IIS.XXXXX.PerfTest2010\TestResults\Perftest _2010-07-13 08_30_25_\In\a8c83b9d-47ea-433c-95f0-b648d2f2da4c\R_Scenario_5_1_1.webtestResult': Failed to serialize  WebTestResultDetails.. The Web test  result details  will be lost  if the Web test result viewer  window is closed.

I masked a few parts of the path with X for privacy but kept the number of characters the same.

I tried the /ResetSettings and /SafeMode switches but it did not solve my problem.

To give more details:

1. The solution and the projects were initially upgraded from VS2008 Test Edition.

2. I created a new project and copied over the web scripts but I get the error on both, the converted project and new project.

3. The error is intermittent, meaning the same script sometimes will save the results  file propery and sometimes not.

4. I tried to deserialize the webtestResult file  using the Deserialize method of the WebTestResultDetails class and got the same error as above and the inner error message was "End of Stream encountered before parsing  was completed" which leads me to believe that somehow the webtestResult file is not properly written to disk.

5. There is no plug-in for serialization but there are data binding, extraction and validation rules plug-ins used by the scripts.

I can not do a clean boot or create a new user account in my machine (company/client policy). At the same time recreating the web scripts from scratch in VS 2010 is not an option either.

Thanks,

Ardian Daka

 

Answer 3

Hello,

If you create a new simple web  test in VS2010 and run it, does this issue exist?

As this issue is intermittent, it is not easy to directly point out the cause, however, you can enable logging to see if you can find anything helpful: http://blogs.msdn.com/b/yutong/archive/2006/10/03/how-to-enable-vsts-logging_3f00_.aspx, this blog works on VS2008, for VS2010, you have to modify either QTAgent.exe.config or QTAgent.exe32.config under the same directory.

 

Answer 4

Hi Edwer,

If I create a new simple web  test in VS2010 everything is fine. And in general, simple and relatively short web tests never have an issue, whether created in VS2010 or converted from vs2008. The  error  seems to happen when the webtestResults file  is over 16 MB.

Here's the end  of the log file created with 'verbose' mode (I highlighted the entries with Outcome: Failed):

V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: WebTest: TestCaseCompletedCallback: Enter
V, 5500, 18, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: WebTest: Exit Playback Thread
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: WebTest: TestCaseCompletedCallback: Send WebTestComplete event
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: WebTestAdapter sending status: IterationComplete
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: invoking special job checker for job 'run id {ff32287d-e77e-4055-be82-413940346e3c},  test  'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: InProgress'
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: successfully invoked special job checker for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: InProgress'
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: isSpecial = False
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: Queuing job 'Type Microsoft.VisualStudio.TestTools.WebStress.WebTestResultMessage: run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: InProgress'
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: WebTest: Shutdown test
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: WebTest: Test Definition Terminate completed.
V, 5500, 15, 2010/07/14, 09:12:17.091, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: Number of calls to BindIPEndPointForWebTest: 0
V, 5500, 9, 2010/07/14, 09:12:17.701, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: successfully invoked job processor for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: InProgress'
V, 5500, 9, 2010/07/14, 09:12:17.701, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: invoking job processor for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: InProgress'
V, 5500, 9, 2010/07/14, 09:12:17.701, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: successfully invoked job processor for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: InProgress'
V, 5500, 11, 2010/07/14, 09:12:20.561, MY_PC_NAME\QTAgent32.exe, AgentObject: Sending heartbeat to listeners
V, 5500, 11, 2010/07/14, 09:12:20.561, MY_PC_NAME\QTAgent32.exe, AgentObject: returned  from sending heartbeat
V, 5500, 15, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: WebTest: TestCaseCompletedCallback: Exit
V, 5500, 14, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: invoking special job checker for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: Failed'
V, 5500, 14, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: successfully invoked special job checker for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: Failed'
V, 5500, 14, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: isSpecial = False
V, 5500, 14, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: Queuing job 'Type Microsoft.VisualStudio.TestTools.WebStress.WebTestResult: run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: Failed'
V, 5500, 15, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: invoking job processor for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: Failed'
V, 5500, 14, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentExecution: m_testAdapter.Run finished with test 'R_Scenario_3_1_2' (bf8a017a-19c7-4702-adf5-03daf63ac4f0)
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): Exit wait for state change, current state is Running.
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): calling state handler for Completing
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentExecution.TestStateCompleting: waiting on m_testThreadComplete...
V, 5500, 14, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentExectution.CallAdapterRunMethod: calling m_testThreadComplete.Set.
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): SetNextState completed  called
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): In state Completed. Waiting for state change...
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): Exit wait for state change, current state is Completed.
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): calling state handler for Completed
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: invoking special job checker for job 'Run {ff32287d-e77e-4055-be82-413940346e3c}, Test {bf8a017a-19c7-4702-adf5-03daf63ac4f0}: Completed'
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: successfully invoked special job checker for job 'Run {ff32287d-e77e-4055-be82-413940346e3c}, Test {bf8a017a-19c7-4702-adf5-03daf63ac4f0}: Completed'
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: isSpecial = False
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: Queuing job 'Type Microsoft.VisualStudio.TestTools.Common.TestStateEvent: Run {ff32287d-e77e-4055-be82-413940346e3c}, Test {bf8a017a-19c7-4702-adf5-03daf63ac4f0}: Completed'
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): SetNextState Disposed called
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): In state Disposed. Waiting for state change...
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(TestState): Exit wait for state change, current state is Disposed.
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, Write: Succeeded.  File: 'D:\SourceCode\XXX.IIS.XXXXX\Main\XXX.IIS.XXXXX.PerformanceTest\XXX.IIS.XXXXX.PerfTest2010\TestResults\Perftest _2010-07-14 09_03_36_\Out\AgentRestart.dat' RunId: ff32287d-e77e-4055-be82-413940346e3c  TestCompleted: 1
V, 5500, 13, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentObject.OnExecutionTestCompleted: done for test R_Scenario_3_1_2
V, 5500, 12, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentObject: WaitForTestState: WaitAny returned 0
I, 5500, 12, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentObject: ExecuteTest 'R_Scenario_3_1_2' is complete.
V, 5500, 12, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentObject: TestQueueThread exit
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is Running.
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): calling state handler for Completing
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentObject.AgentStateCompleting: finished waiting for all executions to complete
V, 5500, 15, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: successfully invoked job processor for job 'run id {ff32287d-e77e-4055-be82-413940346e3c}, test 'R_Scenario_3_1_2' with id bf8a017a-19c7-4702-adf5-03daf63ac4f0: MessageKind: Result, Outcome: Failed'
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, Clear: restartdata being deleted.
V, 5500, 15, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: invoking job processor for job 'Run {ff32287d-e77e-4055-be82-413940346e3c}, Test {bf8a017a-19c7-4702-adf5-03daf63ac4f0}: Completed'
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): SetNextState Waiting called
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state Waiting. Waiting for state change...
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is Waiting.
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): calling state handler for Waiting
I, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, AgentObject.AgentStateWaiting: Queuing AgentRunFinishedMessage for test run 'ff32287d-e77e-4055-be82-413940346e3c'
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: invoking special job checker for job 'AgentRunFinishedMessage for test run 'ff32287d-e77e-4055-be82-413940346e3c''
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: successfully invoked special job checker for job 'AgentRunFinishedMessage for test run 'ff32287d-e77e-4055-be82-413940346e3c''
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundSpecialJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: isSpecial = False
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: Queuing job 'Type Microsoft.VisualStudio.TestTools.Execution.AgentRunFinishedMessage: AgentRunFinishedMessage for test run 'ff32287d-e77e-4055-be82-413940346e3c''
V, 5500, 8, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state Waiting. Waiting for state change...
V, 5500, 15, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: successfully invoked job processor for job 'Run {ff32287d-e77e-4055-be82-413940346e3c}, Test {bf8a017a-19c7-4702-adf5-03daf63ac4f0}: Completed'
V, 5500, 15, 2010/07/14, 09:12:27.592, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: invoking job processor for job 'AgentRunFinishedMessage for test run 'ff32287d-e77e-4055-be82-413940346e3c''
V, 5500, 15, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender)+ExternalJob.ProcessJob: successfully invoked job processor for job 'AgentRunFinishedMessage for test run 'ff32287d-e77e-4055-be82-413940346e3c''
V, 5500, 15, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentObject: Cleanup called with timeout of 108000
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is Waiting.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): calling state handler for CleanupDataCollectors
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.SynchronizedEventInfo>(AgentObject.DataCollectionEventReceiver).Flush: Waiting for 0 jobs to be processed
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.SynchronizedEventInfo>(AgentObject.DataCollectionEventReceiver).TryEnqueueJob: Queuing job 'FlushJob'
I, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, ExecutionPluginManager.CleanupPlugins: CleanupPlugins called
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, ExecutionPluginManager.CleanupPlugins: Cleaning up 0 plugins
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob>(FileDataSender.FileTransferJobProcessor).TryEnqueueJob: Queuing job 'Type Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob: Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob'
V, 5500, 9, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob>(FileDataSender.FileTransferJobProcessor)+ExternalJob.ProcessJob: invoking job processor for job 'Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob'
V, 5500, 9, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, FileDataSender: Triggering reset event for waiting job.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob>(FileDataSender.FileTransferJobProcessor).DoAbort: Clearing 0 queued jobs and 0 jobs waiting to be queued
V, 5500, 9, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob>(FileDataSender.FileTransferJobProcessor)+ExternalJob.ProcessJob: successfully invoked job processor for job 'Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob'
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob>(FileDataSender.FileTransferJobProcessor).Dispose
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Execution.Aggregation.FileDataSender+FileTransferJob>(FileDataSender.FileTransferJobProcessor).DoAbort: Clearing 0 queued jobs and 0 jobs waiting to be queued
I, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, ExecutionPluginManager.CleanupPlugins: CleanupPlugins finished
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): SetNextState RunCleanupScript called
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state RunCleanupScript. Waiting for state change...
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is RunCleanupScript.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): calling state handler for RunCleanupScript
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): SetNextState Cleanup called
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state Cleanup. Waiting for state change...
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is Cleanup.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): calling state handler for Cleanup
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentObject: Calling ForceStop for 0 tests
I, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, TestAdapterManager: Cleanup
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, WebLoadTestAdapter: Cleanup() method called
I, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentObject: Skipping reverse deployment because m_controller is not an IDeploymentManager.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): SetNextState RunCompleted called
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state RunCompleted. Waiting for state change...
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is RunCompleted.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): calling state handler for RunCompleted
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).Flush: Waiting for 0 jobs to be processed
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, BackgroundJobProcessor<Microsoft.VisualStudio.TestTools.Common.TestMessage>(AgentObject.TestMessageSender).TryEnqueueJob: Queuing job 'FlushJob'
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): SetNextState Online called
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state Online. Waiting for state change...
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is Online.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): calling state handler for Online
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state Online. Waiting for state change...
V, 5500, 11, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentExecution: Heartbeat thread is done
V, 5500, 15, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentObject: Cleanup called with timeout of 5000
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): Exit wait for state change, current state is Online.
V, 5500, 8, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, StateMachine(AgentState): In state Online. Waiting for state change...
V, 5500, 1, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentProcess: got shutdown notification
I, 5500, 1, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentProcess: shutting down.
I, 5500, 1, 2010/07/14, 09:12:28.389, MY_PC_NAME\QTAgent32.exe, AgentProcess: exiting

Going through the log I found nothing helpful.

When I tried the tracing using options 2 - Error or 3 - Warn, no logs were produced for executions where the error occurred.

Thanks,

Ardian Daka

 

Answer 5

I think I got closer to the answer. I check the event log (why didn't I think of that before ???) and found there is an OutOfMemory error  thrown:

Event Type: Error
Event Source: VSTTExecution
Event Category: None
Event ID: 0
Date:  7/14/2010
Time:  9:46:12 AM
User:  N/A
Computer: MY_PC_NAME
Description:
The description for Event ID ( 0 ) in Source ( VSTTExecution ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: (devenv.exe, PID 4536, Thread 28) WebLoadTestAdapter: Exception occurred writing web  test result  file 'D:\SourceCode\XXX.IIS.XXXXX\Main\XXX.IIS.XXXXX.PerformanceTest\MLI.IIS.Arrow.PerfTest2010\TestResults\Perftest _2010-07-14 09_37_26_\In\38add15d-4e1d-47f8-afe1-3a4708413dbc\R_Scenario_3_1_2.webtestResult': Microsoft.VisualStudio.TestTools.WebTesting.WebTestException: Failed to serialize  WebTestResultDetails. ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Runtime.Serialization.ObjectIDGenerator.Rehash()
   at System.Runtime.Serialization.ObjectIDGenerator.GetId(Object obj, Boolean& firstTime)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.InternalGetId(Object obj, Boolean assignUniqueIdToValueType, Type type, Boolean& isNew)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteString(NameInfo memberNameInfo, NameInfo typeNameInfo, Object stringObject)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteKnownValueClass(NameInfo memberNameInfo, NameInfo typeNameInfo, Object data)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteMembers(NameInfo memberNameInfo, NameInfo memberTypeNameInfo, Object memberData, WriteObjectInfo objectInfo, NameInfo typeNameInfo, WriteObjectInfo memberObjectInfo)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteMemberSetup(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo, String memberName, Type memberType, Object memberData, WriteObjectInfo memberObjectInfo)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo, String[] memberNames, Type[] memberTypes, Object[] memberData, WriteObjectInfo[] memberObjectInfos)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteArrayMember(WriteObjectInfo objectInfo, NameInfo arrayElemTypeNameInfo, Object data)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteArray(WriteObjectInfo objectInfo, NameInfo memberNameInfo, WriteObjectInfo memberObjectInfo)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
   at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
   at Microsoft.VisualStudio.TestTools.WebTesting.WebTestResultDetailsSerializer.Serialize(WebTestResultDetails details, String filePath)
   --- end  of inner exception stack trace ---
   at Microsoft.VisualStudio.TestTools.WebTesting.WebTestResultDetailsSerializer.Serialize(WebTestResultDetails details, String filePath)
   at Microsoft.VisualStudio.TestTools.WebStress.WebTestResult.TestCompleted().

In general I would get an OutOfMemory exception after running  a few scripts in IDE, the scripts will abort or hang and a message box pops up. Restarting the IDE will aloow me to run the scripts again antil the next OutOfMemory error. The limit of memeory used by devenv.exe when this happen seems to be around 900MB for VS2008 and 700MB for VS2010. This is consistend regardless of how many other software are running or the actual total memory usage at that time.

 

Answer 6

Hello,

Great, event viewer  seems give more direct cause. There can be several different causes of the OutOfMemoryExceptions.

You can take a look at the following article for how to diagnose this kind of issue: http://blogs.msdn.com/b/billbar/archive/2008/08/05/diagnosing-outofmemoryexceptions-that-occur-when-running-load-tests.aspx

 

Answer 7

OK, I drilled more into this issue using the suggestions in the article you linked but it got me nowhere.

I too used MDbg debugging tool to try to get closer to the source but to no avail. It reported the same errors as EventViewer.

I am convinced that the error is caused by the process that writes the webtestResults file  into the disk. The OutOfMemory exception is thrown at System.Runtime.Serialization.ObjectIDGenerator.Rehash call if the webtestResults file is too large. My understanding is that I have no control on this part as this is an internal function of VS2010.

What pazzles me is that I never get this error  when I run the same test  in VS2008, only in VS2010.

 

Answer 8

Hello,

Based on our talk now, this seems to be an issue, could you please submit it on Connect to see if related engineers could confirm it with you or provide any suggestions?

In addition, it would be kind of you if you coudl post back if you get any information there.

Thanks.


Edwer Fang [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com

Please remember to mark the replies as answers if they help and unmark them if they provide no help
 
 

Answer 10

Hey Ardian,

Do you have any update on this issue? Please let me know.  Thanks.

--

Siva

 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter