[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::mailbus_400

Title:MAILBUS 400 User Forum
Notice:kits 100-109 - Infocenter //www.digital.com/info/messaging
Moderator:IOSG::MARSHALL
Created:Thu Jun 11 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3210
Total number of notes:9174

3150.0. "Process XMR$MRTOX400MSG loop, "WRONG_VALUE_MAKEUP"" by EVTAI1::GODARD () Fri Mar 14 1997 10:13

    A customer encountered the following problem with XMR V1.2-002
    
    The process XMR$MRTOX400(MSG) in COM state (100%CPU) was looping when
    processing a message (1997030714255079_cnt1.nbs).
    The customer had to stop and restart the gateway XMR ( the process was
    looping from 2h30!)
    
    This is the LOG 
    
    7-MAR-1997 14:20:41.83  %XMR-I-MRENVSTART, Starting Envelope Processing
     7-MAR-1997 14:25:43.78  %XMR-I-MRENVSTART, Starting Envelope
    Processing
     7-MAR-1997 14:25:51.57  %XMR-I-MRENVSTART, Starting Envelope
    Processing
     7-MAR-1997 14:25:52.37  %XMR-E-OMCANTPUT, Can't put item
    IM_USER_RELATIVE_IDENTIFIER
     7-MAR-1997 14:25:52.47  -XMR-E-MTAAPIERROR, MTA API returned
    "WRONG_VALUE_MAKEUP"
     7-MAR-1997 14:25:52.56  %XMR-E-X400CRIPMID, Cannot put X.400 IPM
    Identifier
     7-MAR-1997 14:25:52.66  -XMR-E-MTAAPIFAIL, Problem with MTA API
    
    ====> RESTART the GATEWAY ***********************
    
    7-MAR-1997 17:17:59.68  %XMR-I-VERSION, MAILbus 400 Message Router
    Gateway V1.2-2
     7-MAR-1997 17:18:17.92  %XMR-I-MTACONNECT, Connected to X.400 MTA on
    OSITP:MTA_CLIENT_CLNS%49000FAA0004005C3C21
     7-MAR-1997 17:18:20.19  %XMR-I-MRENVSTART, Starting Envelope
    Processing
     7-MAR-1997 17:18:21.01  %XMR-E-OMCANTPUT, Can't put item
    IM_USER_RELATIVE_IDENTIFIER
     7-MAR-1997 17:18:21.10  -XMR-E-MTAAPIERROR, MTA API returned
    "WRONG_VALUE_MAKEUP"
     7-MAR-1997 17:18:21.20  %XMR-E-X400CRIPMID, Cannot put X.400 IPM
    Identifier
     7-MAR-1997 17:18:21.30  -XMR-E-MTAAPIFAIL, Problem with MTA API
     7-MAR-1997 17:18:23.10  %XMR-I-MRENVSTART, Starting Envelope
    Processing
     7-MAR-1997 17:18:25.77  %XMR-E-OMCANTCREATE, Can't create object
    MH_C_MESSAGE
     7-MAR-1997 17:18:25.92  -XMR-E-MTAAPIERROR, MTA API returned
    "NO_SUCH_OBJECT"
     7-MAR-1997 17:18:26.01  %XMR-E-MRERROR, Error processing Message
    Router
    Message
     7-MAR-1997 17:18:26.11  -XMR-E-MTAAPIFAIL, Problem with MTA API
     7-MAR-1997 17:19:23.96  %XMR-I-VERSION, MAILbus 400 Message Router
    Gateway V1.2-2
     7-MAR-1997 17:19:25.42  %XMR-I-MTACONNECT, Connected to X.400 MTA on
    OSITP:MTA_CLIENT_CLNS%49000FAA0004005C3C21
     7-MAR-1997 17:19:27.84  %XMR-I-MRENVSTART, Starting Envelope
    Processing
     7-MAR-1997 17:19:30.16  %XMR-I-MRENVSTART, Starting Envelope
    Processing
     7-MAR-1997 17:19:32.24  %XMR-I-MRENVSTART, Starting Envelope
    Processing
     7-MAR-1997 17:19:34.50  %XMR-I-MRENVSTART, Starting Envelope
    Processing
    
    The customer has the dump of the .NBS file but the informations are
    confidentials...SO I can't put them here
    
    There are no messages in XMR$BAD_MSGS
    
    Have you any ideas on this problem which become critical...
    
    Thanks for help
    Monique GODARD
T.RTitleUserPersonal
Name
DateLines
3150.1IPMTZUR01::ASHGGrahame Ash @RLEFri Mar 14 1997 12:2222
This is clearly a bug, so you should enter an IPMT.

>     7-MAR-1997 14:25:52.37  %XMR-E-OMCANTPUT, Can't put item
>    IM_USER_RELATIVE_IDENTIFIER
>     7-MAR-1997 14:25:52.47  -XMR-E-MTAAPIERROR, MTA API returned
>    "WRONG_VALUE_MAKEUP"
>     7-MAR-1997 14:25:52.56  %XMR-E-X400CRIPMID, Cannot put X.400 IPM
>    Identifier

This item IM_USER_RELATIVE_IDENTIFIER comes from the MRIF IDENTIFIER field in 
the APP_MESSAGE_ID, which you should be able to see if you dump the NBS. The
API is saying there is an invalid character in it. I think this is supposed to
be an IA5 string. 

These strings are usually generated automatically by the sending User Agent. 
You don't say what that is, but perhaps you can configure something to get it 
changed.

Alternatively, the sending user may have generated it - perhaps there are 
accented characters in the Subject field?

grahame