TM1.Process myprocess: Could not initialize process"???

[shockwave]

Hi Guys,

when i chore this process which points to an ODBC connection, the process will not execute. I get the following error:
"TM1.Process Process "switch - chore daily load": Could not initialize process"

Is this because the process that i am trying to execute is ODBC? When i run a simple TI process which does not involve ODBC the process runs fine.
Is there a way around this or a better way of picking up errors. Esentially i would like the process to spit out a text file which indicates whether it
was executed sucessfully ( need it for sox purposes)



##################################


ReturnValue=ExecuteProcess('switch4_switch data obbc');


if(ReturnValue=ProcessExitNormal());
AsciiOutput('E:\TM1_Production\Logging_Sox\switch4_switch data obbc_successfull_'|TODAY|'_'|TIMST(now(),'\hhrs\imin\ssec')|'.txt','switch4_switch
data obbc Process has been updated sucessfully - Process_'|TODAY|'_'|TIME);
Elseif (ReturnValue=ProcessExitMinorError());
AsciiOutput('E:\TM1_Production\Logging_Sox\switch4_switch data obbc_minorError_'|TODAY|'_'|TIMST(now(),'\hhrs\imin\ssec')|'.txt','switch4_switch
data obbc Process has been updated but with minor errors - switch4_switch data obbc Process_'|TODAY|'_'|TIME);
Elseif (ReturnValue=ProcessExitSeriousError());
AsciiOutput('E:\TM1_Production\Logging_Sox\switch4_switch data obbc_majorError_'|TODAY|'_'|TIMST(now(),'\hhrs\imin\ssec')|'.txt','switch4_switch
data obbc Process has been updated but with major errors - switch4_switch data obbc Process_'|TODAY|'_'|TIME);
Elseif (ReturnValue=ProcessExitOnInit());
AsciiOutput('E:\TM1_Production\Logging_Sox\switch4_switch data obbc_ExitOnInitError_'|TODAY|'_'|TIMST(now(),'\hhrs\imin\ssec')|'.txt','switch4_sw
itch
data obbc Process has been aborted due to ExitOnInit - switch4_switch data obbc Process_'|TODAY|'_'|TIME);
Endif;



########################################

Cheers

Shock

[LoadzaGrunt]

The error that you are encountering sometimes happens because you call a process with ExecuteProcess but do not correctly specify the parameters that should be passed through. You need to explicity state every parameter and its value even if you are passing blanks through. E.g.

Code: Select all

ExecuteProcess('YOUR_PROCESS_BEING_CALLED','Param1',SOME_PARAMETER,'Param2','');

Or perhaps your ODBC credentials are incorrect, or the data source query is failing. Have you tried to run the process being called in isolation of the calling process ?

[shockwave]

Hi LoadzaGrunt,

The query works fine in isolation, it only appears to fall over when i call it, and it only seems to happen if it accessing ODBC in my case. I have created a simple process to output an asciioutput using the same code and it works fine. For what ever reason it doesn't like that fact that I am trying to retireve data from an ODBC source.

I have no parameters set up in my process, and when i set this up for another one of my processes it worked fine even through I did not pass any parameters. Are you saying that i need to pass parameters since because Its linked to an ODBC connection?? since the documentation says the following:

ParamName The name of an existing parameter of the process to be executed. This argument is required only if the process to be executed uses parameters.
ParamValue A valid value for the ParamName parameter. If you specify a ParamName argument, you must specify a corresponding ParamValue.

Could there be another reason why this is not working????

Cheers

Shock

[Steve Rowe]

Hi Shock,
Just checking should

ReturnValue=ExecuteProcess('switch4_switch data obbc');

be

ReturnValue=ExecuteProcess('switch4_switch data odbc');

I don't think it's anything to do with odbc, it's the call to the TI that is the issue.

Cheers

[Michel Zijlema]

Hi Shock,

I think this is an authentication problem. If you are executing the process directly I think the (Windows) user you're running on is used to log in to the RDBMS, while when the chore triggers the process the (Windows) user the TM1 Service runs on is used to login on the RDBMS.
Probably the latter user doesn't have the proper access rights.

Michel

[shockwave]

Thanks Steve, i think thats going to do the trick...