Script Error 0 on LabView 2010 executables

[FSFirenze]

Good morning,

I have a LabView 2010 executable that runs on several machines, each of those have a slightly different version of the same executable.

Very recently we are experiencing several Script Errors 0 when we launch the executables on any machine.

The code of the executable doesn't connect to any external source, so we are suspecting that this has to do with one of the components we use inside the executable, but we are not able to pinpoint the problem.

Also, because it is happening on at least 3 different machines at the same time, it is suspected it could be due to a 3rd party piece of code that has been updated in the background or maybe is no longer compatible with Win 8+

I am receiving the errors also in the LabView development environment on my development machine, Win 11 home. As I open the main vi of the software I get errors from the following scripts

While labview shows loading ... cli_ure.dll
https://ni500z.btttag.com/btt.js
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.12.9/umd/popper.min.js
https://cdn.jsdelivr.net/npm/bootstrap@4.1.3/dist/js/bootstrap.min.js
https://cdnjs.cloudflare.com/ajax/libs/ekko-lightbox/5.3.0/ekko-lightbox.min.js
https://cdnjs.cloudflare.com/ajax/libs/datatables/1.10.20/js/jquery.dataTables.min.js
https://cdn.jsdelivr.net/npm/bootstrap-select@1.13.10/dist/js/bootstrap-select.min.js
https://www.ni.com/niassets/js/loader.min.js
https://www.ni.com/niassets/jquery/js/jquery-migrate-1.2.1.min.js
https://www.ni.com/niassets/jquery/jqueryui/js/jquery-ui.min.js
https://www.ni.com/niassets/jquery/js/jquery.cookie.min.js
https://www.ni.com/niassets/js/niua.min.js
https://www.ni.com/niassets/js/loader.min.js
https://www.ni.com/niassets/jquery/js/ni.js
https://www.ni.com/docs/en-US/bundle/321393d/page/download.html
https://www.ni.com/niassets/autocomplete/js/pnx.autocomplete.js
https://www.ni.com/niassets/wrapper/js/utils.js
https://www.ni.com/niassets/wrapper/js/cartCount.js
https://www.ni.com/niassets/wrapper/js/cookielaw.js
https://www.ni.com/niassets/wrapper/js/up-data-dt.js
https://www.ni.com/niassets/wrapper/js/wrapper.js
https://www.ni.com/docs/en-US/bundle/321393d/page/download.html
https://service.force.com/embeddedservice/5.0/esw.min.js
https://www.ni.com/javascript/sfdc/sfdc_chat.js
https://kit.fontawesome.com/5806b6a478.js
https://cdn.zoominsoftware.io/ni-prod-skin/public/app.d256feb6c36511d4b57f.js.gz

While labview shows loading ... Microsoft.VisualC.dll
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
https://www.googletagmanager.com/gtm.js?id=GTM-5MG82N9&l=zoominDataLayer

These are the external software we use to have the executable working:

Access Database Engine 2010 32 bit

Gigecam

iccapture

ic_labview_extension

Labview Runtime Engine 2010

Visa Runtime 5.20

OpenOffice 4.0.1

OpenOffice SDK 3.4.1

Primary Interop Assemblies 2010

Can anyone help with some guidance on what the problem could be?

Thank you!

[santo_13]

The problem could be that you're using LabVIEW 2010 on an unsupported Windows OS (Win11 home) - FYI, none of the NI software has official support for Win11, this means, you're on your own for the issues you face when using the product on an unsupported platform.

[FSFirenze]

I managed to pinpoint the issue to an ActiveX WebBrowser control that was part of a deprecated portion of the software.

I updated that ActiveX control to point to the Microsoft Web Browser Active X and the problem solved

[santo_13]

If you could provide more specific instructions and a summary of the issue, it would be helpful for others with the same problem.

[FSFirenze · Accepted solution]

Steps are very similar to what found on this KB article.

Initially I was a bit lost as my executable has something like 300 sub-VI which would make opening them very time consuming, however I realized that from the Project Explorer view you can select multiple VIs and they will all open. Then you can close them all by right clicking on the labview icon in the windows toolbar and selecting Close All. The VI that will ask you to save is the one with the issue. Then you start working on the sub-VI of the VI with the issues in a similar way, till you find the one that is generating the issue.

Finally, you copy the VI, and start deleting stuff, saving, close and reopen, till the script errors go away ... the latest thing you deleted is the likely cause of the issue

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000015AzXSAU&l=en-US