asked on December 9, 2021
Only loads 1 index of 6 configured, in the rest shows this error message:
"2021-12-09 08:46:41|ERROR|Flexmonster.DataServer.Core.IPrepopulatingService|Index espejoRIS cannot be loaded. Details: Cannot load data from database executing query "SELECT * FROM AM_mando.v_fleximonster_espejo_ris". Please check query or connection string. at Flexmonster.DataServer.Core.DataLoaders.DataLoader.Load(String index) at Flexmonster.DataServer.Core.DataStorages.DataStorage.GetOrAddAsync(String cacheKey) at Flexmonster.DataServer.FlexmonsterPrepopulatingCacheService.<>c__DisplayClass4_0.<<Prepopulate>b__1>d.MoveNext()"
In version 2.9.0 loads succesfully.
Thanks.
⋅ December 9, 2021
Hello,
Thank you for reaching out to us.
We haven't managed to reproduce the issue on our end using the latest version of Flexmonster Data Server.
Starting from version 2.9.1, we switched to a different MySQL driver that is supported by .Net Core 5: https://mysqlconnector.net/connection-options/.
With this in mind, we suggest making sure that your connection string is in the supported driver's format.
Please let us know if this helps to resolve the issue.
Looking forward to your response.
Kind regards,
Vera
⋅ December 9, 2021
Hi,
We have 7 index with the same Connection String and only 1 index is loades successfully:
server=XXX.XXX.XXX.XXX;port=3306;user=root;password=XXXXX;database=AM_mando;default command timeout=180;convert zero datetime=True
We already check paremeters and seems be ok, and test connection is ok too. It's rare that one work and others don't.
Is there any way to see more information in the log?
Thanks.
⋅ December 9, 2021
Attach indexes status on Admin Panel
⋅ December 10, 2021
Hello,
Thank you for your reply and for providing further details.
Still, we haven't managed to reproduce the issue using the latest version of Flexmonster Data Server, so it is not entirely clear to us what could be causing the other indexes to fail.
Could you please try updating Flexmonster Data Server to the latest version and check if it helps to resolve the issue? It is possible that the issue was fixed in the latest version.
If updating to the latest version doesn't help, could you please provide us with the following details:
This will help our team to understand the situation better.
Waiting for your response.
Kind regards,
Vera
⋅ December 13, 2021
Hi,
We've already found the problem, the index fails when the select statement is on a view, on a table the index run successfully.
Any solution?
The DB version is: mysql Ver 15.1 Distrib 10.3.18-MariaDB, for Linux (x86_64) using readline 5.1
Thanks.
⋅ December 13, 2021
Hello,
Thank you for providing additional details.
We created a test view on our end and noticed that if you enclose the view name in the SELECT query with backtick quotes (`), the index loads successfully.
Could you please try surrounding your view names in the SELECT queries with backtick quotes (`) and let us know if this helps to resolve the issue? For example:
SELECT * FROM `AM_mando.v_fleximonster_espejo_ris`
Looking forward to your response.
Kind regards,
Vera
⋅ December 15, 2021
Hello,
Just checking in to see if the suggestion worked for you.
Could you please confirm if surrounding your view names in the SELECT queries with backtick quotes helped to resolve the issue?
Please let us know if everything works.
Waiting for your answer.
Kind regards,
Vera
⋅ January 12, 2022
Finally, we already found a solution, adding IgnorePrepare=True to the Connection String.
We hope this could help to other customers.
Thanks.
⋅ January 13, 2022
Hello,
Thank you for the update and for sharing your solution.
We are happy to hear that everything works.
As always, should any questions arise, feel free to reach out.
Kind regards,
Vera
