Error: Could not convert variant of type (OleStr) into type (Dispatch)

Hi Cosmin,



It works fine for me in the latest TestComplete version - 8.70; see the attached screenshot. I have Visual Studio 2010, too.



So, I'd recommend installing the latest TestComplete version and see if the problem persists.





By the way, a similar issue with TC 7 was discussed in the following thread:

Error viewing locals or inspecting an array of objects during debug

You can also try the suggestions listed there.

Hi Helen,



Thanks for your feedback



It worked for me in TestComplete 7.5 until I installed VS I think. I can't update to TC 8 and I also need Visual Studio.



I will try to reinstall TC7.5 and I;ll inform you if the problem will be fixed.



Thanks

I've reinstalled TC7.5 and MS Script debuger but the problem persists. 



How can I fix this problem?

Hi Cosmin,



You may also try to close TestComplete and VisualStudio, rename <Program Files>\Common Files\microsoft shared\VS7DEBUG\ folder (<Program Files (x86)\Common Files\microsoft shared\VS7DEBUG\ in case of 64-bit system) and then reinstall VB Script Debugger.

Maybe, this will help...

Thanks for your feedback.



I've renamed C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG to VS7DEBUG2 and reinstalled MS Script Debugger to 

C:\Program Files\Microsoft Script Debugger and the TC problem was fixed



THANKS

This problem was fixed but another appears:



When I try to close TestComplete an error message appears: 

"TestComplete has encountered a problem in module tcsriptextension.pls and needs to close. ..."



In the reports detail> Additional information> Common information I have the following information:

Exception address: 0x04E08D5C Exception code: 0xC0000005

Report number in session: 1

Session id: {18919362-58EF-4BC6-A4AF-D2DE39F36530}

Product name: TestComplete

Product version: 7

Command line: "C:\Program Files\Automated QA\TestComplete 7\Bin\TestComplete.exe" "D:\Cosmin\Plaxis\SVN\TC7_Work\projects\Plaxis2D\Plaxis2D.mds"



I've also send this report using the build in functionality....



How can I fix this problem?

Hi Cosmin,

This problem was fixed but another appears: When I try to close TestComplete an error message appears: "TestComplete has encountered a problem in module tcsriptextension.pls and needs to close. ..."

This error was fixed in TestComplete 8.0.

There's also a patch for TestComplete 7.52. To get the patch, please contact our Support Team and refer to this thread.

I also get this error. I tried:

Close TestComplete and VisualStudio, rename <Program
Files>\Common Files\microsoft shared\VS7DEBUG\ folder (<Program
Files (x86)\Common Files\microsoft shared\VS7DEBUG\ in case of 64-bit
system) and then reinstall VB Script Debugger.



All that got me was when I Inspect any objects I create, the properties end up blank, but everything that was a property before now is a field.



I had to reinstall my VS2010 SP1 to get it back. Just trying to deal with the "Error: Could not convert variant of type (OleStr) into type (Dispatch)"

Hi Craig,



Sorry to hear you're having this error. To help us troubleshoot your problem, please post here the following information:

* the TestComplete version, as in Help > About,

* the Windows version and bitness,

* the Internet Explorer version,

* the Visual Studio version and edition, as in Help > About Microsoft Visual Studio,

* what exact objects you're inspecting - application objects, COM objects, JScript native objects, etc.,

* a sample script for reproducing the issue,

* a screenshot of the Inspect window with the error.

Hi Helen



- TestComplete version 7.52.678.7 - Enterprise edition

- Microsoft Windows XP Professional Service Pack 3

- Internet Explorer 8 (but I don't really use IE)

- Visual Studio 2010 (Version  10 SP1); .NET Framework 4.0

- Microsoft Visual Web Developer 2010 Express (Registration expired)

- what exact objects you're inspecting - I am inspecting JScript native objects

- example 


function Test() { 

  var a = [ [0,0], 

                [1,1], 

                [2,2]] 

  //inspect element 

} 
- screenshot of the Inspect window with the error is attached