Documentation Generation using PCS leads to crash

[philipp.k]

Hi together,
our SysML model is accessed via PCS, it is a Firebird model.
For documentation generation we set up a dedicated model in the root, consisting out of a "Report Package" element, which contains several "Model Document" elements. Those "Model Document" elements we assigned the package(s) to report on and our RTFTemplates to use for.

The problem is, when executing this documentation generation on the "Report Package" (with F8 key) it now leads to a crash on the server.
Result is, that EA freezes and the PCS service "Sparx Systems Professional Cloud" was stopped somehow and is not running any longer. It needs to be restarted by hand.
Log files report only "2023-11-07 07:42:44 [FATAL]: --------------------------------------"

Same documentation generation was running without problems, when executing it on a local *.qea repository.

Has anyone observed issues like that and know what to do?

[Modesto Vega]

Hi Philipp,

I recommend opening a support case for this. In any case, what version of PCS and Sparx EA are you running? Are you running 32-bit or 64-bit? Is there any additional information in the log after the [FATAL] line (not that I expect more information)? Have you changed PCS logging setting to Debug (it does provide more information)?

[philipp.k]

Hi Modesto,
well I found my workaround (this is also the reason for not anwering so long time, sorry about that)

My workaround is to:
- keep packages small for those documentation is running over
- if the error is showing up, I export the model from the server and import it in a local file

--> If there is no cloud connection, documentation is working fine.

Greetings, Philipp

[Geert Bellekens]

There are still a few cases in which PCS connections don't really work.

I would suggest to use a direct database connection for these cases. (if you can get that approved by your infra team)

Geert