sybase客户端连接数据库，报错，如何处理（图）？？？？

myr

我的服务器w2k，sybase 11.9，客户端相同，客户端使用Sybase Central连接数据库，用户为sa进行管理，十几分钟没有操作，这时再做任何操作时的会报错如图。
   我其他服务器（环境相同，测试用）从来没有出现过这种问题。
   这是什么原因？怎么才可以正常？谢谢了！

myr

还有两个提示，如图

chenfeng825

首先检测你的网络。再看看errorlg有什么信息。

myr

网络应该没有问题，这是我今天的所有     
00:00000:00000:2003/07/30 07:54:45.85 kernel  kisignal: SQL Server terminated by system shutdown.
00:00000:00000:2003/07/30 07:54:45.86 kernel  ueshutdown: exiting
00:00000:00000:2003/07/30 07:54:45.88 kernel  Abnormal exit detected - SQL Server process level execution bindings will be cleared on startup.
00:00000:00000:2003/07/30 07:56:27.43 kernel  Using config area from primary master device.
00:00000:00000:2003/07/30 07:56:27.85 kernel  Warning: Using default file 'C:\Sybase\XHSD.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2003/07/30 07:56:28.82 kernel  Kernel memory at 0x20000000, 217088 bytes
00:00000:00000:2003/07/30 07:56:28.83 kernel  Server part of first shared memory region at 0x20035000, 305959096 bytes
00:00000:00000:2003/07/30 07:56:28.83 kernel  Highest valid address is 0x20035000
00:00000:00000:2003/07/30 07:56:28.83 kernel  Using 100000 file descriptors.
00:00000:00000:2003/07/30 07:56:29.66 kernel  Adaptive Server Enterprise/11.9.2/1031/P/NT (IX86)/OS 3.51,4.0/FBU/Fri Aug 14 01:42:41 1998
00:00000:00000:2003/07/30 07:56:29.66 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2003/07/30 07:56:29.66 kernel  Copyright 1987, 1998
00:00000:00000:2003/07/30 07:56:29.66 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2003/07/30 07:56:29.66 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2003/07/30 07:56:29.66 kernel  
00:00000:00000:2003/07/30 07:56:29.66 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2003/07/30 07:56:29.66 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2003/07/30 07:56:29.66 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2003/07/30 07:56:29.66 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2003/07/30 07:56:29.66 kernel  agreement  specifying  the  Government's rights to use the software and any
00:00000:00000:2003/07/30 07:56:29.66 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2003/07/30 07:56:29.66 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2003/07/30 07:56:29.66 kernel  Using 'C:\Sybase\XHSD.cfg' for configuration information.
00:00000:00000:2003/07/30 07:56:29.66 kernel  Logging SQL Server messages in file 'C:\Sybase\install\errorlog'.
00:00000:00000:2003/07/30 07:56:30.08 kernel  Directory Control Layer (DCL) using directory driver: InterfacesDriver
00:00000:00000:2003/07/30 07:56:30.28 kernel  *** WARNING ******************
00:00000:00000:2003/07/30 07:56:30.28 kernel  Operating system may favor the system cache when memory is at a premium.
To disable this warning, set the registry parameter 'LargeSystemCache' to 0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.
00:00000:00000:2003/07/30 07:56:30.28 kernel  SQL Server NT process id is 0x3ec.
00:00000:00000:2003/07/30 07:56:30.28 kernel  SQL Server was started as a Service.
00:00000:00000:2003/07/30 07:56:30.28 kernel  Network and device connection limit is 99992.
00:00000:00000:2003/07/30 07:56:30.87 server  Number of proc buffers allocated: 28885.
00:00000:00000:2003/07/30 07:56:31.23 server  Proc header memory allocated 14442 pages for each per engine cache
00:00000:00000:2003/07/30 07:56:31.23 server  Number of blocks left for proc headers: 28944.
00:00000:00000:2003/07/30 07:56:31.23 server  Memory allocated for the default data cache cache: 217720 Kb
00:00000:00000:2003/07/30 07:56:31.25 server  Size of the 2K memory pool: 217720 Kb
00:00000:00000:2003/07/30 07:56:31.26 kernel  Initializing virtual device 0, 'C:\Sybase\DATA\MASTER.dat'
00:00000:00000:2003/07/30 07:56:31.27 kernel  Virtual device 0 started using asynchronous i/o.
00:00000:00000:2003/07/30 07:56:31.27 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2003/07/30 07:56:31.27 kernel  Either the config parameter 'use security services' is set to 0, or ASE does not support use of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms will be supported.
00:00000:00000:2003/07/30 07:56:31.67 kernel  engine 0, os pid 180  online
00:00000:00000:2003/07/30 07:56:31.72 server  No active traceflags
00:00000:00001:2003/07/30 07:56:32.60 server  Opening Master Database ...
00:00000:00001:2003/07/30 07:56:35.11 server  Loading SQL Server's default sort order and character set
00:00000:00003:2003/07/30 07:56:35.15 kernel  network name xhsd, type ether, port 5000
00:00000:00004:2003/07/30 07:56:35.15 kernel  network name 192.168.0.253, type ether, port 5000
00:00000:00005:2003/07/30 07:56:35.16 kernel  network name 61.185.217.180, type ether, port 5000
00:00000:00001:2003/07/30 07:56:35.41 server  Recovering database 'master'
00:00000:00001:2003/07/30 07:56:36.05 server  Redo pass of recovery has processed 1 committed and 0 aborted transactions.
00:00000:00001:2003/07/30 07:56:38.69 server  Database 'master' is now online.
00:00000:00001:2003/07/30 07:56:38.79 server  The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:56:38.86 server  0 dump conditions detected at boot time
00:00000:00001:2003/07/30 07:56:38.94 server  server is unnamed
00:00000:00001:2003/07/30 07:56:39.00 server  Activating disk 'TEMPD'.
00:00000:00001:2003/07/30 07:56:39.00 kernel  Initializing virtual device 4, 'D:\data\TEMPD.DAT'
00:00000:00001:2003/07/30 07:56:41.98 kernel  Virtual device 4 started using asynchronous i/o.
00:00000:00001:2003/07/30 07:56:41.98 server  Activating disk 'TSJH'.
00:00000:00001:2003/07/30 07:56:41.98 kernel  Initializing virtual device 5, 'D:\data\TSJH.DAT'
00:00000:00001:2003/07/30 07:56:41.98 kernel  Virtual device 5 started using asynchronous i/o.
00:00000:00001:2003/07/30 07:56:41.98 server  Activating disk 'TSJHLOG'.
00:00000:00001:2003/07/30 07:56:41.98 kernel  Initializing virtual device 6, 'D:\data\TSJHLOG.DAT'
00:00000:00001:2003/07/30 07:56:41.98 kernel  Virtual device 6 started using asynchronous i/o.
00:00000:00001:2003/07/30 07:56:41.98 server  Activating disk 'YXJH'.
00:00000:00001:2003/07/30 07:56:41.98 kernel  Initializing virtual device 2, 'D:\data\YXJH.DAT'
00:00000:00001:2003/07/30 07:56:41.98 kernel  Virtual device 2 started using asynchronous i/o.
00:00000:00001:2003/07/30 07:56:41.98 server  Activating disk 'YXJHLOG'.
00:00000:00001:2003/07/30 07:56:41.98 kernel  Initializing virtual device 3, 'D:\data\YXJHLOG.DAT'
00:00000:00001:2003/07/30 07:56:41.98 kernel  Virtual device 3 started using asynchronous i/o.
00:00000:00001:2003/07/30 07:56:41.98 server  Activating disk 'sysprocsdev'.
00:00000:00001:2003/07/30 07:56:41.98 kernel  Initializing virtual device 1, 'C:\Sybase\DATA\SYBPROCS.DAT'
00:00000:00001:2003/07/30 07:56:42.01 kernel  Virtual device 1 started using asynchronous i/o.
00:00000:00001:2003/07/30 07:56:42.65 server  Recovering database 'model'.
00:00000:00001:2003/07/30 07:56:42.73 server  The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:56:42.91 server  Database 'model' is now online.
00:00000:00001:2003/07/30 07:56:42.91 server  Clearing temp db
00:00000:00001:2003/07/30 07:56:47.31 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:56:58.11 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:56:58.16 server  Database 'tempdb' is now online.
00:00000:00001:2003/07/30 07:56:58.17 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:56:58.25 server  Recovering database 'sybsystemprocs'.
00:00000:00001:2003/07/30 07:56:59.58 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:56:59.62 server  Database 'sybsystemprocs' is now online.
00:00000:00001:2003/07/30 07:56:59.81 server  Recovering database 'YX_EXCHANGE'.
00:00000:00001:2003/07/30 07:57:53.33 server  The transaction log in the database 'YX_EXCHANGE' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:57:53.35 server  Database 'YX_EXCHANGE' is now online.
00:00000:00001:2003/07/30 07:57:53.44 server  Recovering database 'CHAINCENTER'.
00:00000:00001:2003/07/30 07:58:28.96 server  The transaction log in the database 'CHAINCENTER' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 07:58:28.98 server  Database 'CHAINCENTER' is now online.
00:00000:00001:2003/07/30 07:58:28.98 server  Recovery complete.
00:00000:00001:2003/07/30 07:58:28.98 server  SQL Server's default sort order is:
00:00000:00001:2003/07/30 07:58:28.98 server          'bin_iso_1' (ID = 50)
00:00000:00001:2003/07/30 07:58:28.98 server  on top of default character set:
00:00000:00001:2003/07/30 07:58:28.98 server          'iso_1' (ID = 1).
00:00000:00001:2003/07/30 07:58:28.98 server  Loaded default Unilib conversion handle.
00:00000:00003:2003/07/30 08:13:14.94 server  Error: 1605, Severity: 18, State: 1
00:00000:00003:2003/07/30 08:13:14.94 server  Failed to open virtual socket for new connections
00:00000:00003:2003/07/30 08:13:19.61 server  Error: 1605, Severity: 18, State: 1
00:00000:00003:2003/07/30 08:13:19.61 server  Failed to open virtual socket for new connections
00:00000:00003:2003/07/30 08:15:21.31 server  Error: 1605, Severity: 18, State: 1
00:00000:00003:2003/07/30 08:15:21.31 server  Failed to open virtual socket for new connections
00:00000:00003:2003/07/30 08:18:39.81 server  Error: 1605, Severity: 18, State: 1
00:00000:00003:2003/07/30 08:18:39.81 server  Failed to open virtual socket for new connections
00:00000:00001:2003/07/30 08:18:52.93 kernel  Cannot send, host process disconnected: MYR 1212 spid: 1
00:00000:00001:2003/07/30 08:18:52.93 server  Error: 1608, Severity: 18, State: 4
00:00000:00001:2003/07/30 08:18:52.93 server  A client process exited abnormally, or a network error was encountered. Unless other errors occurred, continue processing normally.
00:00000:00000:2003/07/30 08:47:03.93 kernel  Using config area from primary master device.
00:00000:00000:2003/07/30 08:47:04.41 kernel  Warning: Using default file 'C:\Sybase\XHSD.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2003/07/30 08:47:05.57 kernel  Kernel memory at 0x20000000, 217088 bytes
00:00000:00000:2003/07/30 08:47:05.59 kernel  Server part of first shared memory region at 0x20035000, 305959096 bytes
00:00000:00000:2003/07/30 08:47:05.59 kernel  Highest valid address is 0x20035000
00:00000:00000:2003/07/30 08:47:05.59 kernel  Using 100000 file descriptors.
00:00000:00000:2003/07/30 08:47:06.88 kernel  Adaptive Server Enterprise/11.9.2/1031/P/NT (IX86)/OS 3.51,4.0/FBU/Fri Aug 14 01:42:41 1998
00:00000:00000:2003/07/30 08:47:06.88 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2003/07/30 08:47:06.88 kernel  Copyright 1987, 1998
00:00000:00000:2003/07/30 08:47:06.88 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2003/07/30 08:47:06.88 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2003/07/30 08:47:06.88 kernel  
00:00000:00000:2003/07/30 08:47:06.88 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2003/07/30 08:47:06.88 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2003/07/30 08:47:06.88 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2003/07/30 08:47:06.88 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2003/07/30 08:47:06.88 kernel  agreement  specifying  the  Government's rights to use the software and any
00:00000:00000:2003/07/30 08:47:06.88 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2003/07/30 08:47:06.88 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2003/07/30 08:47:06.88 kernel  Using 'C:\Sybase\XHSD.cfg' for configuration information.
00:00000:00000:2003/07/30 08:47:06.88 kernel  Logging SQL Server messages in file 'C:\Sybase\install\errorlog'.
00:00000:00000:2003/07/30 08:47:07.58 kernel  Directory Control Layer (DCL) using directory driver: InterfacesDriver
00:00000:00000:2003/07/30 08:47:07.86 kernel  *** WARNING ******************
00:00000:00000:2003/07/30 08:47:07.86 kernel  Operating system may favor the system cache when memory is at a premium.
To disable this warning, set the registry parameter 'LargeSystemCache' to 0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.
00:00000:00000:2003/07/30 08:47:07.86 kernel  SQL Server NT process id is 0x3e4.
00:00000:00000:2003/07/30 08:47:07.86 kernel  SQL Server was started as a Service.
00:00000:00000:2003/07/30 08:47:07.87 kernel  Network and device connection limit is 99992.
00:00000:00000:2003/07/30 08:47:08.82 server  Number of proc buffers allocated: 28885.
00:00000:00000:2003/07/30 08:47:09.06 server  Proc header memory allocated 14442 pages for each per engine cache
00:00000:00000:2003/07/30 08:47:09.06 server  Number of blocks left for proc headers: 28944.
00:00000:00000:2003/07/30 08:47:09.06 server  Memory allocated for the default data cache cache: 217720 Kb
00:00000:00000:2003/07/30 08:47:09.07 server  Size of the 2K memory pool: 217720 Kb
00:00000:00000:2003/07/30 08:47:09.13 kernel  Initializing virtual device 0, 'C:\Sybase\DATA\MASTER.dat'
00:00000:00000:2003/07/30 08:47:09.13 kernel  Virtual device 0 started using asynchronous i/o.
00:00000:00000:2003/07/30 08:47:09.13 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2003/07/30 08:47:09.13 kernel  Either the config parameter 'use security services' is set to 0, or ASE does not support use of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms will be supported.
00:00000:00000:2003/07/30 08:47:10.06 kernel  engine 0, os pid 180  online
00:00000:00000:2003/07/30 08:47:10.21 server  No active traceflags
00:00000:00001:2003/07/30 08:47:11.62 server  Opening Master Database ...
00:00000:00001:2003/07/30 08:47:15.90 server  Loading SQL Server's default sort order and character set
00:00000:00003:2003/07/30 08:47:15.92 kernel  network name xhsd, type ether, port 5000
00:00000:00004:2003/07/30 08:47:15.93 kernel  network name 192.168.0.253, type ether, port 5000
00:00000:00005:2003/07/30 08:47:15.95 kernel  network name 61.185.217.180, type ether, port 5000
00:00000:00005:2003/07/30 08:47:15.95 kernel  NT operating system error 10049 in module 'e:\earl2\porttree\svr\sql\generic\ksource\strmio\n_winsock.c' at line 1358: 在其上下文中，该请求的地址无效。.
00:00000:00005:2003/07/30 08:47:16.02 kernel  ninit: bind, Could not bind socket address.
00:00000:00005:2003/07/30 08:47:16.12 server  Unable to initialize network 3
00:00000:00001:2003/07/30 08:47:16.83 server  Recovering database 'master'
00:00000:00001:2003/07/30 08:47:18.14 server  Redo pass of recovery has processed 1 committed and 0 aborted transactions.
00:00000:00001:2003/07/30 08:47:19.95 server  Database 'master' is now online.
00:00000:00001:2003/07/30 08:47:20.04 server  The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:47:20.06 server  0 dump conditions detected at boot time
00:00000:00001:2003/07/30 08:47:20.07 server  server is unnamed
00:00000:00001:2003/07/30 08:47:20.08 server  Activating disk 'TEMPD'.
00:00000:00001:2003/07/30 08:47:20.09 kernel  Initializing virtual device 4, 'D:\data\TEMPD.DAT'
00:00000:00001:2003/07/30 08:47:24.83 kernel  Virtual device 4 started using asynchronous i/o.
00:00000:00001:2003/07/30 08:47:24.83 server  Activating disk 'TSJH'.
00:00000:00001:2003/07/30 08:47:24.83 kernel  Initializing virtual device 5, 'D:\data\TSJH.DAT'
00:00000:00001:2003/07/30 08:47:24.83 kernel  Virtual device 5 started using asynchronous i/o.
00:00000:00001:2003/07/30 08:47:24.83 server  Activating disk 'TSJHLOG'.
00:00000:00001:2003/07/30 08:47:24.83 kernel  Initializing virtual device 6, 'D:\data\TSJHLOG.DAT'
00:00000:00001:2003/07/30 08:47:24.83 kernel  Virtual device 6 started using asynchronous i/o.
00:00000:00001:2003/07/30 08:47:24.83 server  Activating disk 'YXJH'.
00:00000:00001:2003/07/30 08:47:24.83 kernel  Initializing virtual device 2, 'D:\data\YXJH.DAT'
00:00000:00001:2003/07/30 08:47:24.83 kernel  Virtual device 2 started using asynchronous i/o.
00:00000:00001:2003/07/30 08:47:24.83 server  Activating disk 'YXJHLOG'.
00:00000:00001:2003/07/30 08:47:24.83 kernel  Initializing virtual device 3, 'D:\data\YXJHLOG.DAT'
00:00000:00001:2003/07/30 08:47:24.83 kernel  Virtual device 3 started using asynchronous i/o.
00:00000:00001:2003/07/30 08:47:24.83 server  Activating disk 'sysprocsdev'.
00:00000:00001:2003/07/30 08:47:24.83 kernel  Initializing virtual device 1, 'C:\Sybase\DATA\SYBPROCS.DAT'
00:00000:00001:2003/07/30 08:47:25.00 kernel  Virtual device 1 started using asynchronous i/o.
00:00000:00001:2003/07/30 08:47:25.69 server  Recovering database 'model'.
00:00000:00001:2003/07/30 08:47:25.82 server  The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:47:25.85 server  Database 'model' is now online.
00:00000:00001:2003/07/30 08:47:25.85 server  Clearing temp db
00:00000:00001:2003/07/30 08:47:32.76 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:47:45.66 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:47:45.69 server  Database 'tempdb' is now online.
00:00000:00001:2003/07/30 08:47:45.69 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:47:45.81 server  Recovering database 'sybsystemprocs'.
00:00000:00001:2003/07/30 08:47:46.97 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:47:47.02 server  Database 'sybsystemprocs' is now online.
00:00000:00001:2003/07/30 08:47:47.21 server  Recovering database 'YX_EXCHANGE'.
00:00000:00001:2003/07/30 08:48:36.41 server  The transaction log in the database 'YX_EXCHANGE' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:48:36.43 server  Database 'YX_EXCHANGE' is now online.
00:00000:00001:2003/07/30 08:48:36.48 server  Recovering database 'CHAINCENTER'.
00:00000:00001:2003/07/30 08:48:36.51 server  Redo pass of recovery has processed 1 committed and 0 aborted transactions.
00:00000:00001:2003/07/30 08:49:14.83 server  The transaction log in the database 'CHAINCENTER' will use I/O size of 2 Kb.
00:00000:00001:2003/07/30 08:49:14.85 server  Database 'CHAINCENTER' is now online.
00:00000:00001:2003/07/30 08:49:14.85 server  Recovery complete.
00:00000:00001:2003/07/30 08:49:14.85 server  SQL Server's default sort order is:
00:00000:00001:2003/07/30 08:49:14.85 server          'bin_iso_1' (ID = 50)
00:00000:00001:2003/07/30 08:49:14.85 server  on top of default character set:
00:00000:00001:2003/07/30 08:49:14.85 server          'iso_1' (ID = 1).
00:00000:00001:2003/07/30 08:49:14.85 server  Loaded default Unilib conversion handle.

