|
Short Description
|
Same Error over and over over
|
|
Entered
|
By:
intek
When: 1998-08-21 20:07:30 Build: 1.03.20D
|
|
Categories
|
Type:
Problem
Department: Product
Category:
Troubleshooting
|
Description
|
We seem to be getting the following warning:
Warning: Unhandled Telnet Command
cmd=241 data(1)=f1ffef40404040404040404
What is happening here?
|
|
|
|
Append
|
By: WindSurfer When: 1998-08-21 21:46:07 New Status:
Pending Customer
|
|
Comment
|
Please run in diagnostic mode until you see this error, then email your \screensurfer\hostserver\surfdiag.log file to surfer@ieinc.com.
Screensurfer issues a warning whenever it encounters a TelNet option or command that it doesn't support-- this allows us to detect when a customer's TN3270 system is asking for more functionality than we are delivering-- we will review the command that is causing this based on your log file, and incorporate support in a future release, or at least stop the warning if it is an inconsequential option or command.
|
|
|
|
Append
|
By: intek When: 1998-08-24 13:42:10 New Status:
Pending IE
|
|
Comment
|
The log is *really huge*. We're talking 142 megs and 30 megs zipped. Can I cut out a portion of
the log and send it to you?
|
|
|
|
Append
|
By: WindSurfer When: 1998-08-24 15:44:57 New Status:
Pending Customer
|
|
Comment
|
Sure--definitely cut-out a portion!
Are you running in diagnostic mode on the production server? With many users, this will drive the log-up pretty quickly!
To stop the logging without having to do a shutdown, go to the Administrator's Console Settings page and change "Sessions to Log" to 0 (zero)-- this should prevent massive logging-- if we need to log on the production server, in the future you should set a log file name and a specific session to log, which then prevents all sessions from hammering the log...then run as a service instead of the diagnostic mode.
|
|
|
|
Append
|
By: intek When: 1998-08-25 14:28:38 New Status:
Pending IE
|
|
Comment
|
We were running in diagnostic mode before to troubleshoot but we are now running as a service.
Just as an aside, when we first installed screensurfer, we realized we didn't want to install it in its current location so we un-installed it and reinstalled it. For some reason, after the re-installation it would only run in diagnostic mode, anything else would complain that the system could not find the specified path. Perhaps the re-installation did not overwrite the original services-registry key path?
Anyway, after much angst we figured out how to fix it!
Thanks for the tips on reconfiguring the logging, we will see if this improves upon the number of errors we've been getting (we suspect timeouts). I will also send out the log with all the cmd=241 undefined telnet errors to you.
Intek
|
|
|
|
Append
|
By: WindSurfer When: 1998-11-09 21:50:17 New Status:
Pending Customer
|
|
Comment
|
We have fixed the 241 command in recent builds-- is it still an issue for you?
|
|
|
|
Append
|
By: intek When: 1999-01-05 18:30:37 New Status:
Closed
|
|
Comment
|
Things seem to have settled down with the new build(s).
|