Report Connection Time Out

[Charlie-Henry]

Hi there,

I am getting a similar issue to this issue where my report is timing out before being converted to a dataframe. It is about 30,000 records. After running my_report.to_dataframe() I get an error after five minutes, that my connection was timed out:

ConnectionError: ('Connection aborted.', ConnectionResetError(54, 'Connection reset by peer'))

After, when I check my connection object conn.status(), I still get:

Connection to MicroStrategy Intelligence Server is active.

Is there a way to paginate through our report object? I see there is a limit parameter, but not a starting location. Or is there a way to increase the timeout of this connection?

Currently running mstrio-py == 11.3.6.102

My code is here

[urszulajaczewska]

Hi @Charlie-Henry, we'll look into it and let you know when we gather more info.

[vioreldinu87]

Hi,

Your report is based on a MSI cube or you get data directly from a DB?

[Charlie-Henry]

@vioreldinu87 We are getting data from an external DB.

[vioreldinu87]

I ask you because if you say the conection to msi remains alive, maybe the connection is reseted in DB not in MSI.

I had a similar message but not with mstrio-py but with A script based on MSI SDK and the connection was dropped in DB.

[Charlie-Henry]

I have no issue running this report in the Microstrategy web app, still takes about 5 minutes but I don't get a timeout error?

[vioreldinu87]

Also you can check in dsserror.log from iserver to see if you have more details.

[urszulajaczewska]

Hi @Charlie-Henry, we'll work on this issue and fix should be available with the release of Report module.

[Charlie-Henry]

Great thanks @urszulajaczewska. We have a sort-of workaround in the meantime because it appears to cache the results and if I retry after ~10-15 minutes I can get my_report.to_dataframe() to run.

[p-kowal]

@Charlie-Henry Thanks for the patience. This is just to inform, that Reports module is now scheduled to be delivered with December release of 2023, so quite long to go. This is why we don't close this issue. Do you find your workaround working well?

[Charlie-Henry]

@p-kowal thanks for the update, yes my workaround is still working well

[urszulajaczewska]

@Charlie-Henry Report module has been moved to be released in Q3 of 2024, possibly earlier. We're sorry for the inconvenience and thank you for your patience.