[Christopher Wells]

Charlie,

I know this is an old post, but the file writing snippet really helped me out.  Just starting to work with decoded PDF files myself.

Thanks,

Christopher Wells

[Christopher Wells]

Thanks for posting the template procs.

Christopher Wells

[Christopher Wells]

With info from another thread, I was able to solve the issue.  I am leaving this thread here and posting my solution to make it easier for others to find the solution to this particular error:

           set msgData [msgget $mh]

           # Kill original message:

           lappend dispList “KILL $mh”

…

           # create new OB message

            set mh2 [msgcopy $mh]

            msgmetaset $mh2 DESTCONN $destConn  

            msgset $mh2 $outboundMsg

            lappend dispList “CONTINUE $mh2”

I have not experienced the error since making these changes.

Regards.

Christopher Wells

[Christopher Wells]

Thanks for posting this solution.  It helped me out with a coding issue I was having when creating multiple OB messages from one IB. I was getting an ‘Invalid MSI index -1’ error.  Bottom line, I was not killing the original message.

Christopher Wells

[Christopher Wells]

Thanks for the input.  We have already opened a ticket, but it does not sound like we have made it as far along as you.  Our ticket is Incident 9342532.  If you will give me your ticket number, I’ll post it to our incident.  Perhaps if we cross-reference our incidents it will get more attention.

Regards,

Christopher Wells

[Christopher Wells]

Peter,

Have you opened up a ticket with Infor support on this yet?  We’re planning to upgrade to 6.0 soon and are VERY interested to avoid this issue ourselves.  

Also, for both of you, what platform/OS version are you running on?

Thanks for the information,

Christopher Wells

[Christopher Wells]

Thanks for mentioning the attachment didn’t post properly.  I’ve updated the original post.

Christopher Wells

[Christopher Wells]

Daniel,

Just noticed your reply.  Sorry for the late response.  It turned out to be a malfunction of the monitor daemon that was setting off the alert erroneously.  Bouncing the monitor daemon fixed it.

Thanks,

Christopher.

Christopher Wells

[Christopher Wells]

Thanks Troy, this is just the info I needed. Very helpful. 🙂

Regards,

Christopher Wells

[Author]

Replies