When trying to run the dead time spread sheet using Excel 365 I am getting this error.
"Active X component can't create object"
The Microprobe is a JEOL 8350F-Plus
Not sure what object Active X can't create
Hi Keith,
I've never tested Excel 365, but I do know that we need to modify how the Remote Server app is installed because Microsoft is really starting to lock things down in the SysWOW64 folder. I'm assuming that you installed the Remote Server app using the latest Remote.msi installer? See the Update page on our web site.
Since you have a JEOL 8230/8530 you will also need to copy the JEOL EIKS files from your PFE app folder to the same folder as the Remote.exe server executable which (for the time being) is C:\Windows\SysWOW64. The list of files you need to copy are described in this post:
http://probesoftware.com/smf/index.php?topic=263.msg6658#msg6658Also did you try running the TestRemote.exe app in the Remote application folder? That is a good way to make sure everything is working first before trying Excel. For example you might need to right click on the Remote.exe app in the SysWOW64 folder, click the Properties menu and click the Compatibility tab and check the box to "Run this program as an administrator". You might also need to do the same for the TestRemote.exe app but probably not.
So as a sanity check I ran TestRemote.exe on my installation (Win 7 64) and it worked fine. Then I tried running the DeadTime.xls spreadsheet from the Remote application folder and I got the error "This operation requires elevation".
That means Windows is detecting someone trying to run an app in the SysWOW64 folder, which it doesn't like. So I found that I had to find the Excel app which is Excel.exe (I'm running Office 2010 or v14), which is in the Program Files (x86)\Microsoft Office folder and as above right click it, then click the Properties menu and then click the Compatibility tab and check the box to "Run this program as an administrator". That fixed it for me.
Again, we need to re-write the installer so all these Remote server files go into a different folder that Microsoft isn't being so protective about. I'll let you know when we have the new installer working, but in the meantime you should be able to get it working following these instructions.