TM1 Forum

Hi
I have scheduled one ti process to pull data from SAP system to TM1 through framework manager. But the problem is that SAP cube is also get refreshed at regular interval and if both the time matched with each other my server get crashed with following Error message:

14104 [461] DEBUG 2014-07-07 06:27:15.954 TM1.Cognos CCognosProxy::Connect C8Error: Failed to create pipe
14104 [461] DEBUG 2014-07-07 06:27:15.954 TM1.Cognos CCognosProxy Connected
14104 [461] ERROR 2014-07-07 06:27:15.955 TM1.Process Process "Loading SalesVolume for TB_division": : Execution was aborted. Error file: <TM1ProcessError_20140707062715_Loading SalesVolume for TB_division.log>
14104 [461] ERROR 2014-07-07 06:27:15.957 TM1.Process Process "Loading SalesVolume for TB": : Execution was aborted. Error file: <TM1ProcessError_20140707062715_Loading SalesVolume for TB.log>
14104 [461] ERROR 2014-07-07 06:27:15.958 TM1.Process Process "2.1.0.Load_TB": finished executing with errors. Error file: <TM1ProcessError_20140707062715_2.1.0.Load_TB.log>

What is shown in your error files "Error file: <TM1ProcessError_20140707062715_Loading SalesVolume for TB.log>"?

I am presuming you have just got your terminology confused in that the TM1 Server itself does not crash, but the TI Process fails due to a failire to connect to your SAP datasource as SAP is in the process of updating its own tables.

If my assumption is correct then you possibly have 3 solutions.
(1)
You could see if there is a Flag in SAP somewhere which states whether the SAP data has been refreshed, and only execute your TI if that is set, and if it is not report it so that it can be ran manually by an admin.
(2)
As part of the SAP Routine that updates your datasource (if it is a scheduled event) you could possibly see if you get SAP to execute the TI utilising the TM1RunTI.exe after it has refreshed the datasource.
(3)
Leave plenty of time between when you expect SAP to complete process and when the TI is scheduled to Run.

It sounds like a bug. Any messages related to pipes means that the TM1 Package Connector process spawned by TM1 either didn't start or quit unexpectedly.
(They communicate with each other via a pipe.)

Contact support.