chenfeng825

你的sybase有问题。1605错误。我从sybase的故障手册上copy下面的内容给你参考。
Error 1605
Severity
21
Error message text
Failed to open virtual socket for new connections
This error may be caused by a hardware problem.
Explanation
The Adaptive Server Network Handler listens on the ports specified in your network addressing ( interfaces or sql.ini) file. When a connection comes in, the Network Handler opens another socket to redirect that client, clearing the listener port for the next connection, hence the term "virtual" socket. The connection appears, from the outside, to be connected to the interfaces port, when it is actually connected at a different address to which there is a pointer.
Error 1605 occurs when a failure occurs in the process of opening the new socket. There are a number of things that can cause this:
·Exceeding the number of configured  user connections
·Exceeding the number of  configured sockets
·Network configuration problems such as using the same IP address for two different clients
Error 1605 error can be raised at the following times:
·At startup time, when the network is initialized.
·At creation of a process, when a new connection request comes in and Adaptive Server is unable to handle it.
·At the forced termination of a process, when a new connection request comes in and Adaptive Server is unable to handle it.
The information below includes several internal configuration parameters. You will not be changing these directly, but they are included to help explain how to calculate values for sp_configure parameters that relate to connection handling. Following are the kernel and configuration parameters used to calculate cnsocket (the maximum number of  virtual sockets):
·kimaxfd -  the maximum number of configured per process file descriptors that a process can use at a given time. The error log message "Using # #  file descriptors" shows what this value is at boot time.
·number of remote sites -  this configuration parameter specifies the maximum number of remote sites.
·number of user connections -  this Adaptive Server configuration parameter specifies the maximum number of user connections allowed.
·cnsocket -  the maximum number of virtual sockets, calculated as:
cmaxnetworks (maximum #  of user connections configured)
+ cusrconnections (the number of user connections configured)
+ cfgsitebuf (the number of remote sites configured)
+ XTRA_SOCKETS (defined as 2 in 11.0.x)
During start-up, if the value for cnsocket is greater than the value for kimaxfd, then the value of cnsocket will be set to the value of kimaxfd, and the message:
kistartup: number of virtual sockets set to # # #
is printed to the log where # # #  is the value of kimaxfd/cnsocket.
Adaptive Server recalculates the value for cnsocket when you use sp_configure to change related parameter values.
Action
Check the error that precedes the 1605 error. If that error is one of the following:
nopen: No virtual sockets available
nopen: no room in socket table
then the value for the Server configuration block parameter cnsocket has been exceeded. To solve the problem in this case, increase user or network connections and possibly increase the maximum number of file descriptors per process:
1.Determine the current value for cnsocket.
Use dbcc resource (this command requires sybase_ts_role and dbcc tracecon(3604) to determine the current configuration for sockets.
2.Determine the current value for the maximum number of network connections:
1>; select @@max_connections
2>; go
If the value of cnsocket is greater than the value of @@max_connections, a problem may occur. Step 5 provides details.
3.Determine the current value for number of devices (the number of database devices that Adaptive Server can use, excluding dump devices):
1>; sp_configure "number of devices"
2>; go
4.Determine an appropriate value for @@max_connections, based on the number of users expected to be logged on at any given time, and the number of devices. Remember that each device takes up a user connection. @@max_connections is the kernel resource value rmaxuconn and is calculated using the following information:
·ksnmstprts -  number of Server listener ports configured (in your interfaces file, additional Server listener ports are listed as clones of the "master" line for the Adaptive Server, one additional line for each interface you want Adaptive Server to listen on).
·rmaxuconn -  maximum value for user connections. It is calculated by: @@max_connections = kimaxfd - ksnmstprts - 4 (5 on OpenVMS). The pool of four is reserved for:
stdout error log console dump/load device (debug on OpenVMS)
5.Compare the appropriate value for sockets to the current value for sockets, as determined in step 1. (Remember that the maximum number of virtual sockets = number of user connections + number of remote sites + 3.) If the current value is too low, use sp_configure to increase the value of number of user connections and/or number of remote sites so that the calculated value for sockets will be correct. This will probably correct the error. If the error still occurs, call Sybase Technical Support.
Under UNIX, you may need to raise the maximum number of file descriptors at the operating system level for the Adaptive Server if the new value for cnsocket exceeds the maximum number of per process file descriptors times the number of online engines for 11.0.x and later versions. In an OpenVMS environment, if you increase the value for number of user connections, you may also need to increase the value of the OpenVMS operating system parameter channelcnt and recalculate your system quotas. Refer to Managing and Monitoring Sybase Adaptive Server Enterprise Using Sybase Central for information about managing the maximum number of user connections available on an NT Server.
Additional information
Refer to "Setting Configuration Parameters" in the System Administration Guide for information about configuration parameters. Refer to the Reference Manual for information about sp_configure.
For parameter information specific to your platform, refer to the Adaptive Server installation and configuration guide.
If you need to call Technical Support, have the following information available:
· Server release and SWR rollup level
· Server error log
·Operating system version and error log
·Output of dbcc resource and sp_configure
·Text of all error messages

myr

看得不是很明白，可以告诉我怎么解决吗？
如果不行，我是不是要重新安装系统？

chenfeng825

把你的配置参数也贴上来。还要详细的版本好。你先使着把number of user connect和number of remote site加大点看行不行。
不要没事冲撞os。

myr

1605错误。我问过sybase公司了，他们说这“往往是指ASE接收到的操作系统网络包的某个标志位有问题，可能与操作系统补丁包有关”，我先看看，如果不行就重做。

chenfeng825

重装os好了也是没什么意思。数据库在建立时就需要os的所有补丁（包括性能和安全）然后建立db server后先不要急着上产品数据库，将最新的ebf上去。ebf要看有rollup.还有ebf并不是覆盖文件就可以了，还可能要更新master等等。这些至顶的帖子都有。
还有就是建议这样以后如果产品库没有问题最好不要急着更新新的ebf，可能里面有新的bug.

RS9000

你操作系统的 补丁是 SP几，打个最新的补丁