Vision Builder error

[uka76_lc]

Good morning,

I have a problem with the 'vbaiLaunchLocalVBAIEngine' function.

When I start the debug session, this function resolves to a fatal run-time error, but sometimes it works correctly. I have used this function in other systems without problems and haven't idea how to fix it.

My system use 'win10 pro 64 bit' - 'Vision Builder AI 2019' Built 20191112230121.

This is the full function:

   String255 Builder_sessionName_pos1;  

   vbaiLaunchLocalVBAIEngine ("TestPos1", VBAI_2019, 1, Builder_sessionName_pos1, sizeof(String255));

In attacched picture the error popup.

My colleague (with the same PC and the same builder version of my PC) tried to use my application with his PC and it works correctly.

I think that I have an installation problem 😞

Thanks for help.

Luca

[Mattia.G]

Hello,

I have the same problem. I'm using your same varsion of OS (win 10 64bit v1903) and Vision Builder.

The strange thing is that this fatal-error does not always occur but in some cases the execution works correctly. (I'm trying with the CVI API Example)

Have you find any solution?

Thanks for your help.

Mattia

[Pinball4Me]

Are you using Visual Builder 32 bit or 64 bit?  I had the same intermittent issue when I started using VBAI (x64).  The problem went away when I switch the CVI compiler build to 64 bit from 32 bit.  I haven't seen the issue since. 

[Mattia.G]

I need to build my CVI project in 32bit. So have I to use Visual Builder 32 bit?

When i Lauch the engine from CVI project I tried to call  vbaiLaunchLocalVBAIEngine ("Test", VBAI_2019, 1, sessionName, sizeof(String255)); with Version parameter VBAI_2019 but I have the same problem.

If I switch the CVI compiler build to 64 bit from 32 bit it seems work.

Is it possible that there is a problem with 32 bit build?

[Pinball4Me]

I set the "Version" parameter to NULL so it uses the latest VBAI version installed.  If I upgrade to a newer version of VBAI in the future, I won't need to remember to change this in my CVI application and recompile.

I'm not a VBAI expert by any means but it doesn't sound like a build issue.  Just to prove things out, have you tried compiling CVI in 64 bit as a test to see if the issue goes away?

[Mattia.G]

I'm not a VBAI expert too. I'm trying to use VBAI for the first time in coomunication with CVI.

If I set to NULL "Version" parameter and build CVI in 64 bit configuration I don't have any problem. Everything's works at well. (The VBAIEngine is at 64 bit)

It seems that the fatal runtime error occurs only when I built the CVI project in 32 bit configuration.