DBExpoter fails to export using network path

Hi!

After updating Milestone SDK from 2020 R3 to 2021 R2 we started encounter a problem with DBExporter. It fails with the error “The filename, directory name, or volume label syntax is incorrect” every time we use network paths, for example [\\TEST-PC\Export.](file://TEST-PC/Export.) There is no problem with access rights and it works with 2020 R3 SDK.

Thanks in advance.

I just now tested with the hotfixed MIP SDK 2021R2, and I could not reproduce the issue. I would recommend the hotfixed version anyways as other issues related to DBExporter was fixed.

Note that the fix is in the form of a new MIP SDK installer, when using it you must reference and use the new dlls directly as there is no fixed version in NuGet. (Remove NuGet reference if you have it.)

Get the fix here - https://supportcommunity.milestonesys.com/s/article/XProtect-2021-R2-cumulative-patch-installers?language=en_US

Hi! Thanks for response!

I’ve just tried with this SDK https://download.milestonesys.com/MTSKB/KB000039500/MIP%20SDK/ (built on 12/23/2021:09:08:47) and the problem still exists. Is there some newer installer?

No, this is the currently newest..

Please verify that you can do the same export to the same location using the Smart Client.

Is [\\TEST-PC\Export](file://TEST-PC/Export) the actual path? If not and you don’t want to disclose the actual path, I am wondering if the path length might be a factor, so how long is the path?

Yes, [\\TEST-PC\Export](file://TEST-PC/Export) is one of the paths we used for testing.

It works for Milestone 2021 R2 Smart Client, but fails with SDK samples (with dlls both from installer and NuGet).

I have reproduced it now. Now it seems odd that I could not reproduce yesterday. I will report this to Milestone Development for further investigation. I will update here when a solution is found.

Milestone have developed a fix.

You find the fix here: https://supportcommunity.milestonesys.com/s/article/XProtect-2021-R2-cumulative-patch-installers?language=en_US

(Download has been updated.)

Important: The fix comes in the form of a MIP SDK installer. If you are currently building using NuGet you must remove the NuGet and instead reference the dlls directly from he installed MIP SDK.