TOPIC:

Hello,
I have problems while debugging in VO2838 (Win10 Enterprise 64 Bit, 21H2):
First few attempts it says *** err type: 0x00000033 *** instead of variable contents (see attached picture)
after a while of debugging just an empty content or NIL.
In the picture dwLen is just a local dword.
Same while hovering over variables in source code.

Any ideas?
BR Kurt

Hello Kurt,

It often helps to reindex the VO repository.

Dick

Dick,
I tried, but no change.
Thx
BR Kurt

I found some more info about this specific error. Someone got it when trying:

After changing

tothe problem was gone. But I would expect retrieving your variable (not a function call) in Ctrl X should not give that error (maybe only when you defined it as usual, but I think it must be a Dword.

Cause nr 2 (I had that myself years ago) was solved after SP2, but 2828 is SP4..

Solution nr 3 is reindexing but sometimes you need to create a new repo and import all AEF's. VOPP helps you rebuild easily.

Do you have the same error with running functions or showing other variables?

Dick

Hi!
I have issues with EVERY variable, never any content is shown. There are different *** err with hex codes.
After some time it just tells the variable name but no more content.
Same effect with ctrl-x.
But if I open the local window in debug I see the variable content.
With show call stack it works, too.
Weird...
BR Kurt

Hello!
A new try:
I uninstalled CAVO2838, reinstalled, created a new repo and imported my libraries and applications again.
But the problem is still there: Neither hovering over a variable nor ctrl-x evaluating the variable works. Evaluating creates error messages like '*** err type: 0x00000033 ***' first few tries, later on shows wrong or empty values.
In separate windows for local and global variables as well as call stack the values are correct!?
Windows 10 Enterprise, 21H1, VO 2838 (VO28 SP4).
Is there anybody with Windows 10 where this is working?
Any idea, what to look for?
BR Kurt

Hello!
It's getting worse after reinstallation: now I can't set any breakpoint outside the start routine (Error setting breakpoint) and with single step VO crashes.
Ever seen that effect?

EDIT: This could be solved by Windows restart, but the main topic (no variable content shown) remains.

BR Kurt

Hi Kurt,
I can confirm that this worked on all our machines before upgrading/changing from Windows 10 Pro to Windows 11 Pro.
Maybe it is an antivirus issue?
Wolfgang
P.S. for us it works on Windows 11 too