<?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 Re: End-to-end errors in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484632#M2242</link>
    <description>Mike, thanks-I found those fixes yesterday and that fixed the issue. Wonderful!</description>
    <pubDate>Tue, 25 Aug 2009 11:48:45 GMT</pubDate>
    <dc:creator>Alice Seeley</dc:creator>
    <dc:date>2009-08-25T11:48:45Z</dc:date>
    <item>
      <title>End-to-end errors</title>
      <link>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484630#M2240</link>
      <description>2 of my customers have seen a new batch of E-2-E errors since installation on Friday. Has anyone else experienced this? Was there a new patch that came out with the sync that they did on Friday? This is Webes 5.5 patch 1 I thought but there was a webes update done when it synched up with HP.</description>
      <pubDate>Mon, 24 Aug 2009 10:11:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484630#M2240</guid>
      <dc:creator>Alice Seeley</dc:creator>
      <dc:date>2009-08-24T10:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: End-to-end errors</title>
      <link>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484631#M2241</link>
      <description>Alice, there are two fixes that resolve this most of the time. The first is, open System Event Analyzer and go to the 6th Icon in the second group above, the yellow triangle with the ? in the middle, make sure that the WEBES Log Notification is turned "on". The second fix is to open a command prompt and enter the following commands:&lt;BR /&gt;1. Go to the prompt and issue:&lt;BR /&gt;ï § desta dri add SEA.idleTimeoutSeconds&lt;BR /&gt;ï § desta dri set SEA.idleTimeoutSeconds 57600&lt;BR /&gt;ï § net stop desta_service&lt;BR /&gt;ï § net stop wccproxy&lt;BR /&gt;2. Right click on My Computer -&amp;gt; Manage, go to Application log file, clear the log and make sure that the maximum log size is 8-16mb.&lt;BR /&gt;3. Go to the prompt again and issue:&lt;BR /&gt;ï § net start wccproxy&lt;BR /&gt;ï § net start desta_service&lt;BR /&gt;&lt;BR /&gt; If you perform both fixes you will probably resolve this.&lt;BR /&gt;&lt;BR /&gt; Thanks&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Aug 2009 11:36:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484631#M2241</guid>
      <dc:creator>Michael Wyant</dc:creator>
      <dc:date>2009-08-25T11:36:41Z</dc:date>
    </item>
    <item>
      <title>Re: End-to-end errors</title>
      <link>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484632#M2242</link>
      <description>Mike, thanks-I found those fixes yesterday and that fixed the issue. Wonderful!</description>
      <pubDate>Tue, 25 Aug 2009 11:48:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484632#M2242</guid>
      <dc:creator>Alice Seeley</dc:creator>
      <dc:date>2009-08-25T11:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: End-to-end errors</title>
      <link>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484633#M2243</link>
      <description>This procedure worked for the short term. My customer replies that when he reboots after maintenance, he has to go through the process all over again since it causes him to have the E2E errors again. I was hoping for a more long-term solution for this.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Aug 2009 16:38:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484633#M2243</guid>
      <dc:creator>Alice Seeley</dc:creator>
      <dc:date>2009-08-26T16:38:36Z</dc:date>
    </item>
    <item>
      <title>Re: End-to-end errors</title>
      <link>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484634#M2244</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;what is the version of the WEBES?&lt;BR /&gt;&lt;BR /&gt;If the version is 5.5 with patch1 then follow the below process.&lt;BR /&gt;&lt;BR /&gt;Enable log , which by default is turned off due to a coding issue with the RSS configuration:&lt;BR /&gt;DOS&amp;gt;wsea status&lt;BR /&gt;DOS&amp;gt;wsea log prob on&lt;BR /&gt;DOS&amp;gt;wsea status&lt;BR /&gt;&lt;BR /&gt;NOTE: Compare and check that the following has changed to enabled.&lt;BR /&gt;WSEA Information:&lt;BR /&gt;&lt;BR /&gt;System Event Analyzer for Windows V5.5 (Build 61)   &lt;BR /&gt;Service Tools Home: C:\Program Files\HP\svctools  Service Obligation Start Date: Mon Apr 27 09:41:24 CDT 2009   &lt;BR /&gt;Service Obligation End Date: Tue Apr 27 09:41:24 CDT 2010   &lt;BR /&gt;ACHS/SICL/DSNlink notification: disabled.   &lt;BR /&gt;OSEM/CSG/QSAP notification: disabled.   &lt;BR /&gt;ISEE notification: enabled.   &lt;BR /&gt;HPSIM notification: disabled.   &lt;BR /&gt;MOM notification: disabled.   &lt;BR /&gt;SNMP notification: disabled.   &lt;BR /&gt;DTCS notification: disabled.   &lt;BR /&gt;SMTP notification: enabled.   &lt;BR /&gt;LOG notification: disabled.     &amp;lt;----- needs to be enabled. &lt;BR /&gt;INDICTMENT notification: disabled.   &lt;BR /&gt;EVT notification: enabled.         &lt;BR /&gt;VMSMAIL notification: disabled.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 16 Sep 2009 13:26:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/end-to-end-errors/m-p/4484634#M2244</guid>
      <dc:creator>ShreeS</dc:creator>
      <dc:date>2009-09-16T13:26:46Z</dc:date>
    </item>
  </channel>
</rss>

