Remote Server Error

[John Donovan]

Hi Ryan,
It may depend on some OS settings, but I found that one needs to both set "XP compatibility mode" *and* run TestRemote.exe "as administrator" to get it to work.  I think if one does that there's no need to mess with the Remote.exe server directly, but again it may vary depending on other OS settings.

May I ask what custom application you are going to use the Remote interface for?  I ask, because did you see this post here where the deadtime calibration acquisition is now embedded in StartWin.exe:

https://smf.probesoftware.com/index.php?topic=1160.0

john

[Ryan McAleer]

Its like you are a mind reader or something! many thanks.

New favorite windows error:  "Error 740: The requested operation requires elevation"

[Ryan McAleer]

I tried the DeadTime feature and the Loop seems like maybe it is broken?  Using the default values (10nA-200nA, 60 second count time) the counting just continued on past 60 seconds without dumping the first line of values into the log window--the counting continued indefinitely.  I tried setting the count time to other values.  The behavior was variable. Most of the time the program just kept on counting without dumping the values and cycling to the next measurement.  On occasion the first set of values would be output, but then on the second cycle the counter just kept going indefinitely.

I had just been trying to make the same measurements using the deadtime_acquire.xlsm and had found exactly the same behavior.  There I notice some significant gaps in the time counter on the Remote.exe GUI such that spec 1 would jump by about 4s each time the count time update. I wondered if it was possible that the slow communication was resulting in the macro getting stuck in its Do Loop because it couldn't satisfy some condition?

[John Donovan]

Hi Ryan,
You are correct.   I was fooled because it works fine in demo mode but the latencies are different for actual spectrometers.  This should work better:

Code Select Expand

For motor% = 1 To NumberOfTunableSpecs%
If Not bdone(motor%) Then
Call RealTimeGetCounts(motor%, motor%, counts!(motor%), counttime!, bdone(motor%))
If ierror Then Exit Sub
If Not bdone(motor%) Then alldone = False
End If
Next motor%


john

[Ryan McAleer]

That worked perfectly! Thanks so much.

[John Donovan]

That worked perfectly! Thanks so much.

Hi Ryan,
Ok, cool.

Tonight I will update the Excel macro code likewise and upload a new PFE distribution.  Sorry for the trouble, and thanks for working with me on this.
john

[John Donovan]

Hi Ryan,
The latest Probe for EPMA distribution (just use the Help | Update Probe for EPMA menu), has the new dead time calibration acquisition code for Startwin.exe.

https://smf.probesoftware.com/index.php?topic=1160.0

Also we modified the Excel macro spreadsheets to include the improved code, so they should now work fine now too. Interestingly, the dead time acquisition .xls file was already OK, it was just the .xlsm file that had the wrong spectrometer counting wait code.

Anyway, it's all OK to go now.   Thanks again for your help.

https://smf.probesoftware.com/index.php?topic=40.msg138#msg138

john

[Ryan McAleer]

Fantastic and thanks again!

-Ryan

[Dan R]

Hi John,
I just downloaded Remote on a refresh computer. PFE works fine, but when i try connecting with Remote i get 'class not registered' -- any idea how to fix that?
-Dan

[John Donovan]

Did you try to start the TestRemote.exe first time "as admin" so the active-x server gets properly registered?

See here for more tips:

https://smf.probesoftware.com/index.php?topic=1062.0

Also for 8230/8530/iSP100/iHP200F JEOL instruments you'll also need to copy *all* the EIKS files from the Probe for EPMA application folder to the Remote application folder:

https://smf.probesoftware.com/index.php?topic=263.msg6658#msg6658

[Dan R]

John, the problem was trying to run Remote for the first time not as an administrator. We uninstalled Remote using the MSI file, reinstalled it and then ran TestRemote.exe as an Admin. This seems to have fixed the problem.
-Dan

[John Donovan]

Sorry for the trouble.

I've updated the Remote documentation and Help file to reflect the need to run TestRemote.exe "as admin" the first time it is run. 

https://smf.probesoftware.com/index.php?topic=88.0

On the older operating systems this was not necessry, but Microsoft has been locking things down pretty tight these last operating systems.

Regarding your "class not registered" error: you might not have had to uninstall Remote first, maybe just run it again "as admin".  Not sure, but glad it's working now under Windows 10.

For those interested, you can download Remote here:

https://www.probesoftware.com/resources/

[John Donovan]

Update:  I got it working. I didn't see that you had to first go to the Remote.exe in  "C:\Program Files (x86)\Common Files\Probe Software\remote.exe" and set to run on SP3 and Run as Administrator. I had changed the setting for the "C:\Program Files (x86)\Probe Software\Remote\TestRemote.exe".  Anyway, after changing those settings the Remote.exe opens after ~30 seconds.  I was then able to change the settings back to normal and the Remote.exe still worked.

Thanks!

What Ryan says here is correct with some of the newer Windows operating systems.  But there's actually an easier method now where one only needs to right click TestRemote.exe and click the Run as Administrator menu the FIRST time you run it (no messing with the Compatibility tab). But a new wrinkle recently showed up...

It used to be that when we right clicked the TestRemote.exe app and selected Run as Administrator, this automatically registered the Remote.exe app object with the OS.  But it seems that Microsoft has locked things further down recently and one may see on a Win11 computer "Class not registered for TestRemoteLoadRemoteObject" and on a Win7 computer "Active X component can't create object" even after doing the "run as admin" right click to TestRemote.exe. 

Therefore when these errors are seen starting TestRemote.exe it will be necessary to use the same trick on the Remote.exe server and select the Run as Administrator menu. The Remote.exe server is found in the C:\Program Files (x86)\Command Files\Probe Software folder. Thanks to Paul Carpenter and Owen Neill for working with us on this issue.

Note also that this is the same folder that one must copy the JEOL EIKS files to, for JEOL 8x30 and iHP200F instruments. These files are:

eiksJSample.exe
jeoleiks.dll
JeolEIKS.ini
mfc100.dll
msvcr100.dll

Remember, these need to be copied from the Probe for EPMA application folder (usually C:\Program Files (x86)\Probe Software\Probe for EPMA) to the Remote.exe application folder (usually C:\Program Files (x86)\Common Files\Probe Software.