Hi all. I have an iFrame component set to act as a view to the web portal of my reporting software. It works fine in the designer, but not in Perspective Workstation, and I get the following error: OdbcException (0x80131937): ERROR [08004] [Microsoft][ODBC Microsoft Access Driver] Too many client tasks.
I called the reporting software's tech support and was on the phone with them for 2 hrs before they concluded that the issue was either with Ignition, my ODBC driver, or the database (MariaDB.) My database settings have remained the same from project to project and MariaDB client connection limitations are pretty high so I've ruled out the database.
I think the ODBC driver is the highest probability based on the error message but I've tried a number of things and am not getting anywhere. How does Ignition release client connections, whether as a whole or in the iFrame? Has anyone seen this before? Any ideas on how to resolve this issue?
Do you actually have an ODBC connection set up in Ignition? Where are you seeing these errors?
It sounds like these are errors your reporting software are generating when you try to access it in the iFrame, I don't really see how there's anything you can do on the Ignition side...
I suppose another good test to see if maybe it is/is not Ignition is to see what kind of errors you get when creating an html file and adding an iframe in that.
I would agree with @Kevin.Herron due to the fact your external system through the iframe is not going to have access to your ODBC in Ignition more than likely
Do you actually have an ODBC connection set up in Ignition? Where are you seeing these errors?
@Kevin.Herron No ODBC connections specific to Ignition. And again, this error only shows up when using iFrame with Workstation. In the designer, and even when I launch the perspective session via the browser actually, it works as intended.
I suppose another good test to see if maybe it is/is not Ignition is to see what kind of errors you get when creating an html file and adding an iframe in that.
@Benjamin_Furlani I just tried this and interestingly enough, when I try "http://neverssl.com" as the example site, it works, but when I try my reporting web portal, the page is blank. How would you interpret this?
The only likely difference between Workstation / Designer / Browser is the version of Chrome being used. Workstation in particular uses a somewhat outdated version of Chromium.
This makes me thing header problems with your reporting web portal. They may not allow IFrames based on their Content-Security-Policy or X-Frame-Options.
Based on you using neverssl I assume that your web portal is using https?
Based on you using neverssl I assume that your web portal is using https?
I actually just used neverssl since it was an example site in the forum post link I referenced in my original post. And I am using http for the report web portal
The plot just thickened. I was unable to resolve the above so I just thought of another test to try, this time not using the iFrame.
The goal was to test if URLs work differently in perspective workstation. I created two new links in my navigation menu, one with the target page URL https://google.com and the other as my reporting software's web portal URL.
Both links work fine when launching perspective as a client in my browser. But neither link works from perspective workstation. Any thoughts or ideas? Shouldn't web links work from perspective workstation if they work in a web-launched client?
Guess opening the web portal in a web browser is a functional option, so I'll call the case closed unless anyone has any other ideas. Still wish there was a way to embed an external web portal/URL in an iFrame, if any ideas, please share!
The answer, described in that linked topic is CORS. That is, the other site must cooperate with your desire to embed in an IFrame. If you are looking for ideas on breaking that, don't hold your breath while waiting.
Don't expect IA to support malware-ish behavior. (IFrames have a history of being leveraged by malware.)