TM1 Forum

This may have been brought up before, so forgive me if that is the case.

Looks like using RunProcess in a process executed by a scheduled or startup chore will crash the server. I'd run into this before and forgot about it, then it happened again when the same changes were made to use RunProcess in our chore processes. No error logs are written for the processes, but there are various entries in the server log as we ran tests:

IX conflict encountered during single threaded operation.
TM1.Lock Before image is NOT NULL Client, server is not stable
TM1.Object TM1ObjectImpl::AddUnregistered: Object NULL could not be added to owning client R*h2_sys.Cube.Dimension Usage Update

And just as likely as not, we would have no error, just a server crash. These errors were reported on separate crashes. So, fair warning.

Hi Pavoga,

I encountered this very issue last week and saw the exact same message in the server log.
I was going to raise an issue on the forum but thought I had used up enough of peoples time with RunProcess questions!

Maren

PavoGa wrote: ↑Wed Feb 26, 2020 4:10 pm This may have been brought up before, so forgive me if that is the case.

Looks like using RunProcess in a process executed by a scheduled or startup chore will crash the server.

For which version? You have two specified in your profile.

I have a bunch of scheduled chores which use RunProcess and I've not encountered this to date. (PA 2.0.6.)

Alan Kirk wrote: ↑Wed Feb 26, 2020 6:00 pm

PavoGa wrote: ↑Wed Feb 26, 2020 4:10 pm This may have been brought up before, so forgive me if that is the case.

Looks like using RunProcess in a process executed by a scheduled or startup chore will crash the server.

For which version? You have two specified in your profile.

I have a bunch of scheduled chores which use RunProcess and I've not encountered this to date. (PA 2.0.6.)

PA 2.0.5. It is repeatable. I should have mentioned this, but we are using CAM. I have no idea if that could be part or all of the problem; have not tested.

Another interesting observation: we use a process that records statistics for each process execution. We had just blanket converted everything to execute this with RunProcess. It would complete the first time it executed, then crash on the second call.

Bottom line was the only way to stop the crashing was to remove the RunProcess calls in processes called in scheduled or startup chores.

For future readers: This is a IBM bug (link to IBM APAR) for which there is a fix available in 2.0.8 and higher.