MSCM RAD - How do you monitor it?

 0 Replies
 0 Subscribed to this topic
 9 Subscribed to this forum
Sort:
Author
Messages
pcesarz
New Member
Posts: 1
New Member

    We continually end up with ‘hanging threads’ in our MSCM server; tasks stuck in the sync table with a status of 0; MSCM TASK9 table with a task ‘POTrackImporter’ that never want’s to go away, users changing passwords but not logging out causing pending issues/pars, printers not set up correctly or changed without warning. . . All of them seem to be preventing MSCM from talking to S3 so no delivery tickets for PO’s print.  The fix for any of these has been to restart the MSCM server, which then ends up causing downtime for the whole Lawson system.  This is happening almost on a daily basis – our receiving departments have been using PO30 more than they have been using RAD to do receipts.

     

    This is where I need the help.  I cannot imagine that everyone using RAD is having to restart their system on a daily, weekly, even monthly basis like we are.  Our downtimes are starting to outweigh our uptimes.  Do you see these issues?  If so, how do you handle them?  Are there files/logs you monitor?  If so, how often and what do you look for (some are huge). 

     

    We are hosted by Infor.  Any help would be appreciated.