<?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: General Socket Error in AcuConnect in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713123#M385216</link>
    <description>&amp;gt;Not yet. Why?&lt;BR /&gt;&lt;BR /&gt;So they can tell you how to fix the problem.</description>
    <pubDate>Mon, 15 Nov 2010 09:14:42 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2010-11-15T09:14:42Z</dc:date>
    <item>
      <title>General Socket Error in AcuConnect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713119#M385212</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Platform&lt;BR /&gt;Server:&lt;BR /&gt;Model:    HP rx2660&lt;BR /&gt;O/S:     HP-UX 11iv3&lt;BR /&gt;Acu Product:  AcuConnect + AcuRuntime version 7.2&lt;BR /&gt;&lt;BR /&gt;Client PC:&lt;BR /&gt;O/S:    Windows 98/XP&lt;BR /&gt;Acu Product: AcuThinClient version 7.2&lt;BR /&gt;&lt;BR /&gt;Case 1:&lt;BR /&gt;1. All the clients encountered â  General Socket Errorâ   when they tried to establish a NEW connection to run the Acu-GT application from the HP Server! &lt;BR /&gt;2. At the same time, for those Clients that have already established the connection to the HP Server earlier (before the â  General Socket Errorâ   started to happen), their connections would not be affected &amp;amp; still could continue running the same ACU-GT application as normal (unless they disconnected &amp;amp; reconnected to the HP Server again)!&lt;BR /&gt;3. It happened 3 times in the passed 6 months!  &lt;BR /&gt;&lt;BR /&gt;Case 2:&lt;BR /&gt;1. A Client, running on Windows XP, hit the â  General Socket Errorâ   while at the middle of running the same Acu-GT application (out of sudden)!&lt;BR /&gt;2. After closing the error screen, the same Client could re-run the same ACU-GT application without any problems!&lt;BR /&gt;3. In this case, the rest of the Clients were not affected; they still could establish a NEW connection to the HP Server to run the Acu-GT application!&lt;BR /&gt;&lt;BR /&gt;Attach is the capture print screen from the client pc.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;AcuConnect Error Log (acurcl.log):&lt;BR /&gt;Configuration file = '/etc/acurcl.cfg'&lt;BR /&gt;Set parameter 'ACCESS_FILE' to '/etc/AcuAccess'&lt;BR /&gt;Set parameter 'SERVER_ALIAS_FILE' to '/etc/acurcl.ini'&lt;BR /&gt;Set parameter 'SERVER_IP' to '128.0.0.5'&lt;BR /&gt;Set parameter 'DEFAULT_USER' to 'root'&lt;BR /&gt;Set parameter 'ACURCL_PORT' to 5632&lt;BR /&gt;Set parameter 'SERVER_RUNTIME' to '/opt/acucorp/720/bin/runcbl'&lt;BR /&gt;kill: 28299: no such process&lt;BR /&gt;kill: 15630: no such process&lt;BR /&gt;kill: 10822: no such process&lt;BR /&gt;sh: kill: bad argument count&lt;BR /&gt;sh: kill: bad argument count&lt;BR /&gt;kill: 24972: no such process&lt;BR /&gt;kill: 1981: no such process&lt;BR /&gt;kill: 19609: no such process&lt;BR /&gt;kill: 23392: no such process&lt;BR /&gt;kill: 2927: no such process&lt;BR /&gt;kill: 15826: no such process&lt;BR /&gt;kill: 14602: no such process&lt;BR /&gt;kill: 20743: no such process&lt;BR /&gt;kill: 29789: no such process&lt;BR /&gt;kill: 28704: no such process&lt;BR /&gt;kill: 9777: no such process&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Nov 2010 02:45:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713119#M385212</guid>
      <dc:creator>Chui Kock You_1</dc:creator>
      <dc:date>2010-11-15T02:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: General Socket Error in AcuConnect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713120#M385213</link>
      <description>Have you contacted Acucorp?</description>
      <pubDate>Mon, 15 Nov 2010 05:37:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713120#M385213</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2010-11-15T05:37:04Z</dc:date>
    </item>
    <item>
      <title>Re: General Socket Error in AcuConnect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713121#M385214</link>
      <description>Hi Dennis,&lt;BR /&gt;&lt;BR /&gt;Not yet. Why?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Chui</description>
      <pubDate>Mon, 15 Nov 2010 06:57:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713121#M385214</guid>
      <dc:creator>Chui Kock You_1</dc:creator>
      <dc:date>2010-11-15T06:57:54Z</dc:date>
    </item>
    <item>
      <title>Re: General Socket Error in AcuConnect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713122#M385215</link>
      <description>Hi Chui , &lt;BR /&gt;from the client pc where/when you are having errro , did control panel &amp;gt; administrative tolls &amp;gt; event viewer gave you some hint.&lt;BR /&gt;At the time of problem , alo whad did the syslog.log on the server said ....perhaps the clue will be in these log files.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Reg,</description>
      <pubDate>Mon, 15 Nov 2010 08:05:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713122#M385215</guid>
      <dc:creator>DeafFrog</dc:creator>
      <dc:date>2010-11-15T08:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: General Socket Error in AcuConnect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713123#M385216</link>
      <description>&amp;gt;Not yet. Why?&lt;BR /&gt;&lt;BR /&gt;So they can tell you how to fix the problem.</description>
      <pubDate>Mon, 15 Nov 2010 09:14:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713123#M385216</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2010-11-15T09:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: General Socket Error in AcuConnect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713124#M385217</link>
      <description>Hi DeafFrog,&lt;BR /&gt;&lt;BR /&gt;I don't find any socket error meassage shown in the syslog. Attach is the syslog file as shown below.&lt;BR /&gt;&lt;BR /&gt;For client pc i'm still checking the error message in the event viewer. &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Chui</description>
      <pubDate>Tue, 16 Nov 2010 11:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713124#M385217</guid>
      <dc:creator>Chui Kock You_1</dc:creator>
      <dc:date>2010-11-16T11:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: General Socket Error in AcuConnect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713125#M385218</link>
      <description>Is it actually reasonable to assume that the AcuConnect server software would log errors to syslog rather than an application-specific log file?</description>
      <pubDate>Tue, 16 Nov 2010 18:55:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/general-socket-error-in-acuconnect/m-p/4713125#M385218</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2010-11-16T18:55:38Z</dc:date>
    </item>
  </channel>
</rss>

