<?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: basestar errors in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/basestar-errors/m-p/3668252#M72488</link>
    <description>As an afterthought, you might consider&lt;BR /&gt;disclosing things like the VMS version, the&lt;BR /&gt;terminal server type, and so on.</description>
    <pubDate>Wed, 09 Nov 2005 18:17:36 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2005-11-09T18:17:36Z</dc:date>
    <item>
      <title>basestar errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/basestar-errors/m-p/3668250#M72486</link>
      <description>Could someone guide me in understanding some of these errors I am getting from bs history log?  &lt;BR /&gt;&lt;BR /&gt;Error occurred on VAX port LTA102:&lt;BR /&gt;Unexpected reply from station #1, Expected station #5.&lt;BR /&gt;Unexpected reply from station #3, Expected station #10.&lt;BR /&gt;Unexpected reply from station #84, Expected station #5.&lt;BR /&gt;Error occurred on VAX port LTA102:, Network address = 006.&lt;BR /&gt;QIO error.&lt;BR /&gt;device timeout&lt;BR /&gt;&lt;BR /&gt;I am thinking there is a general error with the LAT line all together, since all devices on the line are seeing similar errors.&lt;BR /&gt;&lt;BR /&gt;Scott&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Nov 2005 16:41:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/basestar-errors/m-p/3668250#M72486</guid>
      <dc:creator>Scott Prior_1</dc:creator>
      <dc:date>2005-11-09T16:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: basestar errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/basestar-errors/m-p/3668251#M72487</link>
      <description>Google found a document which says:&lt;BR /&gt;&lt;BR /&gt;QIO error. &lt;BR /&gt;Explanation: Error. An error occurred when reading or writing data to the port. &lt;BR /&gt;User Action: Examine the error message and take action based on the error found. If connected via a terminal server examine the terminal server&lt;BR /&gt;counters for errors as well. Check cabling for improper length, improper grounding, breaks, etc. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Unexpected reply from station #!UB, Expected station #!UB. &lt;BR /&gt;Explanation: Error. A different programmable controller responded to a request than the one expected. This problem could be the result of a faulty&lt;BR /&gt;controller or because of a faulty cable. &lt;BR /&gt;User Action: Check cabling for improper length, improper grounding, breaks, etc. If cabling checks out, then replace the controller. &lt;BR /&gt;&lt;BR /&gt;Sounds to me like reasonable advice.&lt;BR /&gt;&lt;BR /&gt;Have you tried anything like restarting the&lt;BR /&gt;terminal server, or logging into it to see&lt;BR /&gt;if it has a story to tell?</description>
      <pubDate>Wed, 09 Nov 2005 18:10:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/basestar-errors/m-p/3668251#M72487</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2005-11-09T18:10:15Z</dc:date>
    </item>
    <item>
      <title>Re: basestar errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/basestar-errors/m-p/3668252#M72488</link>
      <description>As an afterthought, you might consider&lt;BR /&gt;disclosing things like the VMS version, the&lt;BR /&gt;terminal server type, and so on.</description>
      <pubDate>Wed, 09 Nov 2005 18:17:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/basestar-errors/m-p/3668252#M72488</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2005-11-09T18:17:36Z</dc:date>
    </item>
  </channel>
</rss>

