Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.

SYS1000 Stdioerrs

Hola all,

I've recently done some archiving (20+ years worth of data) and table remaking which has done wonders for my client's performance.

Now we're have an issue, likely unrelated, with processes, especially overnight processes, crashing with the SYS1000/STDIOERRs. The same processes will run fine during the day, and the errors don't seem to be tied to specific processes. I'm pretty sure there is something network-related causing this, but the servers' logs aren't showing anything helpful in diagnosing. Once the error occurs, the OI session is dead in the water; nothing works. It has to be closed and reopened.

Does anyone have any suggestions what we can check?

Thanks,

Michael

Comments

  • If I recall correctly, the SYS1000 errors are those caused by a disconnection from the network. I assume you are using UD4.7.x not UD5.x. UD4.7.x does not reconnect after a disconnect.
  • Actually using UD5.2. But the interruption is long enough to crash the program. And once it crashes, OI is totally inoperable.
  • I was under the impression that UD5x was able to reconnect and continue unlike UD4.7.x. Maybe I am wrong as I have not used UD5x but when upgrading to OI10.2.3 I will look at the reconnection option (if available) with the UD that comes with OI10x.
  • Still using OI9.4. So if the reconnect is part of OI10, it's a no-go.

    There's no obvious reason for the loss of network connection and nothing in any logs.

    Thanks for looking into it.
  • edited 12:45AM
    If “Allow clients to reconnect” is checked, the workstations will attempt to reconnect with the Universal Driver if their session is interrupted do to network issues. NOTE: reconnection will only succeed if the cause of the interruption is network related; if either the Universal Driver or the workstation has shut down, then the existing session cannot be restored. Also note that, if reconnect is allowed, it is strongly suggested that either the “Encrypt” or “Encrypt and validate” secure option is selected to prevent “spoofing” during a reconnect attempt.




    Not sure now if it supposed to work with 9.4
  • edited 12:58AM
    The Revelation Universal Driver NUL version 5.2 will ONLY communicate with OpenInsight 9.4 and above.

    I interpret that as meaning you cant use the one that comes with OI10, you need use the one for OI9 (32 bit I assume)

    But arent you already running 5.2 for OI9 , if so, it is supposed to be inbuilt as an automatic feature.
  • Reconnecting is a feature of the UD 5.x, regardless of the version of OI. However, I have yet to see it work under any situation. I've addressed this with Revelation and they have acknowledged it will work only under very specific situations. In short, I don't think it is as robust as we would hope it to be.
Sign In or Register to comment.