Hi all,
Has anyone else experienced this issue with 2015?
https://blogs.msdn.microsoft.com/nav/2013/02/25/nav-2013-reports-may-be-difficult-to-read-when-printing-over-terminal-services/
We had exactly this issue with Nav2015 Terminal Services on Windows Server 2008 R2. We installed the recommended patch
https://support.microsoft.com/en-us/kb/3037639 and the problem fixed itself.
Now however we find that if the client has a few things to print and someone closes the Terminal Services Session...... the client is very often crashing. Not always. Maybe 50:50. Before the client would just keep running in the session and continue printing away happily.
In the Event Viewer of the server I see the following:
Type: System.Drawing.Printing.InvalidPrinterException
Message: Settings to access printer '\\printserver2\KUM-FS4300-02' are not valid.
StackTrace:
at System.Drawing.Printing.PrinterSettings.GetHdevmodeInternal(String printer)
at System.Drawing.Printing.PageSettings.get_ExtraBytes()
Application: Microsoft.Dynamics.Nav.Client.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Settings to access printer '\\printserver2\KUM-FS4300-02' are not valid.
Stack:
at System.Environment.FailFast(System.String)
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.HandleGeneralException(System.Exception)
Answers
did you use the printer via RDP- Client?