Author |
Topic: Connect failed, invalid pointer address (3 messages, Page 1 of 1) |
||||
---|---|---|---|---|---|
Moderators: VPfau | |||||
jlanawalt Posts: 88 Joined: Feb 12, 2009 |
We have a customer that cannot log in. The OnError callback LPDISPATCH exception ex->Message is:
Connect to OEC Server failed. Please check your internet connection. The system detected an invalid pointer address in attempting to use a pointer argument in a call I have seen the .NET stack trace dialog about pointer addresses when a different version of OECAPICOM is installed and registered. This is nothing like that message and no other OEC program is installed on the system. How can we find out what pointer argument had an invalid address on their system? What is the likely cause of this error? Thank you, -- Jacob Anawalt |
||||
VPfau Moderator Posts: 164 Joined: |
Hello,
This is an Windows Socket error. See here: http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx There are not much places where it could occur in the API lib. It goes from Connect method of OECClient. Likely it is something wrong with a first parameter (Host) of this method Vitaliy Pfau |
||||
jlanawalt Posts: 88 Joined: Feb 12, 2009 |
Interesting. We don't give our users direct access to that value, it is hard coded as either sim.openecry.com or prod.openecry.com depending on if they choose the "Demo" or "Real" radio button at login so the host value should always be the same from any customer.
The customer was using a different setup. They were using Bootcamp on a Macbook Pro with only Windows 7 installed. They were going to take a break until the end of this month and order a new computer (but I think it was going to be another Mac...) Thank you for the insight, -- Jacob Anawalt |
||||