Input buffer overflow, how to troubleshoot?

  • Thread starter Thread starter jbclem
  • Start date Start date
J

jbclem

I have a stock market program that gets real time data during market hours.
It's Global Server module, which collects and stores the data, is shutting
off the data collection 2-10 times a day with the error message "input
buffer overflow". I can easily start the data collection up again by
setting it to "collect offline" and then to "collect online". I have a
vague idea what an input buffer is, but I'm not sure if it represents a
space in memory, or a file on a hard drive. I'm also not sure if this
reference is to a Win2000 input buffer or one that's created by the
software.

Can someone show me how to troubleshoot this type of problem? Is there
someway to monitor an "input buffer overflow".
The Event Log(in the Global Server module) that shows me the error message
is poorly designed, and there is no way to spot exactly what time the event
occured unless you catch it exactly when it happens, before the message
scrolls off the screen. Even a program that would capture the Event Log
screen in real time and save it for reference, that would help a lot so I
could try to pin down exactly when this problem occurs.

I'd appreciate any suggestions.

John
 
Tell me about your computer
CPU
RAM type and amount
Any problems since OS installed
Any problems other than this installing this program.
What is the name of the program
Anything else you find relevant

thx,
don
--------------------





I have a stock market program that gets real time data during market hours.
It's Global Server module, which collects and stores the data, is shutting
off the data collection 2-10 times a day with the error message "input
buffer overflow". I can easily start the data collection up again by
setting it to "collect offline" and then to "collect online". I have a
vague idea what an input buffer is, but I'm not sure if it represents a
space in memory, or a file on a hard drive. I'm also not sure if this
reference is to a Win2000 input buffer or one that's created by the
software.

Can someone show me how to troubleshoot this type of problem? Is there
someway to monitor an "input buffer overflow".
The Event Log(in the Global Server module) that shows me the error message
is poorly designed, and there is no way to spot exactly what time the event
occured unless you catch it exactly when it happens, before the message
scrolls off the screen. Even a program that would capture the Event Log
screen in real time and save it for reference, that would help a lot so I
could try to pin down exactly when this problem occurs.

I'd appreciate any suggestions.

John
 
Back
Top