Skip to content
This repository was archived by the owner on May 22, 2025. It is now read-only.

expected TDS_MSG_SEC_ENCRYPT4, received TDS_MSG_SEC_ENCRYPT3 for ASE v16.0 SP04 #244

Closed
vsukameti opened this issue Aug 15, 2023 · 3 comments

Comments

@vsukameti
Copy link

vsukameti commented Aug 15, 2023

Description

A clear and concise description of what the bug is.

Getting below error while trying to connect SQL-exporter to RMA agent of ASE. SQL-exporter uses go-ase driver.

No metrics gathered, [from Gatherer #1] error opening test connection: go-ase: error logging in: server only supports Extended Plus Encrypted Password login protocol, at least On Demand Command Encryption is required: expected TDS_MSG_SEC_ENCRYPT4, received TDS_MSG_SEC_ENCRYPT3

I am able to connect to ASE database server successfully. However, connecting to RMA agent fails with the above error

Full version of ASE:
Adaptive Server Enterprise/16.0 SP04 PL01/EBF 29704 SMP/P/x86_64/SLES 12.4/ase160sp04pl01x/3473/64-bit/FBO/Tue Jul 20 07:58:11 2021

Expected behaviour

Successfully connect sql-exporter to RMA agent of ASE server

Current behaviour

Getting the error as mentioned above

Steps to Reproduce

Steps to reproduce the behavior:

  1. Launch ASE High availability database server. ASE version- Adaptive Server Enterprise/16.0 SP04 PL01/EBF 29704 SMP/P/x86_64/SLES 12.4/ase160sp04pl01x/3473/64-bit/FBO/Tue Jul 20 07:58:11 2021
  2. Download and install SQL-exporter on the instance
  3. Use SQL-exporter to connect to RMA agent of ASE.
  4. See the above error

Environment

Client:
OS: SUSE Linux
go version: v1.20.4
go-ase version / commit hash:
go-dblib version / commit hash:

Server:
OS: SUSE Linux
ASE version: Adaptive Server Enterprise/16.0 SP04 PL01/EBF 29704 SMP/P/x86_64/SLES 12.4/ase160sp04pl01x/3473/64-bit/FBO/Tue Jul 20 07:58:11 2021

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

@zhht1204
Copy link

zhht1204 commented Nov 9, 2024

Same problem. Anyone resolved it?

@krichter1
Copy link
Contributor

Please be informed that we are planning to officially sunset this repository.
Development and support will cease, and the project will be archived.
See also #260 .

@krichter1
Copy link
Contributor

This public repository is read-only and no longer maintained.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants