NST crashes when running a not licensed report

deV.ch

As the title says the NST crashes when running a report by code (run / runmodal) that is not in the license!
Yes, not only the Client, no the service tier crashes too!

The same report called from the menu causes the expected "not licensed" message and no crash.

Anybody else encountered this problem?

beran

Can you post the event log entry?

deV.ch

Here's the eventlog from the Service:

Service: MicrosoftDynamicsNavServer
Type: System.Reflection.TargetInvocationException
Message: Exception has been thrown by the target of an invocation.
StackTrace:
     at System.RuntimeMethodHandle._SerializationInvoke(Object target, SignatureStruct& declaringTypeSig, SerializationInfo info, StreamingContext context)
     at System.Reflection.RuntimeConstructorInfo.SerializationInvoke(Object target, SerializationInfo info, StreamingContext context)
     at System.Runtime.Serialization.ObjectManager.CompleteISerializableObject(Object obj, SerializationInfo info, StreamingContext context)
     at System.Runtime.Serialization.ObjectManager.FixupSpecialObject(ObjectHolder holder)
     at System.Runtime.Serialization.ObjectManager.DoFixups()
     at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
     at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
     at Microsoft.Dynamics.Nav.Common.ExceptionHandler.DeserializeFromByteArray(Byte[] bytes)
     at Microsoft.Dynamics.Nav.Common.ExceptionHandler.GetOriginalException(ServerFault serverFault)
     at Microsoft.Dynamics.Nav.Common.ExceptionHandler.GetOriginalException(FaultException`1 exception)
     at Microsoft.Dynamics.Nav.Service.NSClientCallback.FormRunModal(NavForm form, NavFormRuntimeParameters parameters)
     at Microsoft.Dynamics.Nav.Runtime.NavForm.RunModal(NavRecord record, Int32 fieldNo)
     at Microsoft.Dynamics.Nav.Runtime.NavReport.RunRequestPage()
     at Microsoft.Dynamics.Nav.Runtime.NavReport.RunReportInternal(NavRecord record, Boolean displayResult)
     at Microsoft.Dynamics.Nav.Runtime.NavReport.RunReport(Nullable`1 requestWindow, Nullable`1 systemPrinter, Boolean runReportModal, NavRecord record, IList`1 reportTextualFilters)
     at Microsoft.Dynamics.Nav.Runtime.NavReport.RunReport(Int32 reportId, Nullable`1 requestWindow, Nullable`1 systemPrinter, Boolean isRunningAsModal, NavRecord record, IList`1 textualFilters)
     at Microsoft.Dynamics.Nav.Runtime.NavReport.Run(Int32 reportId)
     at Microsoft.Dynamics.Nav.Service.NSReport.Run(NavConnection connection)
     at Microsoft.Dynamics.Nav.Service.NSService.<>c__DisplayClass24.<RunReport>b__23(Connection connection)
     at Microsoft.Dynamics.Nav.Service.NSService.ExecuteOperation[T](String operationName, ServiceOperation`1 operation, Connection connection, Boolean revertLanguageChanges, WindowsIdentity impersonationIdentity)
Source: mscorlib
----------------------------------
Type: System.Runtime.Serialization.SerializationException
Message: Member 'Anzeigefehler bei Ausnahmereaktion.' was not found.
StackTrace:
     at System.Runtime.Serialization.SerializationInfo.GetElement(String name, Type& foundType)
     at System.Runtime.Serialization.SerializationInfo.GetBoolean(String name)
     at Microsoft.Dynamics.Nav.Client.NavClientClosingException..ctor(SerializationInfo info, StreamingContext context)
Source: mscorlib

Build No. : 6.0.31414.0

deV.ch

Fixed!

You can solve this with a platform hotfix! I tested it with Build No. 6.0.32029 and it works fine.

There can be several Builds affected betwen SP1 original and 32029. SP1 Orig. doesn't have that bug, it was a temporary thing between Builds...