How do I update browser plugins for viewing different LabVIEW build versions?

[Randall_T]

“LabVIEW Client version is incompatible with LabVIEW server version.”

I am changing the systems on my network from 7.0 to 7.1 executables. I get the above message when trying to view and control the 7.1 build applications from Internet Explorer.

How do I update the browser plugin to run the version 7.1 applications? Can both plugins exist on the computer in order to view and control versions built by both 7.0 & 7.1?

I will need this update on computers that may not have the runtime executable installed as yet.

Randall

[EdDickens]

All you need to do is install the LabVIEW 7.1 runtime engine on the target machine. The browser plugin will get installed with that.

LabVIEW 7.1.1 Runtime for Windows.

Ed

[Randall_T]

---

@Ed Dickens wrote:
All you need to do is install the LabVIEW 7.1 runtime engine on the target machine. The browser plugin will get installed with that.

[link removed]
Ed

---

Thanks for the immediate response.

I should have mentioned in the original posting that the error message was received on a machine that has the full development version of 7.1 on it. The run-time engine on the machine running the application was built from the development machine.

For some reason installing 7.1 does not change the application that Microsoft’s IE uses to view the embedded vi . Even if trying to use this with the local host instead of the remote machine I still receive the same message.

I believe I will find the same problem when attempting to install the runtime engine on the client machine. I am willing to try but the client machine will need to switch to view both 7.0 & 7.1 apps until I get all the test machines on the network updated to 7.1. If there is a way to trigger in the HTML file which plug-in to use this would help.


Again thanks for the initial response. Any more suggestions will be appreciated.

Randall

[EdDickens]

You should be able to run either version of a built executable on a machine with both versions of LabVIEW installed.

If you look at the html code that gets generated by LabVIEWs Web Publishing Tool, it specifies which version it was built in using a CLSID number that links back into the registry where it gets the correct path to the .dll for that version.

Open up Explorer and navigate to "C:\Program Files\Internet Explorer\PLUGINS". You should see an ActiveX control for each version of LabVIEW you have installed. I have three on this machine. "LVActiveXControl.dll", "LV7ActiveXControl.dll" and "LV71ActiveXControl.dll". If you are missing the 71 version, try just reinstalling the runtime engine for 7.1 on your machine. It may have been deleted by an errent IE upgrade or patch, or the original installation didn't work.

If you do see all of the versions, something else odd is going on. I'm able to run both 7.0 and 7.1 apps in my browser. Not sure what else to try after that.

Ed

[Randall_T]

---

@Ed Dickens wrote:
You should be able to run either version of a built executable on a machine with both versions of LabVIEW installed.

If you look at the html code that gets generated by LabVIEWs Web Publishing Tool, it specifies which version it was built in using a CLSID number that links back into the registry where it gets the correct path to the .dll for that version.

Open up Explorer and navigate to "C:\Program Files\Internet Explorer\PLUGINS". You should see an ActiveX control for each version of LabVIEW you have installed. I have three on this machine. "LVActiveXControl.dll", "LV7ActiveXControl.dll" and "LV71ActiveXControl.dll". If you are missing the 71 version, try just reinstalling the runtime engine for 7.1 on your machine. It may have been deleted by an errent IE upgrade or patch, or the original installation didn't work.

If you do see all of the versions, something else odd is going on. I'm able to run both 7.0 and 7.1 apps in my browser. Not sure what else to try after that.

Ed

---

Excellent!
My problem was with the html code. Once I regenerated the web page using 7.1 the problem was solved.

Thanks for the path information to the plugins and what .dlls to look for.

You have been extremely helpful.
Thanks again.

Randall