What is Error on exchange IDN?

[JustinWithoutAnE]

We have an application that is trying to connect to another server using an API. The API returns a message saying "Error on exchange IDN". Is there anyone who knows what this means?
Unfortunately we don't have access to the source code of the program that invokes the API and are unable to debug it.

The connection is being done using port 10300. When we try to use TELNET to connect we get this message:

Message ID . . . . . . : TCP84C6 Severity . . . . . . . : 40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 15/07/22 Time sent . . . . . . : 16:19:17

Message . . . . : Internal operations error - RESULT -8 CC 12301 RC 0 ERRNO
3006.
Cause . . . . . : An internal operation function encountered an error - RC 0
RESULT -8 CCODE 12301 ERRNO 3006.
Recovery . . . : Retry the operation. If problem persists contact your
service representative to report the problem.

[Scott Klement]

You haven't provided much information. What sort of API is this? What's its name, what does it do, how does it work, etc?

I can tell you that 3006 basically means "I/O error" -- meaning there was some error during input/output -- presumably the error is "Error on exchange IDN", though you didn't include any details on this.

If I had to guess, you are trying to work with a Microsoft Exchange server. IDN means Internationalized Domain Names -- the abilility to create a domain name with international characters in it ( https://en.wikipedia.org/wiki/Intern...ed_domain_name ) so it is seeing a character value in a domain name field that it doesn't know how to process.

[JustinWithoutAnE]

You haven't provided much information. What sort of API is this? What's its name, what does it do, how does it work, etc?

This is actually our problem. We know the program calls an API but we don't know which one. The program containing the call to the API is a third party program and we don't have access to either the code or the vendor. Only the compiled objects were provided to us and the program has been unchanged since it was first acquired in 2001.

[Scott Klement]

Then you'll need to report this to whomever is responsible for maintaining that third-party program. It seems there was a change on the API server that they need to accomodate.