'Out of Memory' Error message

When using the NEMA analysis tool and trying to import loads from the current Caesar model, I'm receiving an 'Out of memory' error message. There are 181 load cases in the standard model and I assumed it may have been due to limitations with the NEMA analysis tool, but even after removing the vast majority of load cases for a test file and re-running I still received the same error message. Most of the NEMA analysis has been done using Excel but I simply wanted to use the Caesar NEMA tool to verify my spreadsheet.
Is there an easy fix for this?
Caesar II 2014 model is 7.00.01.16000, (Build 141003). We cannot update to later builds due to project requirements.
Thanks in advance

Have you tried allocating more RAM to c2 (in the Configuration)?

Currently using 1024 Mb

Tried using some of the other design modules (e.g. API 617, API 661 and WRC 107) and I get the same error message

1024 is way too much to allocate - so RAM isn't the problem. Open a Support Request on Smart Support and turn this over to the Support Group.

Managed to fix it but a complete uninstall / reinstall was required

Is there a solution without uninstall/reinstall? I am getting the same error.

I'm really stunned here. In general, uninstalling and reinstalling does nothing. Richard - can you open a Support Request and send in the job files needed to reproduce this problem? I'd really like to get to the bottom of this.

Hi. Have you found any solution for this issue? We have same issue.

No, because we cannot reproduce this issue here. We need someone experiencing this problem to submit the necessary job files (via Smart Support) so we can reproduce the problem and resolve it.

Dredging this up from the past... What I can say is that I have 2 versions of CAESAR loaded... 2017 (build 160721) and 2014, and the experience is the same between the two, across all CAESAR files. Whenever I get to the point to select a CAESAR (or _P) file to pull loads from, I get an Out of Memory error.

Unfortunately, I cannot pinpoint a specific action that resulted in CAESAR to start acting this way.

All I can guess is that there's some registry setting or temporary files that gets removed if you un-install, and then gets reset to default when you install it, but doesn't get over-written if you install on top of the last CAESAR install.

I've attached an example file, but I'm doubtful it'll reveal anything.

Michael,

I just downloaded and ran your job (in c2 2017, build 170419). I experienced no issues. The (API-610) loads imported just fine from the static output file. (I have the default 32 MB of Ram allocated to c2.)

Here is the .610 data file with the imported loads.

(If you're going to continue running this version, you should visit Smart Support and download the latest Service Pack. This Service Pack will NOT affect this issue, but you will have everything we did adjust in this version of the software.)

If the file is very large then, there may be an issue with zipping. Why don't you set the option to not zip your file back to the ".c 2" archive (in the config) and then try to import the loads again.

Mandeep,

It's all files, regardless of size. The test file attached consists of 5 elements.

Richard,

I will request a re-install from our IT, and I will make the request for the service pack, as well.

Both,

One thought I did have is at some point (after installing CAESAR) my machine did get an upgrade to RAM. Perhaps that has something to do with it.

Thanks.

Michael,

I'm reasonably sure your issue is not a memory problem with c2 - your model is too small. If there was a flagrant memory bug in the software we would be seeing a great number of these issues, and we are not.

Can you try this same job on a different computer? Also, what virus scanner are you using (we have had an issue or two with certain ones)?

I can confirm with another analyst that he has the same problem. We use Sophos Endpoint.

I will report back on the results of the un/reinstallation and (if needed) finagling with the virus protection.

Rats - I was hoping you were not going to come back with Sophos. We have various issues with this virus scanner.

Uninstall/reinstall will not resolve this problem.

If you have not filed an SR on this issue please do so, so that this issue can be properly tracked.

As a wild guess, in the Configuration (Miscellaneous pane), turn off file compression. Maybe that is panicking Sophos (again, I'm guessing here).