VB Script Runtime Error "Cannot execute a program"

Replies to This Discussion

Permalink Reply by Florian Frank on September 14, 2012 at 6:28am

Hello,

Did you try to clean up your temporary files? Maybe its some issue with those *.cmdline files. You can use CCleaner from piriform to clean your system. I don`t know if this helps :-)

Cheers

FF

Permalink Reply by Jonatan Schumacher on September 14, 2012 at 7:33am

Hi Heidi,

Hmmm...

What happens if you place an empty VB script component on the GH canvas? And what if you then write a simple script such as A = X*Y?

I have recently seen this problem in our office. It occurred when sharing GH files that were created with GH on Rhino 5 with users that are running Rhino 4. You may have to update your .Net framework with Windows update.

Permalink Reply by HEIDI WERNER on September 14, 2012 at 8:00am

Hello Florian and Jonatan:

Thanks for the tips; I'll give them both a shot.

Jonatan-

The same error pops up with a new, unlinked VB component on the canvas (with a simple script).

These are tutorial files being generated in Rhino SP9 and then distributed to users (like myself) running Rhino 4 SP8.

Permalink Reply by David Rutten on September 14, 2012 at 8:10am

vbc.exe is the Visual Basic compiler. It is used to create actual runtime instructions from the textual code you type into a VB script component. 

I don't think I've seen this particular error before. Can you try and re-install the .NET 3.5 full framework?

http://www.microsoft.com/en-us/download/details.aspx?id=21

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by HEIDI WERNER on September 16, 2012 at 2:08pm

Hello David:

I'm currently running .NET Framework 4... are you suggesting un-installing this and returning to .NET Framework 3.5?

Thanks.

Permalink Reply by David Rutten on September 17, 2012 at 3:20am

You need .NET 3.5 to run Grasshopper on Rhino4 and .NET 4+ to run on Rhino5. You can have both installed at the same time.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by HEIDI WERNER on September 16, 2012 at 3:32pm

...it also seems like this VB component is being directed to vbc.exe in the .NET Framework 2.0.50727 folder eventhough my system has the more recent v4.0 installed. Would this be the issue?

The following versions are in this folder: C:\Windows\Microsoft.NET\Framework 

v1.0.3705

v1.1.433

v2.0.50727

v3.0

v3.5

v4.0.30319

I re-installed .NET Framework 4.0 and the associated Run Time Updates 4.0.2 + 4.0.3; but no change to the VB component error message.