MIP SDK 2018 R2 Unable to Connect to VMS 2025 R2

MIP
1

Hi,

I am using MIP SDK 2018 R2 to connect to a VMS running version 2025 R2, but I encounter a ServerNotFoundMIPException during the connection attempt.

The connection is successful when using the XProtect client, and also when using the latest MIP SDK against the same VMS 2025 R2 system.

Additionally, I was able to connect successfully using MIP SDK 2018 R2 with VMS version 2025 R3, which indicates that the SDK can work with newer VMS versions.

Since upgrading the SDK is not currently possible on my side, could you please advise whether there are any specific configurations or compatibility settings required on the VMS 2025 R2 side to support connections from MIP SDK 2018 R2?

Thank you.

2

One likely explanation is encryption.

The MIP SDK 2018 R2 predates the XProtect server‑side encryption framework that is commonly enabled in newer VMS versions. If encryption is enabled in XProtect 2025 R2, an SDK built on 2018 R2 will not be able to connect. This would also explain why your test against 2025 R3 works, if encryption is not enabled there.

You can verify this on the VMS server:

  • Open Server Manager (tray icon)

  • Launch Server Configurator

  • Check the Encryption section to see whether server / streaming encryption is enabled, and temporarily disable it for testing

Server Configurator is the supported way to view and control encryption and certificates on the Management/Recording servers
Documentation: Server Configurator (explained)

If encryption is required, the only supported solution is to upgrade the integration to a newer MIP SDK that supports encrypted communication.

For reference see the MIP SDK Release note announcing “Changes to authentication”.

3

Hi Bo,

Thank you for your response.

I am experiencing the same issue (ServerNotFoundMIPException) with a Milestone Federated Server set up in our local lab running XProtect Corporate 2025 R2.

As suggested, I checked the encryption settings, and encryption is currently disabled.

Could you please advise if there are any additional configurations or settings I should verify to resolve this issue when connecting using MIP SDK 2018 R2?

Thank you.