This is pretty much why one builds a single update trigger program and a single delete trigger program. Then, from within those subroutines, call(s) are made to the actual subroutines that do something. This way, you can actually use "local" subroutines to do trigger work.


----- Original Message -----
*To:* U2 Users List <>
*Date:* 4/8/2014 8:45 AM
*Subject:* Re: [U2] [UV] Messing with file triggers and error 30107

If the program being called by the trigger is catalogued globally and that 
program was changed by an installation, you need to drop the trigger and re-add 
it otherwise it will fail when the trigger is called.

  From: Peter Cheney <>
To: U2 Users List <>
Sent: Tuesday, April 8, 2014 2:05 AM
Subject: [U2] [UV] Messing with file triggers and error 30107
Hi Everyone,

Just thought I'd post a solution to a recent problem to do with a file trigger 
that was driving me up the wall, across the ceiling and down the other side...

I'd made a mod to a particular file trigger to write to an item to a new file 
and all of a sudden the unirpcd started complaining with this error:

IBMU2.UODOTNET.UniSubroutineException: [IBM U2][UODOTNET - 
UNICLIENT][ErrorCode=30107] The subroutine failed to complete successfully
    at IBMU2.UODOTNET.UniSubroutine.Call()
 subroutineName, String[] arguments, Boolean logRequest, Boolean logResponse)

Searching around the usual haunts I found a few similar questions but nothing 
that answered my issue. Am still not entirely sure what other conditions this 
error 30107 covers but if you ever get this error then I recommend you check 
the file permissions of any newly created files that your code/modification is 
trying to write to.


Peter Cheney
Ultracs Developer
t 07 3017 8837 | f 07 3002 8400

This email (inc all attachments) is for the use of the intended recipient(s) 
Privileged or confidential information may be contained in this communication. 
If you have received this email in error, please notify the sender immediately 
and then delete all copies of this message from your computer network. If you 
are not the intended recipient, you must not keep, use, disclose, copy or 
distribute this email without the author's prior permission. If you are the 
intended recipient and you do not wish to receive similar electronic messages 
from us in future, then please respond to the sender to this effect.
We have taken precautions to minimise the risk of transmitting software 
viruses, but advise you to carry out your own virus checks on this email and 
its attachments. We do not accept liability for any loss or damage caused by 
software viruses and do not represent that this transmission is free from 
viruses or other defects.
Firstmac Limited (ABN 59 094 145 963) (AFSL 290600)
U2-Users mailing list
U2-Users mailing list

U2-Users mailing list

Reply via email to