About 50% of the time when I run an analysis, I recieve a Windows error. The detailed text of the error is below:

Problem signature:
Problem Event Name: APPCRASH
Application Name: OUTP01.EXE
Application Version: 6.1.2.200
Application Timestamp: 52740898
Fault Module Name: libifcoremd.dll
Fault Module Version: 10.1.105.105
Fault Module Timestamp: 47d8944c
Exception Code: c0000005
Exception Offset: 00082d80
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Also, everytime I open a model now a small box with a red circle and white X pops-up. The warning text in the box border at the top says "Could not open TEMPM...". I click ok and the model usually opens, but sometimes I have to restart Caesar altogether. There are instructions on how to fix the TempMat problem from previous versions (open configuration, save, restart Caesar and re-open model) but this hasn't fixed the problem.

While typing out this text and working concurrently, I recieved a new error when running an analysis:

The program has encountered an unrecoverable error.
The error number is: 6007

All of these errors do not seem catastrophic as I'm eventually able to resume my work afterward, but it does make me wonder how they may affect my results.

Thank you,
Dmitriy

OUTP01.exe should not be crashing, but the information above doesn't help explain why it is for you. Here are a couple of things to try to narrow down the problem.

1) Make sure none of the files associated with the job name are "read only". You may have to turn this flag on in Windows Explorer to see this, but it is worth checking.

2) Does the problem only happen with one job? If so, open a Support Request and send in that job.

3)If you switch data directories, does the problem still occur? If not, then maybe there is something special about that one path-name. Let us know what that path-name is and we can try to reproduce the problem.


TEMPMAT is a temporary file extracted from your model each time you enter the input. Upon exiting the input the TEMPMAT file is supposed to be deleted. Close CAESAR II and try to delete TEMPMAT yourself.

HI
What About error 740 ?
thank's

bye
Paolo

Verify your spectrum data. Make sure you don't have two entries at exactly the same frequency (period). If you can't resolve the issue, open a Support Request on Smart Support and send in your job files.

Dear Richard,

In my company, many of us are having the same problem as Dmitriy. CAESAR 6.1.2.200. Considering all your comments:

1) We have checked that all the files and the folders are not "read only".

2) It happens in different computers with different calculation and in different folders.

3) Closing the CAESAR input, the TEMPMAT file is auto-deleted.

Hope you can help us, Thank you,

Pablo

Pablo,

From your item #3, I conclude you don't have a problem with TEMPMAT. That doesnt' help or narrow things down. Open a Support Request on Smart Support so they can log-on to your machine and chase this down.

Thank you Richard. Support request opened.

My team members(include me) have encounterd same error.
we are using both CAESAR II 5.3(SP2) and 6, but when we click batch run or start run, it crahses 2 of 5 times.
Is this issue solved recently?

I had a citrix connection with India and Spain (for CAESAR 6), and recieved no solution. Only concluded that we must run CAESAR as administrator, in a short folder (C:\folder) with no extrange symbols.

It is not a solution for this problem, still crashing.

Saving current staus also giving me same problem. Window application stopped and CAESAR II will be closed.
Suppose it is the main problem since both batch and start run save before starting the analysis.

With Caesar 6.10 I have a silly problem but I don't know how to switch this option; I have the node numbers too huge that when I zoom back these nodes override one on the other. Can I solve it?

1,2,3

Thank you very much Dave

I'm also getting error 740? It seems to occur when I increase the fatigue cycles beyond a certain number of cycles? I've increased the memory allocation but that doesnt make any difference. The error occurs whilst OUTP01.exe is running. Thanks

Anyone got any insight on this error 740? I can run low cycle fatigue checks but when I increase the number of cycles I get an OUTP01 error, "The program has encountered an unrecoverable error. The error number is: 740". Thanks

We can't solve this issue here in the Forum. Please open a Support Request (SR) on Smart Support and send in your job files.