SSAS model loading ends in memory failure

jacccodezwart ok, If the msmdsrv.ini memory settings are identical, then we can probably rule out a simple misconfiguration. That means the issue on Server 2 is more likely tied to the environment rather than the model itself.

Here are the next things I’d look into:

NUMA & Hardware Layout

• Large memory servers often have multiple NUMA nodes, and the VertiPaq engine needs large contiguous memory blocks.

• On a machine with “too much” memory, allocations can fragment across NUMA nodes and fail even though plenty of memory is technically available.

Try starting SSAS with processor affinity limited to a single NUMA node.

• Start the SSAS service.

• Open Task Manager → Details tab.

• Find msmdsrv.exe, right-click → Set affinity.

• Choose CPUs belonging to only one NUMA node (e.g., CPUs 0-7 if your first node has 8 cores).

• Re-run processing.

BBF

💡 Did I answer your question? Mark my post as a solution!

👍 Kudos are appreciated

🔥 Proud to be a Super User!