“try the following”
Yeah, let’s experiment with production settings without knowing for sure what other impacts it might have.

“try the following”
Yeah, let’s experiment with production settings without knowing for sure what other impacts it might have.

SAAS , Cloud Customer part of the last Flex Option 2 group to be pushed over the cliff last weekend ..
Having ALL the custom Invoices built off of ArForm RDD broken by the migration hurt the most … Month End Closing ..
Sharing steps that greatly increased the responsiveness of painting forms with data and getting records to show up :
Used CMP to restart the Instance and then the Site.
Performed twice 1st and 2nd day after 2026.1 migration after hours. Each time completed faster and made a noticeable difference in performance.
still dealing w issues never imagined would be brought up by the migration. each day gets a little better. Browser cache turning out to be a large obstacle getting app changes to sync to user experience..
best wishes to all affected ..
I mean I looked at the documentation and it was pretty explicit, the CB is only used to populate data for the AR Reconciliation Report, of which we don’t use. And if you disable the CB, there is a process to run manually prior to running the AR Reconciliation Report.
That being said, we are full of errors today (18 since 8am). Just a coincidence that we only had 1 error yesterday.
No rhyme or reason, just random acts of unkindness…phooey.
I’ve had the same issues with upgrades, I have created a Claude agent for SSRS,BAQ & BPMs and an MCP connection with Epicor. no more sorrow with SSRS.I just point Claude to the location of the SSRS and Claude was able to fix the issues and do all the adjustments using simple prompts.
My case was transferred to a different support person on Friday, 10/30 and their suggestion was for me to run Conversion 430 - DeployReportsToSSRSServer. I had to wait until yesterday to verify improvement and so far we have not seen any of the “An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database” error.![]()