LAW1143 (4/19/2016)
it processes via an ssis task that I am admittedly not intimately familiar with.another note, we are seeing memory starvation on the OS at the time of it processing.
Weve lowered the HardMemoryLimit from 95 to 91 and this still fails. Suspect its related to SSAS consuming memory, starving the OS and causing failure.
I failed to mention, this is on windows 2008R2 server and sql2008r2 sp3, enterprise edition.
I'd definitely recommend that you look into the SSIS processing task first, and split it out to process on a more granular level.
The memory pressure you're seeing can also be a contributing factor, and changing the memory limit will not necessarily fix it if the available memory is already too little for the task it needs to perform. You may need to run a profiler trace while processing to capture any warnings and messages from SSAS.