RSearchLib::IRSearchResponse get_Instruments(&l_instruments) throws

igorg

I have very strange behavior that I cannot explain.

Every morning I run the program (C++ COM API) that does:

1. Initialize Eikon - Starts desktop application

2. Wait for a response.

3. Create RSearch request and send request

4. Wait for the response.

5. Get response with

l_hr = m_pIRSearchResponse->get_Status(&l_RSearchQueryStatus); where l_RSearchQueryStatus == S_OK.

6. l_hr = m_pIRSearchResponse->get_Instruments(&l_instruments); - this line throws access violation that I cannot catch anyhow.

The problem is it happens every morning once or twice in a row. After I step in debug mode, the error is gone until next morning.

I know it looks weird, but I don't have a way to deal with this crash.I checked m_pIRSearchResponse is not NULL and based on msxml3.dll in the error, it's something internal.

Please check the screenshot:

Any idea why it can happen?

Thanks.

Find more posts tagged with

eikon

eikon-com-api

Accepted answers

Alex Putkov.1

Your guess is as good as mine. The exception is in a Microsoft DLL. Maybe you should try updating MS XML Parser. Or maybe it's the latest version of the parser that causes the problem.

All comments

Alex Putkov.1

Your guess is as good as mine. The exception is in a Microsoft DLL. Maybe you should try updating MS XML Parser. Or maybe it's the latest version of the parser that causes the problem.

igorg

I checked the versions. I have 3 and 6 with the latest updates.

I don't use msxml in my project. But Eikon COM uses msxml internally, so I have no chance to track the error and find out what call causes it...

Is there a way to tell Eikon to use msxml6?

igorg

@Alex Putkov.1

I believe I found what causes the crash.
First of all, it's not just first request per day. It's a first request per day per exchange.

The problem is: eikon's callback function signature looks like :

OnRSearchQueryUpdate(RSearchLib::IRSearchResponse * pIRSearchResponse)

What I do (and what fails) is I pass this pointer to another thread which parses the data.

The call on this pointer crashes if there were no request for this data today. This makes me think Eikon saves the data request/response in its cache and returns a response from its cache without a problem. But if there is no cache yet... it does something not allowed in Single Threaded Apartment environment that leads to crash.

I know how to deal with it in my code, but will test it only in a few hours.

Anyway, it would be nice to get some exception instead of Access Violation.

EXPLORE OUR SITES