error: Cannot obtain value  
Author Message
Wouterd





PostPosted: Visual Studio Debugger, error: Cannot obtain value Top

Hello,

When i am debuging my application, i can't read the values of the variables used in the application. I see only the message: "error: Cannot obtain value" as the value. How can i fix this

I use the tool visual studio 2005, vb .net and sql server 200.

os windows xp

 

Wouter



Visual Studio14  
 
 
Ghayth





PostPosted: Visual Studio Debugger, error: Cannot obtain value Top

Hi;

I'm getting the same message (error: Cannot obtain value) when debugging an asp.net app.
I'm using:

VS 2003,
.Net 1.1
running on Win2003 SBS.

the only descussion about this issue mentioned that using too many parameters in a function might cause this message but
I'm not using parameters in this function.



 
 
D Radcliffe





PostPosted: Visual Studio Debugger, error: Cannot obtain value Top

I'm getting the same problem, using Oracle's ODP.NET.

The value of an OracleParameter is shown as "error: Cannot obtain value", but a QuickWatch reveals that the internal value, as obtained from the database, is visible - it is just refusing to make it available in the pubic properties.

This problem only started last week, but ODP and the .NET framework hasn't been changed...

Is it possible some other Windows security patch has caused this


 
 
Ghayth





PostPosted: Visual Studio Debugger, error: Cannot obtain value Top

I've realized that the size and complexity of teh object i'm working on has something to do with it.
I'm calling 4 functions (none has parameters) everything goes normal till i reach the 4th function, that's where i won't be able to access the values of my variables.

I think that if i split the 4th function into many smaller functions i may avoid this "error: Cannot obtain value" issue, but the problem is that i can't break the 4th function anymore....!

try to find out in which function you start getting this error, and see if you can split it into smaller ones.

I still need someone from MS to tell us what is going on with this error....and if their is a fix for it.