What does "integer limit" actually mean? I found only one (rather old!) related Knowledge Base entry, S-062259, but it doesn't help.
I have a similar problem with an apparently even simpler simulation -- only bonded contacts, three parts, 713090 nodes, 496334 elements (primarily a result of needed mesh controls on four surfaces). Currently running SW Premium 2016 SP3.0 (64-bit on a similar Windows 7 SP1 machine, also with 32GB memory and plenty of available disk space). The error message I get is:
"The solver is currently running out of integer limit. It is recommended that you change the solver from Direct Sparse to Large Problem Direct Sparse (see the study properties).
Would you like to change the solver to Large Problem Direct Sparse now?"
At the time of the error the solver screen looked like this:
I never saw more than about 2 GB of memory usage. The simulation does run (and quickly) with the Iterative solver, but I suspected the results and wanted to compare with the Direct Sparse solver.
Should I go back (with considerable difficulty!) and try running the problem in SW2015? -- John Willett
OK, I think I found the problem, in my case at least. I can get the Direct Sparse simulation to run if I decrease the resolution of the aforementioned mesh-control resolution slightly. The memory usage now maxes out (during the "Decomposition of stiffness matrix" phase, which I never got to before) around 17 GB, which from past experience is pushing my limits. I guess it really was a memory problem after all...