eSignal loaded and appears to run without issues on Windows Vista Home Premium. My Visual Basic project references eSignal but my previously functional program hangs up when attempting to set a reference to IESignal.hooks. Any ideas or sympathy?
Announcement
Collapse
No announcement yet.
Implementing the API in Windows Vista
Collapse
X
-
I am running as an administrator but I am not sure if that is what GenSpoo meant.
However, on the surface this does not appear to be a security issue. The IESignal objects are visible in object browser. My Excel VBA code is:
Dim WithEvents fu as IESignal.Hooks - at the module level
Set fu = New IESignal.Hooks - in the procedure which fails.
The "Set fu" statement yields error 429 (ActiveX component can't create object or return references to this object). The help screen suggests that: 1) the class isn't registered, 2) a DLL is missing or corrupted, 3) a required license isn't available, or 4) access is explicitly denied.
Any ideas? Should I have done something special to authorize access when I loaded ESignal on my new machine?
Thank you all in advance.
Comment
-
GenSpoo, thank you for your reply. After following your instructions, there appears to be another glich because I still hung up at the same point with the same error message.
Playing around, I manually restarted eSignal as an administrator. This did something somewhere because I now have a new error message at the same point: "Automation Error - The requested operation requires elevation." Hey, at least something moved.
UPDATE! Running both Excel and eSignal as adminstrators (rather than just logging in as an administror) appears to do the trick. Thank you GenSpoo.Last edited by Cone Killer; 06-05-2007, 01:28 PM.
Comment
-
Vista and IEsignal Still Getting an Issue
Hi,
I've turned on "run as administrator" both for esignal data manager (shortcut and exe) and for excel exe. Changing the esignal app definitely had an impact as I stopped getting an error about interface. However despite all these changes I am still getting:
"error 429 activex component can't create object"
When I try to run the following line:
Set esignal = New IESignal.Hooks
This worked fine in xp.
Please help!
Thanks
Lin
p.s. I am operating within user context of "system" in vista.
Comment
-
Vista and IESIgnal.. need winsig enabled
OK thanks to use processmonitor tool was able to debug further. I was confused it turns out. I needed to administrator enable winsig . I was enabling winros (not sure if this needs it too). I'm going to leave these posts in though in case hope future folks.
Thanks
Lin
Comment
-
Under Vista I can't get events
With the help of these posts, I was able in Vista only to instantiate IESIGNAL.HOOKS. The problem is I'm still not getting events (either OnBarsReceived or OnQuoteChanged).
My guess is that something's not communicating to eSignal. For example, RequestHistory is returning a 0 cookie. RequestSignal doesn't appear to throw an error, so I don't know whether it's communicating or not.
I'm running everything under "Run Administrator"...winrow,winsig and excel. Data Manager says I'm alive.
On all apps I've allowed local security elevation, set compatibility to XP service pack 2, "Full Control" security levels. The only thing I couldn't change was "Privilege Level" under <app>Properties.Compatibility. This happens to be "Run the program as Administrator." The checkbox is disabled, and I don't know how to get it enabled so I can turn it on.
This app runs fine under XP; it fails under Vista. Any ideas?
Comment
-
The problem was resolved with what surely seems to be voodoo.
I noticed in the eSignal app on the Vista machine that although quotes were streaming in, charts were not.
In eSignal app I went to Preferences.Connections. My (correct) customer ID was there as the account number. So, I changed it to my customer name. And, bingo...everything started to light up.
I recall that when I downloaded eSignal to the vista machine, I used my account number. This was probably the first mistake.
So, if you are intending to run Vista, you may want to assure that the account is the name and not the number!
Comment
Comment