Hello,
I'm having a problem with the dm_noop_auto_method. After lots of testing I don't think it's the method itself, but maybe something to do with the workflow. I'm not an expert on workflows, I'm really just learning this part of Documentum, but in some cases, we launch a workflow into a state that does nothing, just to advance it to a second state. So the nothing state has its' exec_method_id set to the id of dm_noop_auto_method. Although the log says this:
FD7000101-2-3-001TRACE LAUNCH: ./dmbasic -eEntry_Point -f/apps/dcm/share/data/common/0000498d/80/00/00/0b/0600498d80d8ee5a75fb2c8f.txt -- -docbase_name TCMUAT2 -user "dmadmin" -packageId 4a00498d81a54e3f -ticket DM_TICKET=<ticket here> -mode 0
dmExec::ForkLaunch() system(./dmbasic -eEntry_Point -f/apps/dcm/share/data/common/0000498d/80/00/00/0b/0600498d80d8ee5a75fb2c8f.txt -- -docbase_name TCMUAT2 -user "dmadmin" -packageId 4a00498d81a54e3f -ticket DM_TICKET=<ticket here> -mode 0 )
dmExec::ForkLaunch() returns: 25600, errno: 9
dmExec::ForkLaunch() returning value: 100
dmUnderTaker: waitpid() results:
Pid: 6856956
Errno: 0
DeathByExit: 1
ExitVal: 100
DeathByStop: 0
StopVal: -1
DeathBySignal: 0
SigVal: -1
[DM_WORKFLOW_E_AGENT_LAUNCH]error: "Failed to launch 4a00498d81a54e3f due to an operating system error: No Error Message Available."
So what I've really noticed seems wrong here is this "0600498d80d8ee5a75fb2c8f.txt". Not quite a normal object id. This file does exist though, 0600498d80d8ee5a.txt and contains some basic code with the function Entry_Point.
I also tried creating a Java method that does the same thing the basic method does and pointing the activity to that. When I did that I just get this error:
[DM_WORKFLOW_E_AGENT_LAUNCH]error: "Failed to launch 4a00498d81a54e3f due to an operating system error: No Error Message Available."
At this point I don't really have any other ideas. Any help with this would be greatly appreciated.