Feedback
Did this article resolve your question/issue?

   

Article

Connection fails to read MS Access file using Sequelink ODBC Socket Server

Information

 
TitleConnection fails to read MS Access file using Sequelink ODBC Socket Server
URL Nameconnection-fails-to-read-ms-access-file-using-sequelink-odbc-socket-server
Article Number000119637
EnvironmentProduct: SequeLink Server for ODBC Socket
OS: Windows 2016
Product: SequeLink ODBC
OS: AIX
Version: 6.0
Database: MS Access
Application: All Supported Applications
Question/Problem Description
Connection fails with below error message to read MS Access file using Sequelink ODBC on AIX and SequeLink Server for ODBC Socket installed in windows 2016
Steps to Reproduce
Clarifying Information
SequeLink Server for ODBC Socket on windows 2008 is configured to use DataSourceLogonMethod as OSIntegrated and the connection was successfull.

SequeLink Server for ODBC Socket on windows 2016 is configured to use DataSourceLogonMethod as DBMSLogon(UID,PWD) and the connection fails.
Error Message[ODBC Socket][Microsoft][ODBC Microsoft Access Driver] Not a valid password.
Defect Number
Enhancement Number
Cause
On Windows 2016 SequeLink Socket server the DataSourceLogonMethod was set to DBMSLogon(UID,PWD) instead of OSIntegrated
Resolution
Set the DataSourceLogonMethod=OSIntegrated

Run the SequeLink Management studio.
Select the datasource.
Select User Security.
Update the DatasourceLogonMethod attribute.
save changes.
Workaround
Notes
Last Modified Date1/2/2020 5:59 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.