Known Issues for ECDA

Because ECDA uses a 1MB thread stack size, on 32-bit Windows machines, the maximum number of client connections is limited to approximately 1900 connections. Certain Windows operating systems allow the 4GT RAM tuning option, which can provide additional connections.

Workaround: None.

The Admin Service of ECDA 15.0 and later has been changed from to read and write encrypted passwords to using the user.pwd file. Earlier versions of user.pwd files are not supported with ECDA 15.0 and later result in administrator login failures.

Workaround: Reenter the administrator IDs and passwords from earlier installations to the new Admin Service.

You can start and use ECDA as a service, but it is not visible in the Windows 2003 Task Manager.

Workaround:Use other Windows utilities to monitor service processes.

If you edit the sql.ini file with a word processing program, such as Microsoft Word, extra non-printable characters may be added to the end of text in the sql.ini file. As a result, Sybase Open Server-based applications may not recognize the server names in the sql.ini file.

Workaround:To modify the sql.ini file, use dsedit, which Sybase provides with your Open Client and Open Server installation.

When you use the InstallShield uninstallation function from the Start menu, it does not remove all ECDA server files as well as the Control Center installer program in Add or Remove Programs. Manually remove any files that remain.

Workaround:None.