IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 2 replies
  • Latest Post - ‏2013-11-22T15:32:04Z by andyzz411
andyzz411
andyzz411
19 Posts

Pinned topic msl has stopped with result 139.

‏2013-11-15T01:15:17Z |

Hi

When I am starting the WTX launcher in linux it automatically stopping with error code 139.Can some help what does that mean.I am not changing any settings .It working in DEV but not in UAT.

 

Thanks

  • Bhoju
    Bhoju
    37 Posts

    Re: msl has stopped with result 139.

    ‏2013-11-19T17:30:06Z  

    Did you check the lancher logs and compound system logs.. there is possibility you have a bad system file there.. which is without any trigger or not compiled properly.. try restarting launcher by keeping only one msl at a time in systems directory.. do this by brute force and you will find the faulty msl.. repair it and you are good to go....

  • andyzz411
    andyzz411
    19 Posts

    Re: msl has stopped with result 139.

    ‏2013-11-22T15:32:04Z  
    • Bhoju
    • ‏2013-11-19T17:30:06Z

    Did you check the lancher logs and compound system logs.. there is possibility you have a bad system file there.. which is without any trigger or not compiled properly.. try restarting launcher by keeping only one msl at a time in systems directory.. do this by brute force and you will find the faulty msl.. repair it and you are good to go....

    Thanks Boju

    Now it is working fine.Restarting launcher fixed the issue.