Posted: Apr 21, 2010 @ 07:04 PM             Msg. 1 of 10

We have one user who is receiving this exception during a call to OnLoginComplete: Return argument has an invalid type. What could be the cause?

---

Thank You,
Sierra Chart Engineering

Posted: Apr 22, 2010 @ 08:41 AM             Msg. 2 of 10

Hello,

Do you have a stack trace or any other details of this exception?

Posted: Apr 22, 2010 @ 06:41 PM             Msg. 3 of 10

We could provide you the source code of the function. But at this point we don't know if the user is still having the problem. They have not responded to us. Being that this is the only report we have it, at this point we will just let this go.

---

Thank You,
Sierra Chart Engineering

Posted: May 03, 2010 @ 03:22 AM             Msg. 4 of 10

We now have a lot of users getting this exception involving various functions in your API:
Exception caught: Return argument has an invalid type.

This issue began with your new version 3.5. This happens when using Remoting.

What we did is take the API files from this version and rebuild our program with them. This solved the problem for us, but still some of our users are having this same exception even on your new version. We do not know what to do.

Apparently you have changed something in your newer version to break compatibility with the old API files when using Remoting. However even with the new files, we still have users with the same problem.

---

Thank You,
Sierra Chart Engineering

Posted: May 03, 2010 @ 08:19 AM             Msg. 5 of 10

Old version of API: do you mean 3.4 branch or 3.5.0.7 build?

Posted: May 03, 2010 @ 05:33 PM             Msg. 6 of 10

The prior version we were using was from the 3.4 branch.

---

Thank You,
Sierra Chart Engineering

Posted: May 04, 2010 @ 08:40 AM             Msg. 7 of 10

OECAPI 3.4 and 3.5 are compatible on the interface level, but for remoting it requires recompiling of application to make sure OEC Trader and the application have references to the same version of OECAPI (3.4.0.0 or 3.5.0.0). OECAPI version is constant inside one branch.

Posted: May 04, 2010 @ 04:19 PM             Msg. 8 of 10

We understand this. And we did recompile. However, still some users are having a problem with the latest Sierra Chart version and the latest version of OEC Trader. Although we have not heard of any problems in the last day. So maybe everything is OK for unknown reasons.

---

Thank You,
Sierra Chart Engineering

Posted: May 04, 2010 @ 04:21 PM             Msg. 9 of 10

Could you please send me in private usernames and timestamps of issues?

Posted: May 05, 2010 @ 02:14 PM             Msg. 10 of 10

If we have another report of this issue, we will send them to you.

---

Thank You,
Sierra Chart Engineering