Script Error when click on Find Example in LabVIEW Help

[Vincent_Claes]

I still have this issue, any help?

[Bob_Schor]

Vincent,

     You seem to be a new Poster to this thread.  Most of the other Posters have documented the Version(s) of LabVIEW they are using (I would include whether 32-bit or 64-bit LabVIEW) and detailed information on the OS, including name, "Family" (Home, Professional, Enterprise), 32- or 64-bit, Version or SP level (use WinVer to find out for Windows 10).

     The few times I've seen it on my systems, there was a problem with the LabVIEW installation.  Doing a complete removal of LabVIEW and all NI Software followed by a careful reinstall usually fixed it -- the one case where it didn't was caused by my mistakenly installing a superceded LabVIEW Patch.

Bob Schor

[RavensFan]

Bob,

There is definitely an issue  with a Microsoft KB update that was pushed out by MS.  It has occurred to me.

I was able to verify it was the update because when I uninstalled that update, the problem went away.

Unfortunately, two things have conspired against me since then.

1.  Our corporate update policy wound up forcing the same broken MS KB update on me again a couple days later.  So even if I did remove it again, I would just have been battling a vicious cycle of having to keep removing it and all the painful reboots, to just have all the effort lost when they went and forced the update again.

2.  Since then, our IT policy has gotten even more strict and I can't even install or uninstall software on my PC.

The KB update that is supposed to fix the broken KB update hasn't been pushed to my computer yet. I don't know if it ever will.  So I can't confirm if that does fix the problem in my case.

Also, I just haven't had time to try to get IT to fix things for me.  This particularly KB install is really only a small part of what is a larger battle to fight to get control of my machine again from our IT overlords.

[altenbach]

Personally, I don't micromanage windows and surgically remove certain random updates, because we cannot win and it is a continuous whack-a-mole and it will only create more incompatibilities down the line.

As a result, ALL my LabVIEW installations are still fully broken for all external links inside LabVIEW help.

I really hope that NI works with Microsoft to find a solution. The fix is up to Microsoft and if there is sufficient pressure, it will be fixed with yet another windows update. Fingers crossed.

[RavensFan]

Hi Altenbach,

I agree with you there.  It would be some serious frustration to try to keep it sorted out.

BoKnow's message 47 claims there are some newer KB's that fix the issue.

I had figured out that KB 4462918 had broken my system.  It first installed on 10/18/18  I uninstalled it and said in message 27 on 11/6/18 that removing it fixed my system.  However it was reinstalled automatically by my IT on 11/7/18 and broke again.  After another removal, it automatically reinstalled again on 11/8/18

Since then, I've had the following KB's installed by our Landesk update process.

KB4465661 12/7/18

KB4467686 12/7/18

KB4467694 12/7/18

KB4471329 1/11/19

KB4477136 1/11/19

KB4483232 1/11/19

KB4480978 1/18/19

KB4486996 2/21/19

KB4485448 2/21/19

KB4487038 2/21/19

None of these have fixed the problem.  And none are listed in BoKnow's message 47.  But the one is very close in number to Bryan's list in message 49 of Windows 10, version 1803: KB4480976

The problem with Microsoft is that they create a lot of patches, but don't necessarily push them all.  And the other problem I have is our IT ultimately decides which patches they will and won't push to us through Landesk.  And if they do, it may be several weeks after MS publishes them.

I just haven't been bothered by the error message enough yet to try to fight with our IT department install any patches for me or uninstall the bad patch and put an exception in so I won't get it pushed again the following day.

[Dhubbell]

I opened a thread after this original post, I didn't think my was related to this same Script Error Message, but, I agree with Bill, this is the same error.  I'm throwing my findings into the mix in this thread and I also opened a support request with National Instruments.

https://forums.ni.com/t5/LabVIEW/Script-Error-URL-s-switfypecdn-com-install-v2-st-js/m-p/3897099

I like Altenbach's "whack a mole" analogy.  Not ideal to keep rolling back updates.

It would be nice if we could find the source from the "Script Error", in my example, it says "This Page" on "line 0 ",  "Char 0", and "Code 0".   Perhaps "Script Errors" could be a little more vague? 

This error occurred on my development machine, W10 Pro, Labview Professional Development System, V18.0.1f2 (32 Bit).  After digging around my company, I found W7 and W10 Machines running the same Application saw this "Script Error" without any Labview update.  I'm sure it's related to a windows update.  I also noted simply opening the VI in the Labview IDE displayed the "Script Error" and after compiling the "Script Error" appears on all other W7/W10 machines.

The one good thing is my Application seems to run after they clear the "Script Error".  Just annoying to see your application throw a "Script Error" to an unknown website when your users run your application.  It only brings up more questions.

Doug

[Dhubbell]

I have Three main Labview Applications I've developed.  Sales, Shipping, and Quality Control.  Sales and Shipping show no signs of the "Script Error".  Only my QC applications shows this "Script Error".   All of these three applications use many of the same vis.

I find it interesting the QC applications is showing these "Script Errors" while Sales and Shipping are not affected by the "Script Error".

Obviously, the "QC" application is using something different, than Sales, and Shipping.  Trying to track the offending VI is the problem.  The "QC" application does use GPIB interface while Sales and Shipping do not use GPIB.

Does anyone else see any other patterns with their "Script Errors" between different Applications?

Doug

[altenbach]

I see that you moved your discussion here, but it somehow does not seem fully related. It seems you are seeing this in "applications" (i.e. standalone executables built in LabVIEW. Is this correct?) while the original problem occurs when using features of the LabVIEW help in the development environment.

"Script error" is such a generic term and the exact error messages here are quite different. I wish I understand what's going on...

[Dhubbell]

Yes Altenbach, true, my "Script Error" isn't related to the "Help" menu in Labview.

My "Script Error" displays when I open the main VI in my project.  As the VI loads into memory this message appears in the IDE:

This "Script Error" also appears when I build the "exe" and then when the Application Runs, it displays this "Script Error" on the user's desktop.  If you answer "No" to continue running the script, the application runs fine.

I apologize if this isn't appropriate forum thread. 

Should I move back over to my original thread and stay out of this "help" menu post?

I've never seen a "Script Error" in any of my Labview applications until recently.

Thank you,

Doug

[billko]

---

@Dhubbell wrote:

Yes Altenbach, true, my "Script Error" isn't related to the "Help" menu in Labview.

My "Script Error" displays when I open the main VI in my project.  As the VI loads into memory this message appears in the IDE:

This "Script Error" also appears when I build the "exe" and then when the Application Runs, it displays this "Script Error" on the user's desktop.  If you answer "No" to continue running the script, the application runs fine.

I apologize if this isn't appropriate forum thread. 

Should I move back over to my original thread and stay out of this "help" menu post?

I've never seen a "Script Error" in any of my Labview applications until recently.

Thank you,

Doug

---

I think they are definitely related, and most likely share a common cause.  That being said, they are probably different enough to warrant their own topics.  I think it's good that the two are linked, though.