Also if you dont want these messages to be logged u can try this.
altermessage 1608, with_log, false
I hope this works for you.
Cheers,
Main Topics
Browse All TopicsHi guys,
We are using SYBASE ASE 11.9.2.2. version, Our error log is flooded with message 1608, client process exited abnormally..
1608 A client process exited abnormally, or a network error was encountered. Unless other errors occurred, continue processing normally.
Searched various websites including SYBASE,read the documentation which says not to worry, (all our client machines running Visual basic connecting to sybase are running fine and none of them have been disconnected as described in the message, there are about 150 simultaneous users connecting to sybase). But for us it has become serious message, flooded with hundereds and hundereds , I have to say thousands of 1608 messages per day. Network guys say network is fine. For this error we had to restart SYBASE server once in a while (for deleting log). I am really worried why sybase is not coming with a solution to this. I tried sp_altermessage 1608, with_log, false, it didn't have any effect, documentation says it works only for the "true", false doesn't have any effect. don't know what to do. I am giving 500 points, I can still increase the points depending on the answer. Can anyone please tell me how to avoid this error in my SYBASE error log file. Please help me. Thank You so much.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
it sounds like the application is not closing the connection gracefully.
do a controlled test: start the app and then exit. If you get a 1608 then blame your developers, maybe a newer version of the ODBC drivers is required ???
maybe you can run your log analysis through a "grep -v" to strip out the 1608 lines.
Hi guys, first things first, thanks to all for answering, but
If you see my question, I tried all the options suggested by many of you (with of no help) except the one by ChrisKing "grep-v",
Chris could you please tell me how do I do grep-v,
regarding ODBC driver, we are using the latest one (released nov 2002 - 04.10.0020 - syodase.dll)
Also we checked all the users none of them has exited abnormally as per 1608 message.
Hy,
grep -v is a Unix command and you seem to be on a windows environment.
You can use grep command on windows with cygwin (a unix "emulator").
Just find the cygwin1.dll and grep.exe on cywgin.com.
Check if you have a line like
Cannot send, host process disconnected: MyServer 2092 spid: 14
just before your error message.
You must investigate on client processes (you can know which are the connected processes with a sp_who or a query like
use master
go
select spid,hostname,hostprocess,
go
)
Try to launch it in a loop and log the processes details. Then compare with your error log and identify spid's that exit abnormaly.
Bye
Hi,
Once again, you should investigate on client processes.
You talk about VB applications. Maybe one of them causes problems.
An application can generate such messages without a crash.
If you use ct_lib, there are some rules that must be respected.
For example, in an application, you can connect to the database with the ct_connect function, you send commands with ct_send, etc... but at the end of your code you must use ct_cancel to cancel all pending transactions, and ct_close to close connection with the database. If you don't do so, your application won't crash or produce any error message, but errors 1608 will appear in server log.
And it is exactly the same with ODBC functions.
I guess it won't be easy, but you must tell your developpers to check their code
Good luck
PS : sp_altermessages only works with user-defined messages
Hi everyone,
Sorry for causing you so much trouble.
Christking, I just wanted to explain praveenpoli what exactly could make such errors. In your first message, you say that this kind of error can result from application not closing connection gracefully (just like explained by mansoor a khan ... :-) ...) and you finish with : maybe you should get a newer version of the ODBC drivers... Then praveenpoli answered that the problem was still unsolved. So, convinced that the problem was due to client application, i tried to explain praveenpoli what are exactly the connection mechanisms to help him identify problematic code, and i think that this was the "something new to the thread"
So now I think it's up to praveenpoli to tell us if my explanations have been helpfull.
Business Accounts
Answer for Membership
by: mansoor_a_khanPosted on 2003-10-15 at 00:14:27ID: 9552700
Here is the information which I could find for u.
The following Error appears in the Sybase Error Log
Error 1608, Severity Level, 21
A client process exited abnormally, or a network error was encountered. Unless other errors occurred, continue processing normally.
Explanation:
This error occurs when a client process stopped without informing SQL Server and a subsequent attempt by SQL Server to send results to this client fails.
Error 1608 is usually not serious and may be viewed as notification that a client process no longer exists. Some of the possible reasons a client process can disappear are:
The client application was killed or ended abnormally
The client machine was powered off or rebooted
There is excessive network traffic
The network connection has been dropped or interrupted
Resolution:
Do not be concerned if this error occurs only sporadically. However, if the error occurs frequently and continuously, or frequently for short periods of time, it may be a result of excessive network traffic or network problems.
If it is suspected that there are network problems, contact the network administrator in order to run diagnostics on the network between the client and the SQL Server machines to isolate the problem.
Note: If this error is preceded by another Sybase error then obtain a complete and current copy of the Sybase error log and forward it to the SPS Help Desk for further analysis. The error log can be found in the c:\sybase\install directory on
cheers,
Mansoor