Hi there,
Obviously the subject is a question, but it's not the question I'm actually asking. Basically I work for a company that has an IBM UniVerse database and have got a slight issue I'm a bit unsure of how to fix.
The issue:
Two events appear in the event log (order of occurrence):
1) UniVerse warning: Unable to read from stdin.. WSA error: 0.
2) UniVerse warning: Unable to write to socket.. WSA error: 10053.
3) UniVerse warning: Unable to read from pipe.. Win32 error: 109. The pipe has been ended..
Now I've seen similar ones like this, it's usually when you have a telnet client and exit out of it rather than logging off cleanly. This isn't because of logging off though, in this case, we don't have any telnet clients running.
The weird thing - these events occur every 10 minutes, on the dot. Sometimes the second event doesn't occur.
We do have a .NET service connecting into UniVerse, but even if you stop all our applications and just have UniVerse running by itself - problem still happens.
As far as I can see it doesn't affect the server, but having these warnings in the event log every 10 minutes isn't the best either.
Researching the individual codes:
WSA error 0
I'm guessing this isn't an actual error related to WSA, but rather a warning from the stdin issue. WSA error 0 seems to indicate success rather than an error.
WSA error 10053
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
Win32 error: 109
Broken pipe, or the pipe has ended.
What I have tried:
- Resizing files appropriately.
- Checking disk for errors.
- Defragged hard drives.
- Checked to make sure telnet service can interact with desktop.
Thanks in advance for any help!
Other Notes
- Server is Windows Server 2003 Standard
- U2 version is 10.1.18 (can't upgrade this yet)
- Two cores
- 4GB of RAM
- Stopping the UniVerse telnet service stops the warnings from appearing, so I'm guessing it's somewhat related.
Submit an article or tip