Hello,
We’ve recently activated an additional processing node in our instance, but every generic inquiry I try to run shows this error if the results have more than 1000 records. I tried running the same GI’s in the original node, and they work just fine.
The biggest reason we wanted to have this additional node was for running larger reports/GI’s and being able to export them without taking processing power away from the rest of the work.
Any ideas why this is happening?
Best answer by bryanb39
Is this SAAS or PCS? What's the hardware specs of the processing node vs main?
The SQL server would be shared, so seems unlikely to be SQL related.
Do you have access to the webconfig files to compare? Dumping them both in ChatGPT would spit out the differences. Wonder if there's a timeout?
+19
However, I don’t know if any of that helps with my specific issue.
With this new processing node, every GI returns this error. And it doesn’t have any problems pulling all records and aggregates in the original node.
Even for a super simple generic inquiry with 429 records, it is unable to get a record count and actually takes a long time to run.
Is there possibly something that needs to be adjusted with the new processing node?
+6Is this SAAS or PCS? What's the hardware specs of the processing node vs main?
The SQL server would be shared, so seems unlikely to be SQL related.
Do you have access to the webconfig files to compare? Dumping them both in ChatGPT would spit out the differences. Wonder if there's a timeout?
It’s SAAS.
I don’t have access to the web config, but I can ask about that with our VAR.
It was very recently set up, so I didn’t know if I was missing a step before it could run effectively.
Thanks!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
