We have created an IBOM dashboard that may return a few records or many, many records depending on where in the BOM the desired part is located. In our non-SSO environment we have no issues running any level of BOM.
When we run in SSO, small BOMs return data but the larger ones seem to time out. I can see it saying Retrieving Data… but then it goes back to Ready without anything returned.
I have compared the config files for both environments and they are identical (except for URLs).
I am having an issue trying to connect the Admin Console with the SSO version (it tells me “The client and server cannot communicate, because they do not possess a common algorithm”).
Is there a way to see the BAQ timeout settings without the console? Is there somewhere that there may be a different setting for SSO that is causing the timeout?
We are on 10.2.600.
This smells like a parameter sniffing issue, but before I get into that, I’m going to ask some basic housekeeping questions just to make sure I’m not assuming anything. (I know these are obvious but I just want to cover the obvious.
- You are connecting to the same database instance?
- You are using the same user for both test?
So while you answer that, what tools do you have available to you (personally, or with help in your company). Do you have direct SQL database access so that we can look at the database? Do you only have access the the BAQ editor? (we can work with either, but we can see more with database access).
Yes, we are connecting to the same database instance. Yes, we are using the same user (me and some other team members) for the tests.
I do have access directly to the SQL Server database. I also have access to the BAQ editor.
Do you know how to get query plan on a running query from the database while the query is running? (I use the toolkit from Brent Ozar BlitzWho). If we do that, we can look at see the actual query that’s being used and see if there is a difference.
I have not done this and I will take a look at it.
I am 99% sure this query is the same. SSO uses the same app server, SQL server instance and database, etc. The only difference is the way the user logs into Epicor. That is what makes me think there is some hidden timing setting somewhere.
I have finally found the answer to this issue. It turns out the query timeout settings in the SSO version of the web.config file did not match the non-SSO version. Once I changed them (now set to 3600) the long-running BAQs are now working.