<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: SM66 - Work Process Failures in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391883#M4229666</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could also reset the trace files (SM50 -&amp;gt; Administration -&amp;gt; Trace -&amp;gt; Reset -&amp;gt; work processes).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The next time you see a failure, open the corresponding trace file and search for " pid&amp;nbsp;&amp;nbsp; ".&lt;/P&gt;&lt;P&gt;Each failure means that the work process has restarted.&lt;/P&gt;&lt;P&gt;At each restart, the work process PID will change, and the work process will log the initial header at the trace again (that initial part that shows the system ID, kernel version, the PID, ...).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you locate the second occurrence of the PID (the first one would be the PID from before the new failure), copy the trace entries from around 100 lines up until around 100 lines down (from the line of the second PID) and attach it to this thread.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notice that the failure that occurred at one work process might not be the same that occurred at all of them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Isaías&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Jan 2016 10:15:43 GMT</pubDate>
    <dc:creator>Isaias_SAP</dc:creator>
    <dc:date>2016-01-26T10:15:43Z</dc:date>
    <item>
      <title>SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaq-p/11391861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just noticed the following on transaction SM66:&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/837990" width="450" /&gt;&lt;/P&gt;&lt;P&gt;The system is running fine. Looking in SM21 nothing seems to appear for the&lt;/P&gt;&lt;P&gt;same Process ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this something to worry about? How can I clear them down?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I went into SM50 and then restart process after error but it still stays highlighted in &lt;SPAN style="color: #ff0000;"&gt;red&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas anyone?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 13:37:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaq-p/11391861</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T13:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391862#M4229645</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your SM66 screen shot is telling you that the &amp;lt;nn&amp;gt; WP have restarted &amp;lt;nn&amp;gt; times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie: The WP with PID 29906 has had 181 failures (restarts) but is currently in status WAITING (waiting for work).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you need to check is the developer trace associated with the WP (SM50) and see from within the dev trace what errors are being logged.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps you a wee bit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;KR,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amerjit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 14:12:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391862#M4229645</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T14:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391863#M4229646</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are seeing no errors in the system log or WP logs, then you may find at the WPs are set to restart periodically - it's a profile parameter which sets this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Graham&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 14:14:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391863#M4229646</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T14:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391864#M4229647</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Graham,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply. Would you happen to know the profile parameter so I can&lt;/P&gt;&lt;P&gt;check this out?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 14:21:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391864#M4229647</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T14:21:56Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391865#M4229648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for replying Amerjit, very useful info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 14:22:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391865#M4229648</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T14:22:35Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391866#M4229649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try this note: &lt;A href="http://service.sap.com/sap/support/notes/1709928" title="http://service.sap.com/sap/support/notes/1709928"&gt;http://service.sap.com/sap/support/notes/1709928&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Graham&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 14:28:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391866#M4229649</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T14:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391867#M4229650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good man, thanks Graham &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro_emoticon jive_macro jive_emote" src="https://community.sap.com/1382/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 14:32:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391867#M4229650</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T14:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391868#M4229651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Graham,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can see where you're coming from with your initial remark and probably by the screen shot with the number of failures across all WP being almost identical.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That said, the WP autorestart wouldn't (shouldn't) show up in the error count of a WP. You'd just see in the dev trace that the autorestart time had been reached and the WP would restart.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a test system, check it out by setting it to a silly value like 60s.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amerjit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 15:38:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391868#M4229651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T15:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391869#M4229652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You're welcome. Could you do two things for us.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Post a screen shot of tx ST02.&lt;/P&gt;&lt;P&gt;2. Upload one of the developer trace files. eg: dev_w0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you also check tx ST22 to see if you're getting any short dumps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amerjit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 15:40:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391869#M4229652</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-25T15:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391870#M4229653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The profile parameter for auto-restart (rdisp/wp_auto_restart) does &lt;SPAN style="text-decoration: underline;"&gt;not&lt;/SPAN&gt; increase that counter.&lt;/P&gt;&lt;P&gt;Those are unexpected restarts (e.g., crashes?).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2015 16:53:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391870#M4229653</guid>
      <dc:creator>Isaias_SAP</dc:creator>
      <dc:date>2015-11-25T16:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391871#M4229654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Amerjit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here we go:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/838920" width="450" /&gt;&lt;/P&gt;&lt;P&gt;There are no short dumps in ST22&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Nov 2015 11:37:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391871#M4229654</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-26T11:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391872#M4229655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;trace file&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Nov 2015 11:39:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391872#M4229655</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-26T11:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391873#M4229656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with Issaias, you need to check your workprocesses developer traces and find out what is making the dialog processes crash.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, JP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Nov 2015 12:23:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391873#M4229656</guid>
      <dc:creator>JPReyes</dc:creator>
      <dc:date>2015-11-26T12:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391874#M4229657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Didn't see any attachments to this reply. Can you upload dev_w0 from the work directory so that whoever is interested can have a look and try and help you out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amerjit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Nov 2015 12:56:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391874#M4229657</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-26T12:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391875#M4229658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;The count tell the number of time the work process has restarted after the system restart.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;In your case I see the main reason is heap memory. It is set low.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;Work process restarts itself once it reaches heaplimit value or the heap configured for the work process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;Parameters:&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;abap/heaplimit&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 10pt; font-family: inherit; background: transparent;"&gt;abap/heap_area_dia&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;abap/heap_area_nondia&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;From your St02 screen-shot I can see the value set to heap is very small.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;Regards,&lt;/P&gt;&lt;P style="font-size: 12px; color: #333333; background: #ffffff;"&gt;Prithviraj.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Nov 2015 11:40:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391875#M4229658</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-27T11:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391876#M4229659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;abap/heaplimit should &lt;SPAN style="text-decoration: underline;"&gt;not&lt;/SPAN&gt; be changed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;It has to be a low value (40MB - 60MB).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;This is not a memory allocation limit.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;Read the parameter documentation through the transaction RZ11 for more details.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-size: 13.3333px; font-family: inherit; background: transparent;"&gt;Isaías&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Dec 2015 12:35:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391876#M4229659</guid>
      <dc:creator>Isaias_SAP</dc:creator>
      <dc:date>2015-12-01T12:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391877#M4229660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if possible restart the application when the system load is less .&lt;/P&gt;&lt;P&gt;hope this fix the issue .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Jan 2016 08:57:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391877#M4229660</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-23T08:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391878#M4229661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check the below notes, which gives you the various reason for workprocess restart&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 16px; font-weight: bold; background-color: #cfecff;"&gt;Note 101717 - Automatic restart of SAP R/3 work processes&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And still if you are seeing the "red" highlights(In Failure column) in SM50. Please follow the below steps to resolve this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;tcode SM50&amp;gt;&amp;gt; List &amp;gt;&amp;gt; Reset &amp;gt;&amp;gt; Failures (After resetting, the red highlights will disappear)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Little late reply but still it may help someone who experience this issue in future &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.sap.com/74/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Mervin Joseph&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jan 2016 07:16:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391878#M4229661</guid>
      <dc:creator>mervin_joseph</dc:creator>
      <dc:date>2016-01-25T07:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391879#M4229662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many thanks Mervin - I shall take a look&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jan 2016 07:29:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391879#M4229662</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-25T07:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: SM66 - Work Process Failures</title>
      <link>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391880#M4229663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;tcode SM50&amp;gt;&amp;gt; List &amp;gt;&amp;gt; Reset &amp;gt;&amp;gt; Failures (After resetting, the red highlights will disappear)&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although this will reset the counter and make the red light go away, it will not fix the root cause of the issue &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.sap.com/74/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jan 2016 19:34:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sm66-work-process-failures/qaa-p/11391880#M4229663</guid>
      <dc:creator>Isaias_SAP</dc:creator>
      <dc:date>2016-01-25T19:34:07Z</dc:date>
    </item>
  </channel>
</rss>

