Can't export from NAV 2018 without loosing connection to server

MBfm

I loose the connection to the server and am not able to export data because of it.



When I check the event viewer, I see the following error (sadly it's in Danish, but you should still be able to pick something out):

Type: System.Runtime.Serialization.SerializationException
Message: <ii>Typen 'Microsoft.Dynamics.Nav.Types.StreamTransfer' med datakontraktnavnet 'StreamTransfer:http://schemas.datacontract.org/2004/07/Microsoft.Dynamics.Nav.Types' blev ikke forventet. Brug evt. en DataContractResolver, hvis du bruger DataContractSerializer, eller føj de typer, der ikke er kendt statisk, til listen over kendte typer, f.eks. ved at bruge attributten KnownTypeAttribute eller ved at føje dem til listen over kendte typer, der overføres til funktionen til serialisering.</ii>
StackTrace:
ved System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
ved System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiTypeAtTopLevel(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle originalDeclaredTypeHandle, Type graphType)
ved System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
ved System.Runtime.Serialization.XmlObjectSerializer.WriteObjectContentHandleExceptions(XmlWriterDelegator writer, Object graph)
ved Microsoft.Dynamics.Nav.Types.Channels.ErrorLoggingDataContractSerializerOperationBehavior.ErrorLoggingSerializer.WriteObjectContent(XmlDictionaryWriter writer, Object graph)
Source: System.Runtime.Serialization
HResult: -2146233076

Best regards

panhadom@hotmail.com

I also have this issue, does anyone have solution?

dave_c

I got the same error, tried it through powershell, and then got the error here:
https://forum.mibuso.com/discussion/70767/export-navdata-not-support-for-nav-2018-with-extension-v2-installed
I think this is the RTC equivilent of that error. It is fixed in CU5 apparently.
https://support.microsoft.com/en-gb/help/4171921/cumulative-update-05-for-microsoft-dynamics-nav-2018-build-21836