I have 2 users running CAESAR II v4.50.050407 on W2k SP4, and MS Word 2003/SP2. On certain projects, when they run an Output Displacement Report, MS Word will lock up with the cursor at the "Table of Contents" header. When this happens Winword.exe utilizes 100% of CPU process time, and I must kill this process in order to recover. They can then close the report module, and will get an Outp02.exe - Application Error, memory could not be "read".

I have removed Caesar and MSOffice and reistalled, and re-registered Outword.dll. They are not using customized Header.doc files.

They have also copied to input files to a local drive and reprocessed output files, but when they try to run the report Winword.exe still locks up.

Hello, I have the same CAESAR II, Windows and Office versions and we have faced exactly the same problem, I tried to increase the 'Memory Allocated' value in the configuration setup panel but it was unsuccesfull...

You have asked "MS Word" to do too much work, for the hardware you're on, and "Word" is thrashing.

We've seen this occasionally here, and if you "wait it out", it usually finishes.

Two weeks a go a user with CAESAR II 5.00 and Office 2003 reported the same issue, attempting to generate a 300 page ".doc" file. His IT group moved him from a 1.9 Ghz machine to a 3.2 Ghz machine with triple the memory. He called back ecstatic about how well (and fast) the "Word" export worked.

If you can't throw more resources at it, then request the reports one at a time (sending them to the same ".doc" file).

I was able to find a workaround for this problem. One of the projects was very small, and the end user was able to recreate the input information and run the analysis again. At that point he was able to run the output report.

The second analysis was too large to re-input the information. So I was able to run the report on a PC with more resources. The failed PC was a 2.8Ghz CPU with 512Meg RAM. The PC that successfully generated the report was a 3.2GHZ CPU with 2Gig RAM.

You should not have had to recreate anything. All you needed to do was go back to "output".

So, "MS Word" needs a lot of memory. How big (in number of pages) was the report?

Richard, we have tried to generate only displacement reports as you suggested (one at a time) and the program hangs at the first case.

I do not think the problem is the size of the job because it is not a big report (almost 40 pages) and we have processed much bigger reports before, in fact I have installed CAESAR II in other PC with earlier version of MS Word and the report does works.

What exact version/build of CAESAR II are you using?

Can you generate the report on that 3.2 GHz machine with 2 Gbytes of RAM?