<?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>topic Crashed VDI while Process is running in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Crashed-VDI-while-Process-is-running/m-p/52735#M7560</link>
    <description>We now had to find out twice that processes in production, which terminate without any problems for days, suddenly stopped and the computer crashes.
In both cases the log in control room shows that nothing happened after one time Kill Process with ProcessName AcroRd32 (Adobe Reader) and onother time after Check File exists (Utility File Management - File exists).

An exception handling is not possible or even takes no effect. Also call immediate stop does not lead to success, only reboot of machine is possible.

Any suggestions why this could happen?</description>
    <pubDate>Thu, 21 Sep 2017 15:16:00 GMT</pubDate>
    <dc:creator>al2piwo</dc:creator>
    <dc:date>2017-09-21T15:16:00Z</dc:date>
    <item>
      <title>Crashed VDI while Process is running</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Crashed-VDI-while-Process-is-running/m-p/52735#M7560</link>
      <description>We now had to find out twice that processes in production, which terminate without any problems for days, suddenly stopped and the computer crashes.
In both cases the log in control room shows that nothing happened after one time Kill Process with ProcessName AcroRd32 (Adobe Reader) and onother time after Check File exists (Utility File Management - File exists).

An exception handling is not possible or even takes no effect. Also call immediate stop does not lead to success, only reboot of machine is possible.

Any suggestions why this could happen?</description>
      <pubDate>Thu, 21 Sep 2017 15:16:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Crashed-VDI-while-Process-is-running/m-p/52735#M7560</guid>
      <dc:creator>al2piwo</dc:creator>
      <dc:date>2017-09-21T15:16:00Z</dc:date>
    </item>
    <item>
      <title>Enable memory logging as this</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Crashed-VDI-while-Process-is-running/m-p/52736#M7561</link>
      <description>Enable memory logging as this might give you a hint.
You can do this in 'System Manager' - &amp;gt; 'Resources', right click on a resource and tick 'Log Memory Usage'.
Also, all Windows machines are in need of restart, preferably daily. Could regular restarts fix the issue?</description>
      <pubDate>Fri, 22 Sep 2017 06:57:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Crashed-VDI-while-Process-is-running/m-p/52736#M7561</guid>
      <dc:creator>ivan.gordeyev</dc:creator>
      <dc:date>2017-09-22T06:57:00Z</dc:date>
    </item>
  </channel>
</rss>

